From: Dave Jones <davej@redhat.com>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: cpufreq scaling appears not to work on overclocked systems
Date: Sun, 29 Jul 2007 19:34:28 -0400 [thread overview]
Message-ID: <20070729233428.GA405@redhat.com> (raw)
In-Reply-To: <46AD03BD.7040203@gmail.com>
On Sun, Jul 29, 2007 at 03:16:45PM -0600, Berck E. Nash wrote:
> I'm running a Core2 Duo 1.86GHz overclocked to 2.56GHz. Everything is
> normal with cpufreq scaling disabled. With cpufreq scaling enabled in
> the kernel, using any governor, /proc/cpuinfo indicates a maximum of the
> rated frequency rather than the actual frequency.
FAQ.
The BIOS contains hard coded tables of frequencies.
Just because you changed the clocks on which those tables
are based doesn't mean the tables will change.
Not a bug.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2007-07-29 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 21:16 cpufreq scaling appears not to work on overclocked systems Berck E. Nash
2007-07-29 23:34 ` Dave Jones [this message]
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=20070729233428.GA405@redhat.com \
--to=davej@redhat.com \
--cc=flyboy@gmail.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