public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurriaan <thunder7@xs4all.nl>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: My P3 runs at.... zero Mhz (bug rpt)
Date: Fri, 18 Apr 2003 06:44:54 +0200	[thread overview]
Message-ID: <20030418044454.GA5349@middle.of.nowhere> (raw)
In-Reply-To: <3E9F5EAD.2070006@pobox.com>

From: Jeff Garzik <jgarzik@pobox.com>
Date: Thu, Apr 17, 2003 at 10:10:53PM -0400
> Just booted into 2.5.67-BK-latest (plus my __builtin_memcpy patch). 
> Everything seems to be running just fine, so naturally one must nitpick 
> little things like being told my CPU is running at 0.000 Mhz.  :)
> 
fwiw, my Athlon XP2400 does the same in 2.5.67-ac1:

processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 6
model		: 8
model name	: AMD Athlon(tm) XP 2400+
stepping	: 1
cpu MHz		: 0.000
cache size	: 256 KB
bogomips	: 1970.17

Interesting enough, even the bogomips have halved w.r.t. earlier 2.5.x
kernels and 2.4.2x kernels. Booting a 2.4.21-pre7 kernel on the same
machine gets me close to 4000 bogomips, as is proper for a 2 GHz cpu.

The ioapic code does report the correct bus-speed however.

Ah well, they were bogus to begin with.
-- 
"I am not to be trifled with!"
"I didn't bring a trifle," Hawk said to Fisher. "Did you think to
bring a trifle?" "Knew I forgot something," said Fisher.
	Simon R Green - Beyond the Blue Moon
Debian (Unstable) GNU/Linux 2.5.67-ac1 1970 bogomips load av: 1.48 1.62 1.79

  reply	other threads:[~2003-04-18  4:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18  2:10 My P3 runs at.... zero Mhz (bug rpt) Jeff Garzik
2003-04-18  4:44 ` Jurriaan [this message]
2003-04-18 21:11   ` Dave Jones
2003-04-18 21:44     ` Petr Konecny
2003-04-18 23:50       ` Alan Cox
2003-04-19  0:07         ` Jeff Garzik
2003-04-18  5:08 ` [patch] mach_countup() fix Andrew Morton

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=20030418044454.GA5349@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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