Clock too fast?

From: Kevin Kinsey (kdk_at_daleco.biz)
Date: 12/30/04

  • Next message: Mattias Björk: "Problems with MySQL and SNORT after Reboot" 
    Date: Thu, 30 Dec 2004 16:52:04 -0600
To: questions@freebsd.org

    >Thank you for the suggestions. Unfortunately, I've been through all
    >that, including the rude values of minpoll and maxpoll, using multiple
    >servers, and starting with a fresh drift file. I'm pretty sure ntpd
    >isn't the problem. In addition, the hardware clock itself appears to be
    >plenty accurate, as it is always correct within a second or two when I
    >check it directly in BIOS ... and two other 5.3-STABLE hosts on the same
    >network, with the same ntpd configuration, but on different hardware, do
    >not have this problem, which began when I updated (reinstalled) to
    >5.3-STABLE from 5.2.

    [503] Thu 30.Dec.2004 16:51:10 [kadmin@archangel][~]
    #sysctl kern.timecounter.choice
    kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-1000000)

    Last box I had trouble like this on was K6-2/500 on Asus p5a mobo.
    Setting to i8254 worked in that case. If you've not tried all the
    possibilities, do so now.

    I must also say that I *think* I had a box (around PII 200) that I
    never got this resolved on (but I'm not sure how hard I tried....)

    HTH,

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

  • Next message: Mattias Björk: "Problems with MySQL and SNORT after Reboot"

    Relevant Pages

    • Re: clock running fast
      ... > that, including the rude values of minpoll and maxpoll, using multiple ... > servers, and starting with a fresh drift file. ... the hardware clock itself appears to be ... > network, with the same ntpd configuration, but on different hardware, do ...
      (freebsd-stable)
    • Re: Clock skew problem - RHEL 4 AS
      ... Syed Johnullah wrote: ... I don't have problem in other servers in which 32 bit RHEL 4 ES ... The accuracy of the hardware clock is determined by the quality of its timebase oscillator. ...
      (RedHat)
    • Re: simple time server
      ... That presupposes that both your clients and servers are located in the ... I don't mean "local time" as in 12:00 means solar noon. ... With somebody constantly correcting the hardware clock, ... The system clock on a Unix system doesn't operate in a time zone at ...
      (comp.protocols.time.ntp)
    • Re: time shift in CEST
      ... If the system is off at the change time, it will assume at next startup that the hardware clock contains the correct local time, so you will need to set that manually. ... I always set servers to UTC=true for this reason. ... Clemson University Math Sciences ...
      (RedHat)