public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hunt <oliverhunt@gmail.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Romain Moyne <aero_climb@yahoo.fr>, linux-kernel@vger.kernel.org
Subject: Re: Time runs exactly three times too fast
Date: Thu, 2 Sep 2004 00:32:09 +1200	[thread overview]
Message-ID: <4699bb7b04090105323c2d69b8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409010826500.4481@montezuma.fsmlabs.com>

On Wed, 1 Sep 2004 08:28:02 -0400 (EDT), Zwane Mwaikambo
<zwane@linuxpower.ca> wrote:
> On Thu, 2 Sep 2004, Oliver Hunt wrote:
> 
> > Is it just me or the bogomips rating listed there completely out of whack?
> 
> Yes it is, you'll also note that the cpu clock frequency is also low,
> hence my suspicion of cpufreq, which would affect general timing.
> 

Oops, I hadn't noticed that :)

Perhaps one of the cpu specific options in the config? 
Sadly I can't remember what options there are, and the last 2.6 kernel
compile I did was with 2.6.3 or 4 so there may be new options, but I
can't think of anything that could conceivably cause weirdness in the
clock speed detection...

--Oliver

  reply	other threads:[~2004-09-01 12:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 12:53 Time runs exactly three times too fast Romain Moyne
2004-09-01 12:15 ` Zwane Mwaikambo
2004-09-01 12:18   ` Oliver Hunt
2004-09-01 12:28     ` Zwane Mwaikambo
2004-09-01 12:32       ` Oliver Hunt [this message]
2004-09-02 14:14   ` Romain Moyne
2004-09-01 12:32     ` Dave Jones
2004-09-01 12:35     ` Zwane Mwaikambo
2004-09-02 15:08       ` Romain Moyne
2004-09-01 13:00         ` Dave Jones
2004-09-02 16:31           ` Romain Moyne
2004-09-01 13:14             ` Dave Jones
2004-09-01 13:58             ` Paul Rolland
2004-09-01 20:19 ` john stultz
2004-09-02  5:46   ` Oliver Hunt
2004-09-02 18:18     ` john stultz

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=4699bb7b04090105323c2d69b8@mail.gmail.com \
    --to=oliverhunt@gmail.com \
    --cc=aero_climb@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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