ntpd struggling to keep up - how to fix?
Torfinn Ingolfsen
torfinn.ingolfsen at broadpark.no
Sun Feb 21 16:36:30 UTC 2010
On Sun, 21 Feb 2010 16:08:23 +1100
Peter Jeremy <peterjeremy at acm.org> wrote:
> Having re-checked my maths, using both your "time reset" results, can
> you please try:
> sysctl machdep.acpi_timer_freq=3570847
> That should result in a drift of close to zero (well within NTP's
> lock range of +/- 300ppm).
And a few hours later: from /var/log/messages:
Feb 21 09:54:50 kg-f2 ntpd[55452]: ntpd 4.2.4p5-a (1)
Feb 21 09:59:10 kg-f2 ntpd[55453]: kernel time sync status change 2001
More info:
root at kg-f2# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*kg-omni1.kg4.no 78.157.115.4 3 u 31 64 377 0.174 -10.253 0.160
root at kg-f2# ntpdc -c loopi -c sysi
offset: -0.010253 s
frequency: 6.744 ppm
poll adjust: -30
watchdog timer: 47 s
system peer: kg-omni1.kg4.no
system peer mode: client
leap indicator: 00
stratum: 4
precision: -18
root distance: 0.02956 s
root dispersion: 0.06795 s
reference ID: [10.1.10.1]
reference time: cf2bdf36.f8820aef Sun, Feb 21 2010 17:35:02.970
system flags: auth monitor ntp kernel stats
jitter: 0.000153 s
stability: 0.000 ppm
broadcastdelay: 0.003998 s
authdelay: 0.000000 s
Problem solved.
Thanks a lot.
--
Torfinn
More information about the freebsd-stable
mailing list