From: Bernhard Schmidt <berni@birkenwald.de>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Clock jumps
Date: Fri, 28 May 2010 02:33:03 +0200 [thread overview]
Message-ID: <4BFF0F3F.9050800@birkenwald.de> (raw)
In-Reply-To: <1275004816.1813.15.camel@work-vm>
On 28.05.2010 02:00, john stultz wrote:
Hi John,
> Looking at the diff:
> --- dmesg-lenny 2010-05-27 16:45:33.000000000 -0700
> +++ dmesg-squeeze 2010-05-27 16:46:14.000000000 -0700
> @@ -132,8 +132,8 @@
> console [ttyS1] enabled
> hpet clockevent registered
> Fast TSC calibration using PIT
> -Detected 2660.398 MHz processor.
> -Calibrating delay loop (skipped), value calculated using timer frequency.. 5320.79 BogoMIPS (lpj=10641592)
> +Detected 2613.324 MHz processor.
> +Calibrating delay loop (skipped), value calculated using timer frequency.. 5226.64 BogoMIPS (lpj=10453296)
> Security Framework initialized
> Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
> Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
> @@ -160,7 +160,7 @@
> CPU0: Intel(R) Xeon(R) CPU 3075 @ 2.66GHz stepping 0b
> Booting Node 0, Processors #1
> Brought up 2 CPUs
> -Total of 2 processors activated (10640.79 BogoMIPS).
> +Total of 2 processors activated (10546.63 BogoMIPS).
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
>
> So you can see in the above the during the second boot the TSC
> calibration was badly mis-calculated. This was the cause of the skew.
>
> Not sure how that might be linked to the distro upgrade. It could have
> been something like SMI damage during the calibration time, but I
> thought the calibration loop watched for that.
>
> Bernhard: I expect with all those vms, this machine isn't rebooted
> frequently. So could you look at the logs to see how much the "Detected
> xxxx.yyy MHz processor." line varies by across a few other boots (if
> they still exist?).
Correct, the box isn't rebooted often, but I do have a few dmesg outputs
laying around. lpj was always almost the same until the very last boot
which screwed up the clock.
dmesg:[ 0.000000] Linux version 2.6.33 (root@svr02) (gcc version
4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Sun Mar 7 23:01:45 CET 2010
dmesg:[ 0.008005] Calibrating delay loop (skipped), value calculated
using timer frequency.. 5226.64 BogoMIPS (lpj=10453296)
dmesg:[ 0.288002] Total of 2 processors activated (10546.63 BogoMIPS).
dmesg.0:[ 0.000000] Linux version 2.6.33 (root@svr02) (gcc version
4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Sun Mar 7 23:01:45 CET 2010
dmesg.0:[ 0.008005] Calibrating delay loop (skipped), value
calculated using timer frequency.. 5320.79 BogoMIPS (lpj=10641592)
dmesg.0:[ 0.274022] Total of 2 processors activated (10640.79 BogoMIPS).
dmesg.1.gz:[ 0.000000] Linux version 2.6.32-rc7 (root@svr02) (gcc
version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Thu Nov 19 14:36:03 CET 2009
dmesg.1.gz:[ 0.012004] Calibrating delay loop (skipped), value
calculated using timer frequency.. 5319.06 BogoMIPS (lpj=10638120)
dmesg.1.gz:[ 0.016000] Calibrating delay using timer specific
routine.. 5319.99 BogoMIPS (lpj=10639980)
dmesg.1.gz:[ 0.260003] Total of 2 processors activated (10639.05
BogoMIPS).
dmesg.2.gz:[ 0.000000] Linux version 2.6.32-rc7 (root@svr02) (gcc
version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Thu Nov 19 14:36:03 CET 2009
dmesg.2.gz:[ 0.012005] Calibrating delay loop (skipped), value
calculated using timer frequency.. 5319.35 BogoMIPS (lpj=10638712)
dmesg.2.gz:[ 0.016000] Calibrating delay using timer specific
routine.. 5319.99 BogoMIPS (lpj=10639990)
dmesg.2.gz:[ 0.261567] Total of 2 processors activated (10639.35
BogoMIPS).
dmesg.3.gz:[ 0.000000] Linux version 2.6.32-rc7 (root@svr02) (gcc
version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Thu Nov 19 14:36:03 CET 2009
dmesg.3.gz:[ 0.012005] Calibrating delay loop (skipped), value
calculated using timer frequency.. 5319.97 BogoMIPS (lpj=10639956)
dmesg.3.gz:[ 0.016000] Calibrating delay using timer specific
routine.. 5319.99 BogoMIPS (lpj=10639987)
dmesg.3.gz:[ 0.257152] Total of 2 processors activated (10639.97
BogoMIPS).
dmesg.4.gz:[ 0.000000] Linux version 2.6.32-rc7 (root@svr02) (gcc
version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Thu Nov 19 14:36:03 CET 2009
dmesg.4.gz:[ 0.012005] Calibrating delay loop (skipped), value
calculated using timer frequency.. 5319.84 BogoMIPS (lpj=10639688)
dmesg.4.gz:[ 0.016000] Calibrating delay using timer specific
routine.. 5319.99 BogoMIPS (lpj=10639993)
dmesg.4.gz:[ 0.253571] Total of 2 processors activated (10639.84
BogoMIPS).
If necessary I can reboot once more, but I'd like to avoid it.
Bernhard
next prev parent reply other threads:[~2010-05-28 0:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 16:06 Orion Poplawski
2010-05-25 6:21 ` Gleb Natapov
2010-05-26 17:10 ` Orion Poplawski
2010-05-26 17:31 ` Alexander Graf
2010-05-26 17:50 ` Orion Poplawski
2010-05-26 22:55 ` Orion Poplawski
2010-05-27 18:32 ` Bernhard Schmidt
2010-05-27 19:08 ` john stultz
2010-05-27 21:48 ` Bernhard Schmidt
2010-05-28 0:00 ` john stultz
2010-05-28 0:33 ` Bernhard Schmidt [this message]
2010-05-28 0:46 ` john stultz
2010-05-28 0:49 ` Bernhard Schmidt
2010-05-27 21:53 ` Zachary Amsden
2010-05-27 22:12 ` Bernhard Schmidt
2010-05-27 22:20 ` Zachary Amsden
2010-05-27 22:22 ` Zachary Amsden
2010-06-02 22:54 ` Orion Poplawski
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=4BFF0F3F.9050800@birkenwald.de \
--to=berni@birkenwald.de \
--cc=johnstul@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®