clock runs very fast on 5.1R

From: kanematsu (taca98_at_hotmail.com)
Date: 11/22/03

  • Next message: mike bueide: "Re: Technical/support questions on -newbies" 
    To: <freebsd-newbies@freebsd.org>
Date: Sat, 22 Nov 2003 00:59:33 -0500

    Clock on my server runs very fast. It is about twice faster,

    and I think it is not good for a server. I'm running 5.1R.

    The problem did not occur under 4.4R, 4.7R, or 4.8R

    on the same PC. I know FreeBSD doesn't read time

    from CMOS Clock. Right after rebooting the machine,

    date command shows me a correct time because of

    xntpd in rc.conf. The PC has AMD 350 MHz IBM Aptiva.

    I pasted information of Timercounter “i8254” and “TSC”

    from dmesg.today below.

     

    Copyright (c) 1992-2003 The FreeBSD Project.

    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

                The Regents of the University of California. All rights reserved.

    FreeBSD 5.1-RELEASE #15: Thu Nov 20 00:54:10 EST 2003

        root@abc.abc.com:/usr/src/sys/i386/compile/KERNELABC

    Preloaded elf kernel "/boot/kernel/kernel" at 0xc043c000.

    Preloaded elf module "/boot/kernel/acpi.ko" at 0xc043c1cc.

    Timecounter "i8254" frequency 1193182 Hz

    Timecounter "TSC" frequency 349180042 Hz

    CPU: AMD-K6(tm) 3D processor (349.18-MHz 586-class CPU)

     

    I added each line below on my kernel and configured as someone

    suggested me but it didn’t work.

     

    #options CLK_USE_TSC_CALIBRATION

     

    #options TIMER_FREQ=2359004

     

    #options CLK_USE_i8254_CALIBRATION

     

    Also, someone suggested me that I might modify clock.c file in

    /usr/src/sys/i386/isa/ but I didn’t know how to modify it.

     

    Does anyone have any idea or know where should I ask?

    Kanematsu

    _______________________________________________
    freebsd-newbies@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
    To unsubscribe, send any mail to "freebsd-newbies-unsubscribe@freebsd.org"

  • Next message: mike bueide: "Re: Technical/support questions on -newbies"

    Relevant Pages

    • Re: polling algorithm
      ... >>> the correct time is not within its interval. ... > for a clock is a computed value based on observed data, ... > server claims its own accuracy is. ... > way to determine whether it is a falseticker. ...
      (comp.protocols.time.ntp)
    • Re: DST Change frustration!
      ... What you need is a server that gives you the correct time. ... I discovered that if I stop the time service and change my clock to the ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: Received mail timestamp is off by 7 hours
      ... > server does are dependent in some way on the correct time. ... NTP is difficult to configure. ... If your clock tends to run noticably fast or slow, ...
      (freebsd-questions)
    • Re: NTP no internet connection
      ... Even worse, if the temperature is not controlled, the clock frequency and, therefore, the tick rate, can change from hour to hour. ... Nobody is going to crash into anything but the various machines trying to synchronize to the server will probably be all over the map. ... I mean that a system with a GPS based hardware reference clock synchronizes a mob of other machines more closely than a system using a bunch of internet servers can. ... Those internet servers MAY know the correct time to within a few microseconds but, by the time the internet is done with the query and response packets, the time is a "Scientific Wild Ass Guess" with an uncertainty of many milliseconds. ...
      (comp.protocols.time.ntp)
    • Re: Which release notes say sts$manager:utc$configure_tdf is obsolete
      ... >>in UTC, and after comparing it to the time as determined from its ... I think it will only attempt to change the clock if it is less than ... or a ST clock just after the spring forward, and NTP would fix it. ... guess of the real time that it makes from polling the time server. ...
      (comp.os.vms)