Date: Thu, 10 May 2007 22:56:43 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: peterjeremy@optushome.com.au Cc: freebsd-stable@freebsd.org, martin.dieringer@gmx.de Subject: Re: clock problem Message-ID: <20070510.225643.-713548429.imp@bsdimp.com> In-Reply-To: <20070508191617.GH838@turion.vk2pj.dyndns.org> References: <200705081248.l48CmvBO083216@lurza.secnetix.de> <20070508151525.Y839@thinkpad.dieringer.dyndns.org> <20070508191617.GH838@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20070508191617.GH838@turion.vk2pj.dyndns.org>
Peter Jeremy <peterjeremy@optushome.com.au> writes:
: There seems to be a bug in ntpd where the PLL can saturate at
: +/-500ppm and will not recover. This problem seems too occur mostly
: where the reference servers have lots of jitter (ie a fairly congested
: link to them).
Yes. This is a rather interesting misfeature of ntpd. Its rails are
at +/- 500ppm, and when it hits the rail it assumes that things are
too bad to continue and it stops.
Most PC clocks have a frequency error on the order of 10-150ppm, so it
doesn't take a whole lot of jitter from a conjectsted remote network
to exceed the limits...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070510.225643.-713548429.imp>