From: Dave Jones <davej@redhat.com>
To: Alexander Rajula <chris@nerdmail.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: /proc/cpuinfo reports erroneous CPU frequency. (2.6.23 & 2.6.22)
Date: Mon, 10 Dec 2007 13:04:38 -0500 [thread overview]
Message-ID: <20071210180438.GA22488@redhat.com> (raw)
In-Reply-To: <475C9B06.9000901@nerdmail.nu>
On Mon, Dec 10, 2007 at 02:48:54AM +0100, Alexander Rajula wrote:
> While using 2.6.23 and 2.6.22 (earlier kernels have not been tested) /proc/cpuinfo reports the wrong CPU frequency:
>
>
> While overclocking an AMD Athlon X2 (2GHz) CPU /proc/cpuinfo reports the wrong CPU frequency.
> I am quite puzzled by this.
> Is this an error in the kernel, or is there something strange going on?
cpu frequency scaling relies on static tables in the BIOS that contain
a bunch of predefined frequencies. When you overclock, you're running
at frequencies that aren't in these tables. Everything falls apart as a result.
There's nothing here to fix, don't overclock.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2007-12-10 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 1:48 PROBLEM: /proc/cpuinfo reports erroneous CPU frequency. (2.6.23 & 2.6.22) Alexander Rajula
2007-12-10 2:49 ` Frans Pop
2007-12-10 18:04 ` 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=20071210180438.GA22488@redhat.com \
--to=davej@redhat.com \
--cc=chris@nerdmail.nu \
--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