From owner-freebsd-stable@FreeBSD.ORG Tue May 8 19:16:19 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C37D816A404 for ; Tue, 8 May 2007 19:16:19 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id 44D6D13C45B for ; Tue, 8 May 2007 19:16:18 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l48JGH51002952; Wed, 9 May 2007 05:16:17 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l48JGH01002951; Wed, 9 May 2007 05:16:17 +1000 (EST) (envelope-from peter) Date: Wed, 9 May 2007 05:16:17 +1000 From: Peter Jeremy To: Martin Dieringer Message-ID: <20070508191617.GH838@turion.vk2pj.dyndns.org> References: <200705081248.l48CmvBO083216@lurza.secnetix.de> <20070508151525.Y839@thinkpad.dieringer.dyndns.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nHwqXXcoX0o6fKCv" Content-Disposition: inline In-Reply-To: <20070508151525.Y839@thinkpad.dieringer.dyndns.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-stable@freebsd.org Subject: Re: clock problem X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2007 19:16:19 -0000 --nHwqXXcoX0o6fKCv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-May-08 15:33:51 +0200, Martin Dieringer w= rote: ># cat /var/db/ntp.drift >500.000 ># 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). The recovery action I've used is: - Kill ntpd # /etc/rc.d/ntpd stop - Delete the existing drift file # rm /var/db/ntp.drift - Reset the kernel PLL # ntptime -f 0 - Reset the system time # /etc/rc.d/ntpdate forcestart - Restart ntpd # /etc/rc.d/ntpd start At this point, ntpd will need to recalibrate itself - which can take anything from a couple of hours to a day or more, depending on the accuracy of your system clock. During this time, your system needs to be online. In my experience, ntpd also does not recover from having its own IP address change. My work-around is to restart NTP within my dhclient configuration if the address changes. You may also be able to configure your system so that ntpd attaches to an interface with a fixed address and the NTP packets are then NAT'd to the servers (though this will add jitter due to the additional processing). --=20 Peter Jeremy --nHwqXXcoX0o6fKCv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGQMyB/opHv/APuIcRAqHMAKCAfkGYSeLgJ8sqNdn02c85uJoCKACdEd+H r+LZjPeurIA0ocuGnf+74TU= =+gW4 -----END PGP SIGNATURE----- --nHwqXXcoX0o6fKCv--