linux-kernel - Re: cpufreq scaling appears not to work on overclocked systems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070729233428.GA405@redhat.com>
Date:	Sun, 29 Jul 2007 19:34:28 -0400
From:	Dave Jones <davej@...hat.com>
To:	"Berck E. Nash" <flyboy@...il.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: cpufreq scaling appears not to work on overclocked systems

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/