From: Frans Pop <elendil@planet.nl>
To: jplatte@naasa.net
Cc: Kasper Sandberg <lkml@metanurb.dk>, linux-kernel@vger.kernel.org
Subject: Re: cpuinfo shows wrong MHz value
Date: Sun, 15 Feb 2009 17:41:29 +0100 [thread overview]
Message-ID: <200902151741.30303.elendil@planet.nl> (raw)
In-Reply-To: <200902150811.36826.jplatte@naasa.net>
On Sunday 15 February 2009, Joerg Platte wrote:
> Looks like p4_clockmod is responsible for these high values. After
> removing it /proc/cpuinfo shows the correct values:
Can you check whether or not you were also using p4-clockmode with the
last kernel that did show correct values? The same grep command should
show this.
It would also help to know which kernel version was the last working one.
You mentioned 2.6.26, but with some uncertainty. Can you check for 2.6.26
and possibly for 2.6.27?
Note that p4-clockmode does not really help with power saving, but only
with thermal management (prevention of overheating). Possibly the
speedstep or acpi-cpufreq modules will work better for you, but it can
also be they don't support your processor.
That does not mean this issue should not be looked into of course.
next prev parent reply other threads:[~2009-02-15 16:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 21:17 cpuinfo shows wrong MHz value Joerg Platte
2009-02-14 22:29 ` Frans Pop
2009-02-14 22:38 ` Kasper Sandberg
2009-02-14 22:46 ` Frans Pop
2009-02-14 23:22 ` Joerg Platte
2009-02-15 0:02 ` Frans Pop
2009-02-15 7:00 ` Joerg Platte
2009-02-15 7:11 ` Joerg Platte
2009-02-15 16:41 ` Frans Pop [this message]
2009-02-16 14:19 ` Thomas Renninger
2009-02-16 16:50 ` Matthew Garrett
2009-02-16 18:13 ` Thomas Renninger
2009-02-16 18:19 ` Matthew Garrett
2009-02-16 18:47 ` Thomas Renninger
2009-02-16 18:52 ` Frans Pop
2009-02-16 19:01 ` Matthew Garrett
2009-02-18 19:54 ` Joerg Platte
2009-02-18 21:05 ` Frans Pop
2009-02-19 17:03 ` Joerg Platte
2009-02-20 2:52 ` Frans Pop
2009-02-20 18:42 ` Joerg Platte
2009-02-15 17:43 ` Frans Pop
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=200902151741.30303.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=jplatte@naasa.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
/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