On 2010-Feb-17 20:03:22 +0100, Torfinn Ingolfsen <torfinn.ingolf...@broadpark.no> wrote: >On Wed, 17 Feb 2010 19:49:27 +0100 >Torfinn Ingolfsen <torfinn.ingolf...@broadpark.no> wrote: > >> Unfortunately, it isn't enough to keep the machine in sync all the time. >> But it is better than HPET so I'll keep it.
Did you delete /etc/ntp.drift between timecounter changes? >This thread is interesting: >http://lkml.indiana.edu/hypermail/linux/kernel/0903.1/01356.html > >Is there a way in FreeBSD to perform adjustmenst like adjtimex? There's ntptime(8) but it doesn't have a "self-calibrate mode". Based on the messages log you gave, and assuming the ntpd PLL is sane, your acpi-safe clock is about 2500ppm slow (the steps reflect about 2000ppm and the ntpd PLL should be compensating for a further 500ppm) - this is really bad, even for consumer-grade stuff. Are you running non-standard clock speeds or multipliers? If there's nothing obvious, I'd follow John Hay's suggesion and force set either your TSC or ACPI frequency in sysctl.conf (you can't override the HPET frequency). Take either the TSC or ACPI frequency reported by "sysctl machdep", reduce it by 2500ppm and set that in /etc/sysctl.conf. Assuming a "standard" (3.58MHz) ACPI, the latter would look like: machdep.acpi_timer_freq=3570596 kern.timecounter.hardware=ACPI-safe The stop ntpd, delete /var/db/ntp.drift and either reboot or manually set the above sysctl's and restart ntpd. [I think I've got the adjustment direction correct in the above, if I've stuffed up, you need to adjust in the other direction] -- Peter Jeremy
pgpcm7bDQJdjP.pgp
Description: PGP signature
