All of lore.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:18:35 +1200	[thread overview]
Message-ID: <4699bb7b04090105182c5591a9@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409010814580.4481@montezuma.fsmlabs.com>

Is it just me or the bogomips rating listed there completely out of whack?

I'll note however I don't have a kernel 2.6 box lying anywhere nearby,
but I shouldn't have thought the way the bogomips rating is counted
would have changed.

Anyhoo my understanding is that bogomips are used for timing in a few
obscure circumstances -- maybe this could be causing the problems?  (I
would have though about 10x higher would be more correct)

--Oliver Hunt

On Wed, 1 Sep 2004 08:15:55 -0400 (EDT), Zwane Mwaikambo
<zwane@linuxpower.ca> wrote:
> On Thu, 2 Sep 2004, Romain Moyne wrote:
> 
> > Hello, I'm french, sorry for my bad english :(
> >
> > I have a problem with my kernel: Time runs exactly three times too fast.
> >
> > I tested the kernel 2.6.8.1 and the 2.6.9-rc1, no success.
> > It is really strange because yesterday I reinstalled my debian with a kernel
> > 2.6.8.1 (made by me): Time ran correctly. And this morning when I rebooted my
> > computer (Compaq presario R3000 series, R3215EA exactly) the time is running
> > again three times too fast (with the kernel 2.6.8.1 and 2.6.9-rc1).
> >
> > All my applications (KDE, command "date"...) runs three times too fast. It's
> > very annoying.
> 
> Can you try this without cpuspeed or some frequency control daemon
> running? So disable it in runlevel scripts and then reboot.
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

  reply	other threads:[~2004-09-01 12:18 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 [this message]
2004-09-01 12:28     ` Zwane Mwaikambo
2004-09-01 12:32       ` Oliver Hunt
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=4699bb7b04090105182c5591a9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.