Re: xntpd: was ok with 2.2.14-pre17, broke again with 2.2.14

[Ron Flory]

Tim Walberg wrote:
> 
> I've never seen a kernel yet where this **doesn't** happen at least
> occasionally - Linux, Solaris, HP, or otherwise. It can be caused by
> erratic drift in the system clock caused by high load, as well as by
> a congested network/internet leading to irregular delays in polling,
> as well as a number of other factors. So I expect to see this on
> occasion. I would only worry if you see it very often - e.g. more than
> once or twice an hour, or if you never see a "synchronized to..."
> message within a few (<10) minutes after a "synchronization lost".

Jan  6 18:56:17 valen xntpd[430]: synchronisation lost
Jan  6 19:01:08 valen xntpd[430]: synchronized to 172.22.48.1,stratum=3
Jan  6 19:10:21 valen xntpd[430]: time reset (step) 0.216240 s
Jan  6 19:10:21 valen xntpd[430]: synchronisation lost
Jan  6 19:15:41 valen xntpd[430]: synchronized to 172.22.48.1,stratum=3
Jan  6 19:16:45 valen xntpd[430]: kernel pll status change 89

 Agreed, loss of sync is not an unuaual event in itself, but under
kernels < 2.2.13 I remember this happening much less often.  The two
above are about 15 minutes apart on a lightly loaded machine, which
leaves me somewhat suspicious.  Under 2.2.14-pre17/18 they were rare-
now they are back.

Jan  6 15:33:34 valen xntpd[430]: synchronisation lost
Jan  6 16:41:34 valen xntpd[430]: synchronisation lost
Jan  6 16:52:14 valen xntpd[430]: synchronisation lost
Jan  6 17:43:04 valen xntpd[430]: synchronisation lost
Jan  6 17:57:37 valen xntpd[430]: synchronisation lost
Jan  6 18:56:17 valen xntpd[430]: synchronisation lost
Jan  6 19:10:21 valen xntpd[430]: synchronisation lost
Jan  6 20:29:17 valen xntpd[430]: synchronisation lost
Jan  6 20:43:55 valen xntpd[430]: synchronisation lost
Jan  6 21:32:59 valen xntpd[430]: synchronisation lost
Jan  6 21:47:19 valen xntpd[430]: synchronisation lost
Jan  6 22:35:03 valen xntpd[430]: synchronisation lost
Jan  6 22:49:30 valen xntpd[430]: synchronisation lost
Jan  7 04:15:53 valen xntpd[430]: synchronisation lost
Jan  7 04:29:53 valen xntpd[430]: synchronisation lost
Jan  7 05:44:33 valen xntpd[430]: synchronisation lost
Jan  7 05:58:53 valen xntpd[430]: synchronisation lost
Jan  7 07:49:50 valen xntpd[430]: synchronisation lost
Jan  7 08:01:34 valen xntpd[430]: synchronisation lost
Jan  7 08:15:51 valen xntpd[430]: synchronisation lost
Jan  7 10:52:39 valen xntpd[430]: synchronisation lost
Jan  7 11:39:33 valen xntpd[430]: synchronisation lost
Jan  7 11:54:32 valen xntpd[430]: synchronisation lost
Jan  7 12:39:20 valen xntpd[430]: synchronisation lost

 I'm really not too worried about this, 'just thought somebody might
want to know about a possible change in behavior that "may" be kernel
related-

ron