From: Tom Sightler <ttsig@tuxyturvy.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: CPUFreq and strange /proc/cpuinfo
Date: Sun, 11 Jan 2004 22:43:09 -0500 [thread overview]
Message-ID: <1073878908.4971.30.camel@localhost.localdomain> (raw)
I've recently upgraded to kernel 2.6.1 (previously 2.6.0) and decided to
try using some of the dynamic cpufreq daemons such as cpufreqd and
powernowd. Both of these seem to work, but there's a strange anomaly in
/proc/cpuinfo. Normally my /proc/cpuinfo had entries like this (only
relavent entries):
model name : Intel(R) Pentium(R) M processor 1700MHz
cpu MHz : 1694.984
bogomips : 3358.72
which looks pretty good I guess, however, once you enable either of
these two daemons these numbers get all confused, for example, when
scaled to full speed I get:
model name : Intel(R) Pentium(R) M processor 1700MHz
cpu MHz : 4802.454
bogomips : 9516.37
and when scaled down to the lowest speed (600Mhz) I get something that
looks like this:
model name : Intel(R) Pentium(R) M processor 1700MHz
cpu MHz : 2824.973
bogomips : 5597.86
I'm not sure if this is just a cosmetic blip or not (it does appear to
be), but I thought it was odd. Any ideas what could cause this or
suggestions how to fix it? Or maybe I should ignore it.
Scaling driver is "centrino".
Later,
Tom
reply other threads:[~2004-01-12 3:43 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=1073878908.4971.30.camel@localhost.localdomain \
--to=ttsig@tuxyturvy.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
all inboxes | Powered by JetHome®