From owner-freebsd-questions@FreeBSD.ORG Sat May 21 13:56:57 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCB8716A4CE for ; Sat, 21 May 2005 13:56:57 +0000 (GMT) Received: from rdsmtp.iglou.com (rdsmtp.iglou.com [192.107.41.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EB2143D31 for ; Sat, 21 May 2005 13:56:55 +0000 (GMT) (envelope-from dlevitch@iglou.com) Received: from [192.107.41.3] (helo=iglou1.iglou.com) by rdsmtp.iglou.com with esmtp (8.12.5/8.12.5) id 1DZUTG-0005pc-H5 for freebsd-questions@freebsd.org; Sat, 21 May 2005 09:56:54 -0400 Received: from [192.107.41.17] (helo=shell1) by iglou1.iglou.com with esmtp (8.12.5/8.12.5) id 1DZUTG-0005YT-0g; Sat, 21 May 2005 09:56:54 -0400 Date: Sat, 21 May 2005 09:56:53 -0400 (EDT) From: Darrel X-X-Sender: dlevitch@shell1 To: Christian Hiris <4711@chello.at> In-Reply-To: <200505202240.27506.4711@chello.at> Message-ID: References: <200505202240.27506.4711@chello.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Originating-IP: 192.107.41.17 X-IgLou-Customer: verified cc: freebsd-questions@freebsd.org Subject: Re: NTP issues with 5.4 (SOLVED) (fwd) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2005 13:56:57 -0000 On Fri, 20 May 2005, Christian Hiris wrote: > On Friday 20 May 2005 01:01:01, Darrel wrote: > >> I installed openntpd considering that it should run with reduced >> privileges. The Workgroup did not sync up right away and I reinstalled >> NTP4. >> >> Currently, I can sync Window XP and Windows 98. My /var/log/messages: >> >> May 19 12:25:37 ntpd[379]: kernel time sync enabled 6001 >> May 19 12:42:40 ntpd[379]: kernel time sync enabled 2001 >> May 19 14:59:14 ntpd[379]: kernel time sync enabled 6001 >> May 19 15:16:19 ntpd[379]: kernel time sync enabled 2001 >> May 19 18:24:09 ntpd[379]: kernel time sync enabled 6001 >> May 19 18:41:14 ntpd[379]: kernel time sync enabled 2001 >> >> I am not sure, but this could be normal phase-lock-loop of the >> kernel. > > I think this is normal, the above status codes are in hex. Bit 0 of the 1st > byte tells about clock source (0=A 1=B), bit 1 of 1st byte stands for mode > status (0=PLL 1=FLL), bit 2 of 1st byte represents resolution status (0=us > 1=ns) and bit 7 of the 2nd byte indicates that PLL updates are enabled. > > status 0x2001 = source A, mode PLL, resolution ns, PLL updates enabled > status 0x6001 = source A, mode FLL, resolution ns, PLL updates enabled > > The command 'ntpdc -c kerninfo | grep status' displays some of this status > information in human-readable format. > > You can find a document that describes the Adaptive Hybrid Clock Discipline > Algorithm at http://www.eecis.udel.edu/~mills/database/papers/allan.pdf > > Cheers, > ch > > -- > Christian Hiris <4711@chello.at> | OpenPGP KeyID 0x3BCA53BE > OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu > Thanks, Christian! I am comparing to a NetBSD computer with older hardware, that seems to always have PLL enabled: May 14 18:26:10 ntpd[343]: ntpd 4.2.0-r Wed Mar 23 08:12:50 UTC 2005 (1) May 14 18:26:11 ntpd[343]: precision = 2.000 usec May 14 18:26:11 ntpd[343]: kernel time sync status 0040 May 14 18:26:12 ntpd[343]: frequency initialized 74.725 PPM from /var/db/ntp.drift May 14 18:29:29 ntpd[343]: time reset -1.128987 s May 14 18:29:29 ntpd[343]: kernel time sync disabled 0041 May 14 18:35:49 ntpd[343]: kernel time sync enabled 0001 Probably the 4 indicates that the clock had drifted too far for the program to permit syncing to- perhaps the battery should be replaced. I am still not sure why we do not see the new NTP4 mode shift to FLL, as with the FreeBSD computer. Maybe the /var/log/messages are just implemented differently on NetBSD 2.02. I will watch it occasionally with 'ntpdc -c kerninfo | grep status'. This NetBSD clock is also set to UTC and it seems that I recall that UTC can be improperly implemented when the computer previously had Microsoft Windows installed. Cheers, Darrel