Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 May 2005 09:56:53 -0400 (EDT)
From:      Darrel <dlevitch@iglou.com>
To:        Christian Hiris <4711@chello.at>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: NTP issues with 5.4 (SOLVED) (fwd)
Message-ID:  <Pine.GSO.4.61.0505210916570.4653@shell1>
In-Reply-To: <200505202240.27506.4711@chello.at>
References:  <Pine.GSO.4.61.0505191853570.24602@shell1> <200505202240.27506.4711@chello.at>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.61.0505210916570.4653>