linux-kernel - Re: Linux 2.6.29-rc6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 04 Mar 2009 06:36:16 +0100
From:	Jesper Krogh <jesper@...gh.cc>
To:	john stultz <johnstul@...ibm.com>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>
Subject: Re: Linux 2.6.29-rc6

john stultz wrote:
> On Tue, 2009-03-03 at 21:39 +0100, Jesper Krogh wrote:
>> john stultz wrote:
>>> Do you see the same behavior if you drop all but one server (including
>>> the local clock: 127.127.1.0)? 
>> Yes.
>> Mar  3 21:20:59 quad12 ntpd[2435]: ntpd 4.2.4p4@...520-o Tue Jan  6 
>> 15:50:55 UTC 2009 (1)
>> Mar  3 21:20:59 quad12 ntpd[2436]: precision = 1.000 usec
>> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #0 wildcard, 
>> 0.0.0.0#123 Disabled
>> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #1 wildcard, 
>> ::#123 Disabled
>> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #2 lo, ::1#123 
>> Enabled
>> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #3 bond0, 
>> fe80::21e:68ff:fe57:8169#123 Enabled
>> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #4 lo, 
>> 127.0.0.1#123 Enabled
>> Mar  3 21:20:59 quad12 ntpd[2436]: Listening on interface #5 bond0, 
>> 10.194.132.91#123 Enabled
>> Mar  3 21:20:59 quad12 ntpd[2436]: kernel time sync status 0040
>> Mar  3 21:20:59 quad12 ntpd[2436]: frequency initialized -29.286 PPM 
>> from /var/lib/ntp/ntp.drift
>> Mar  3 21:21:58 quad12 ntpd[2436]: synchronized to 10.194.133.12, stratum 4
>> Mar  3 21:21:58 quad12 ntpd[2436]: time reset -6.148275 s
>> Mar  3 21:21:58 quad12 ntpd[2436]: kernel time sync status change 0001
>> Mar  3 21:25:01 quad12 ntpd[2436]: synchronized to 10.194.133.12, stratum 4
>> Mar  3 21:37:03 quad12 ntpd[2436]: time reset -0.664351 s
>>
>> Only one server and the minpoll 4 maxpoll 4 options to the server line.
> 
> Well, it may still need a few hours to settle. :)  Again, those time
> resets are seen when NTPd doesn't have a good drift ppm at startup, and
> it has to find it.

With one server and the maxpoll minpoll stuff, this on "settled" after a 
bit more than 3 hours:
Mar  4 01:14:05 quad12 ntpd[2436]: time reset -0.381826 s
Mar  4 01:15:39 quad12 ntpd[2436]: synchronized to 10.194.133.12, stratum 4
jk@...d12:~$ uptime
  06:35:40 up 15:55,  1 user,  load average: 0.00, 0.00, 0.00
jk@...d12:~$ ntpq -c peers
      remote           refid      st t when poll reach   delay   offset 
  jitter
==============================================================================
*bioinf.nzcorp.n 10.192.96.19     4 u    8   16  377    0.098  -80.184 
  0.673
jk@...d12:~$ ntpdc -c kerinfo
***Command `kerinfo' unknown
jk@...d12:~$ ntpdc -c kerninfo
pll offset:           -0.06619 s
pll frequency:        -500.000 ppm
maximum error:        0.130081 s
estimated error:      0.001201 s
status:               0001  pll
pll time constant:    4
precision:            1e-06 s
frequency tolerance:  500 ppm

-- 
Jesper
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/