From: Jeff Garzik <jgarzik@pobox.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: My P3 runs at.... zero Mhz (bug rpt)
Date: Thu, 17 Apr 2003 22:10:53 -0400 [thread overview]
Message-ID: <3E9F5EAD.2070006@pobox.com> (raw)
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. :)
2.4.x reports the Mhz correctly. I don't recall if 2.5.x did in the
past, but can check if needed.
sh-2.05b$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 0.000
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
cmov pat pse36 mmx fxsr sse
bogomips : 494.59
Selected dmesg bits:
Calibrating delay loop... 494.59 BogoMIPS
Memory: 644596k/655296k available (2192k kernel code, 9960k reserved,
694k data, 296k init, 0k highmem)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU serial number disabled.
CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel Pentium III (Katmai) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
IA-32 Microcode Update Driver: v1.11 <tigran@veritas.com>
Enabling SEP on CPU 0
next reply other threads:[~2003-04-18 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 2:10 Jeff Garzik [this message]
2003-04-18 4:44 ` My P3 runs at.... zero Mhz (bug rpt) Jurriaan
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=3E9F5EAD.2070006@pobox.com \
--to=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 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.