[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BFF1304.2030605@birkenwald.de>
Date: Fri, 28 May 2010 02:49:08 +0200
From: Bernhard Schmidt <berni@...kenwald.de>
To: john stultz <johnstul@...ibm.com>
CC: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: Clock jumps
On 28.05.2010 02:46, john stultz wrote:
[ dropped kvm ml ]
Hi John,
>> 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@...02) (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).
>
> Yea. The bogomips/loops per jiffies are actually calculated with a
> different chunk of code (although its interesting it miscalculated in
> both cases).
>
> Could you send the "Detected xxxx.yyy MHz processor." lines as well?
Sure...
dmesg:[ 0.000000] Detected 2613.324 MHz processor.
dmesg.0:[ 0.000000] Detected 2660.398 MHz processor.
dmesg.1.gz:[ 0.000000] Detected 2659.530 MHz processor.
dmesg.2.gz:[ 0.000000] Detected 2659.678 MHz processor.
dmesg.3.gz:[ 0.000000] Detected 2659.989 MHz processor.
dmesg.4.gz:[ 0.000000] Detected 2659.922 MHz processor.
Bernhard
--
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/
Powered by blists - more mailing lists