From: <WHarms@bfs.de> (Walter Harms)
To: <linux-kernel@vger.kernel.org>
Subject: inconsistant speed reporting
Date: Sun, 27 Jul 2003 18:14:06 +0200 [thread overview]
Message-ID: <vines.sxdD+Cdz6zA@SZKOM.BFS.DE> (raw)
hi all,
i have noticed that the processor speed reported by the kernel is different. Here is a list that i have compiled on my notebook:
dmesg.2.4.19: Detected 999.906 MHz processor.
dmesg.2.4.21: Detected 1019.778 MHz processor.
dmesg.2.6.0: Detected 999.927 MHz processor.
dmesg.2.6.0-a3: Detected 999.903 MHz processor.
ACPI:
dmesg.2.4.21:..... CPU clock speed is 999.9308 MHz.
dmesg.2.6.0:..... CPU clock speed is 1329.0655 MHz.
dmesg.2.6.0-a3:..... CPU clock speed is 1329.0620 MHz.
ACPI:
dmesg.2.4.21:..... host bus clock speed is 133.3240 MHz.
dmesg.2.6.0:..... host bus clock speed is 177.0287 MHz.
dmesg.2.6.0-a3:..... host bus clock speed is 177.0282 MHz.
notebook:
acer tm 620
with
CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz stepping 01
btw: thx to the ACPI team without the ACPI patch (for 2.4.x)
its not possible to use the nb propperly.
walter
reply other threads:[~2003-07-27 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vines.sxdD+Cdz6zA@SZKOM.BFS.DE \
--to=wharms@bfs.de \
--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;
as well as URLs for NNTP newsgroup(s).