mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bernhard Schmidt <berni@birkenwald.de>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Clock jumps
Date: Fri, 28 May 2010 02:49:08 +0200	[thread overview]
Message-ID: <4BFF1304.2030605@birkenwald.de> (raw)
In-Reply-To: <1275007605.1813.18.camel@work-vm>

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@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).
>
> 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

  reply	other threads:[~2010-05-28  0:49 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
2010-05-28  0:46                 ` john stultz
2010-05-28  0:49                   ` Bernhard Schmidt [this message]
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=4BFF1304.2030605@birkenwald.de \
    --to=berni@birkenwald.de \
    --cc=johnstul@us.ibm.com \
    --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®