From: Jesper Krogh <jesper@krogh.cc>
To: john stultz <johnstul@us.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: Re: Linux 2.6.29-rc6
Date: Fri, 27 Feb 2009 07:47:21 +0100 [thread overview]
Message-ID: <49A78C79.304@krogh.cc> (raw)
In-Reply-To: <1235687483.6811.26.camel@localhost.localdomain>
john stultz wrote:
> On Thu, 2009-02-26 at 23:06 +0100, Thomas Gleixner wrote:
>> On Thu, 26 Feb 2009, john stultz wrote:
>>> On Thu, 2009-02-26 at 22:35 +0100, Jesper Krogh wrote:
>>>>> Also mind sending the full dmesg for both kernels?
>>>> http://krogh.cc/~jesper/dmesg-2.6.29-rc6.txt
>>>> http://krogh.cc/~jesper/dmesg-2.6.26.8.txt
>>> So one interesting difference:
>>> 2.6.26.8: TSC calibrated against PM_TIMER
>>> 2.6.29-rc6: Fast TSC calibration using PIT
>>>
>>> Thomas, any thoughts as to why we might be calibrating off the PIT
>>> instead of the PM_TIMER w/ 2.6.29?
>> Yup, because we introduced the Fast PIT calibration in 2.6.28.
>
> Ah. Ok.
>
>> Is the delta anything NTP might get upset about:
>>
>> 2.6.26: time.c: Detected 2311.847 MHz processor.
>> 2.6.29: Detected 2310.029 MHz processor.
>
> I wouldn't think so.
>
> Although, I'm recalling on some systems here right after we deploy them
> we'll see something similar to the originally reported ntpd "time reset"
> noise for a period of time while ntpd tries to find the right freq. For
> some reason, I've noticed, having multiple servers in your ntp.conf
> seems to increase NTP's difficulty at picking a time and converging.
>
> So this may be just the slight calibration change is confusing ntp or it
> may be the NTP_INTERVAL_LENGTH change from awhile back which would cause
> the drift value to change could be doing the same thing (although I
> thought that landed in the 2.6.24 timeframe, but I may be forgetting).
>
> I'll kick up some of my own testing between these two releases to see if
> I can't find something similar.
>
> Jesper: How long was the box up for when you noticed the ntpd noise?
I was booted Feb 25 21:58 .. the first noice from ntp starts here:
Feb 25 22:09:53 quad12 ntpd[4901]: synchronized to LOCAL(0), stratum 13
Feb 25 22:09:56 quad12 ntpd[4901]: synchronized to 10.194.133.13, stratum 4
Feb 25 22:14:08 quad12 ntpd[4901]: synchronized to LOCAL(0), stratum 13
Feb 25 22:16:20 quad12 ntpd[4901]: synchronized to 10.194.133.13, stratum 4
Feb 25 22:32:25 quad12 ntpd[4901]: time reset -1.601641 s
Feb 25 22:36:18 quad12 ntpd[4901]: synchronized to LOCAL(0), stratum 13
Feb 25 22:36:45 quad12 ntpd[4901]: synchronized to 10.194.133.12, stratum 4
Feb 25 22:51:41 quad12 ntpd[4901]: time reset -0.922993 s
Feb 25 22:55:05 quad12 ntpd[4901]: synchronized to LOCAL(0), stratum 13
> Also what's the output of the following under the different kernels:
> ntpdc -c peers
> ntpdc -c kerninfo
Working (clocksource=acpi_pm) 2.6.29-rc6
jk@quad02:~$ ntpdc -c kerninfo
pll offset: -0.001577 s
pll frequency: -45.787 ppm
maximum error: 0.066739 s
estimated error: 0.000768 s
status: 0001 pll
pll time constant: 6
precision: 1e-06 s
frequency tolerance: 500 ppm
jk@quad02:~$ ntpdc -c peers
remote local st poll reach delay offset disp
=======================================================================
*hal.nzcorp.net 10.194.132.81 4 64 377 0.00008 0.003752 0.04816
=svn.nzcorp.net 10.194.132.81 4 64 377 0.00009 -0.008724 0.04979
=LOCAL(0) 127.0.0.1 13 64 377 0.00000 0.000000 0.03082
Working (clocksource=tsc) 2.6.26.8
jk@quad03:~$ ntpdc -c kerninfo
pll offset: 0.003208 s
pll frequency: -25.070 ppm
maximum error: 0.833193 s
estimated error: 0.002787 s
status: 4001 pll
pll time constant: 10
precision: 1e-06 s
frequency tolerance: 500 ppm
jk@quad03:~$ ntpdc -c peers
remote local st poll reach delay offset disp
=======================================================================
*hal.nzcorp.net 10.194.132.82 4 1024 377 0.00781 0.006788 0.13666
=sal.nzcorp.net 10.194.132.82 4 1024 377 0.00018 -0.000541 0.12175
=LOCAL(0) 127.0.0.1 13 64 377 0.00000 0.000000 0.03041
Non-working (clocksource=tsc) 2.6.29-rc6
jk@quad12:~$ ntpdc -c kerninfo
pll offset: 0 s
pll frequency: -34.754 ppm
maximum error: 0.023514 s
estimated error: 0 s
status: 0001 pll
pll time constant: 6
precision: 1e-06 s
frequency tolerance: 500 ppm
jk@quad12:~$ ntpdc -c peers
remote local st poll reach delay offset disp
=======================================================================
=hal.nzcorp.net 10.194.132.91 4 64 17 0.00011 -0.069377 0.96895
=trac.nzcorp.net 10.194.132.91 4 64 17 0.00011 -0.096107 0.96904
*LOCAL(0) 127.0.0.1 13 64 17 0.00000 0.000000 0.96857
next prev parent reply other threads:[~2009-02-27 6:47 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 4:31 Linux 2.6.29-rc6 Linus Torvalds
2009-02-23 14:07 ` Linux 2.6.29-rc6 - Fix oops in i915_gem_retire_requests Karsten Wiese
2009-02-26 11:15 ` Linux 2.6.29-rc6 Jesper Krogh
2009-02-26 17:17 ` MTD_CK804XROM warning (Was: Linux 2.6.29-rc6) Marcin Slusarz
2009-02-26 17:53 ` Linux 2.6.29-rc6 Linus Torvalds
2009-02-26 19:22 ` David Woodhouse
2009-02-26 19:31 ` Jesper Krogh
2009-02-26 19:36 ` David Woodhouse
2009-02-26 19:46 ` Jesper Krogh
2009-02-26 19:49 ` David Woodhouse
2009-02-26 20:53 ` Carl-Daniel Hailfinger
2009-02-26 20:32 ` Linus Torvalds
2009-02-26 19:55 ` Jesper Krogh
2009-02-26 20:33 ` Linus Torvalds
2009-02-26 20:43 ` Jesper Krogh
2009-02-26 21:19 ` john stultz
2009-02-26 21:35 ` Jesper Krogh
2009-02-26 21:46 ` john stultz
2009-02-26 21:54 ` Thomas Gleixner
2009-02-26 22:04 ` Jesper Krogh
2009-02-27 6:30 ` Jesper Krogh
2009-03-01 13:51 ` Jesper Krogh
2009-02-26 21:49 ` Linus Torvalds
2009-03-01 15:04 ` Jesper Krogh
2009-02-26 21:54 ` john stultz
2009-02-26 22:06 ` Thomas Gleixner
2009-02-26 22:24 ` Linus Torvalds
2009-02-26 22:31 ` Linus Torvalds
2009-02-26 22:31 ` john stultz
2009-02-26 22:40 ` Linus Torvalds
2009-02-26 22:59 ` john stultz
2009-02-27 7:33 ` Ingo Molnar
2009-02-27 20:50 ` john stultz
2009-02-27 6:47 ` Jesper Krogh [this message]
2009-02-27 20:35 ` john stultz
2009-03-01 20:13 ` Jesper Krogh
2009-03-02 9:53 ` Jesper Krogh
2009-03-02 21:27 ` john stultz
2009-03-03 6:04 ` Jesper Krogh
2009-03-03 19:53 ` john stultz
2009-03-03 20:19 ` Jesper Krogh
2009-03-03 22:22 ` john stultz
2009-03-04 15:30 ` Jesper Krogh
2009-03-04 18:36 ` Jesper Krogh
2009-03-04 18:57 ` John Stultz
2009-03-05 2:39 ` john stultz
2009-03-05 2:52 ` john stultz
2009-03-05 8:43 ` Ingo Molnar
2009-03-06 3:13 ` john stultz
2009-03-06 3:54 ` john stultz
2009-03-06 11:34 ` Ingo Molnar
2009-03-09 20:42 ` Jesper Krogh
2009-03-10 4:26 ` Linus Torvalds
2009-03-10 11:29 ` Thomas Gleixner
2009-03-10 19:42 ` Jesper Krogh
2009-03-10 22:22 ` Thomas Gleixner
2009-03-15 19:53 ` Jesper Krogh
2009-03-16 18:40 ` Jesper Krogh
2009-03-15 1:19 ` Linus Torvalds
2009-03-15 15:44 ` Jesper Krogh
2009-03-15 18:09 ` Linus Torvalds
2009-03-15 18:38 ` Jesper Krogh
2009-03-15 19:02 ` Linus Torvalds
2009-03-15 19:52 ` Jesper Krogh
2009-03-16 18:59 ` Jesper Krogh
2009-03-16 19:32 ` Linus Torvalds
2009-03-17 1:43 ` john stultz
2009-03-17 8:14 ` Ingo Molnar
2009-03-17 15:48 ` Linus Torvalds
2009-03-17 16:13 ` Ingo Molnar
2009-03-17 16:28 ` Linus Torvalds
2009-03-17 16:40 ` Ingo Molnar
2009-03-17 17:28 ` Olivier Galibert
2009-03-21 9:11 ` Jesper Krogh
2009-03-21 10:06 ` Ingo Molnar
2009-03-15 20:32 ` Linus Torvalds
2009-03-03 20:39 ` Jesper Krogh
2009-03-03 22:16 ` john stultz
2009-03-04 5:36 ` Jesper Krogh
2009-03-01 15:09 ` Jesper Krogh
2009-03-01 15:44 ` Linux 2.6.29-rc6 (clocksource) Sitsofe Wheeler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49A78C79.304@krogh.cc \
--to=jesper@krogh.cc \
--cc=johnstul@us.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox