[ntp:questions] ntp 4.2.0 and freebsd

mayer at gis.net mayer at gis.net
Fri Apr 8 16:40:02 UTC 2005


Has anyone filed a bug report on it, either with FreeBSD or with
NTP?

Danny
----- Original Message Follows -----
> I've recently upgraded my FreeBSD from 5.2.1 to 5.3 and that also
> meant that my ntp software version changed from 4.1.1b to 4.2.0.
> After that I've started to get a lot of messages like:
> 
> Mar 29 01:19:51 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 06:12:49 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 29 06:29:53 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 09:03:25 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 29 09:20:31 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 11:20:04 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 29 11:37:08 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 14:44:55 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 29 15:02:01 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 17:52:50 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 29 18:09:54 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 18:44:03 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 29 19:54:30 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 22:15:40 oddity ntpd[400]: time reset -0.288522 s
> Mar 29 22:15:40 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 29 23:09:19 oddity ntpd[400]: time reset +0.530732 s
> Mar 29 23:09:19 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 29 23:35:18 oddity ntpd[400]: time reset -0.165853 s
> Mar 30 00:41:14 oddity ntpd[400]: time reset -0.199104 s
> Mar 30 11:21:21 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 30 11:38:27 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 30 17:22:37 oddity ntpd[400]: time reset -0.392425 s
> Mar 30 17:22:37 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 30 17:26:06 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 30 17:28:15 oddity ntpd[400]: time reset +0.309711 s
> Mar 30 18:07:02 oddity ntpd[400]: time reset +0.164515 s
> Mar 30 18:41:43 oddity ntpd[400]: time reset -0.391355 s
> Mar 30 19:00:17 oddity ntpd[400]: time reset +0.598313 s
> Mar 30 19:47:45 oddity ntpd[400]: time reset -0.276978 s
> Mar 30 21:26:24 oddity ntpd[400]: time reset +0.158781 s
> Mar 30 23:18:01 oddity ntpd[400]: time reset +0.160708 s
> Mar 30 23:18:01 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 30 23:19:13 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 31 08:36:16 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 31 08:53:20 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 31 11:44:02 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 31 12:18:08 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 31 13:26:30 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 31 13:43:35 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 31 17:32:07 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 31 17:49:11 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 31 20:22:54 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 31 20:39:59 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 31 21:14:08 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 31 21:31:11 oddity ntpd[400]: kernel time sync enabled 2001
> Mar 31 22:39:28 oddity ntpd[400]: kernel time sync enabled 6001
> Mar 31 22:56:31 oddity ntpd[400]: kernel time sync enabled 2001
> 
> As I understand these 2001<->6001 flips are kernel PLL<->FLL flips.
> I am not sure that time resets are related to them, but I suspect that
> they are, because prior to upgrade I have not seen either of the
> events.
> 
> Please also note that I do not use any tinker-ing nor change
> maxpoll/minpoll paraemters.
> 
> Several other freebsd users have also reported the same problem on
> freebsd lists and joint investigation showed that the most likely
> cause is that ntp_adjtime(MOD_OFFSET) is not being called for longer
> than 2048 seconds (a parameter hardcoded in FreeBSD kernel). There was
> no significant changes in this area of FreeBSD kernel between the
> releases.
> 
> My knowledge of NTP protocol and ntpd internals is zero, so I hope
> that people on this list will ideas on what could be causing the
> described situation and how to investigate/debug this problem further.
> 
> Please also see
> http://www.mail-archive.com/freebsd-stable@freebsd.org/msg67325.html
> for some of the mentioned discussion on freebsd list(s).
> 
> P.S. if you would like to reply to me by email please flip TLD in
> From: from Australia to Ukraine.
> 
> -- 
> Andriy Gapon
> _______________________________________________
> questions mailing list
> questions at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions



More information about the questions mailing list