From: Simon Detheridge <simon@symdata.com>
To: Thomas Renninger <trenn@suse.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: 2G P4M won't go above 1.2 - cpuinfo_max_freq too low
Date: Thu, 4 Dec 2003 16:21:53 +0000 [thread overview]
Message-ID: <200312041621.54171.simon@symdata.com> (raw)
In-Reply-To: <3FCF542B.9040703@suse.de>
I wrote:
> 2G P4M won't go above 1.2 - cpuinfo_max_freq too low
Thomas Renninger wrote:
> I have the same problem, cpuinfo shows the wrong value!!!
> I get 1200MHz even I set it up to 1800MHz.
> (posted prog calculates the right value, (procspeed))
Odd. My CPU was definitely running at the slower speed. It wasn't just being
misreported by /proc/cpuinfo
I fixed the problem by compiling all the cpufreq stuff as modules (I had
everything compiled into the kernel before) and loading them one-by-one. It
turns out that my kernel was choosing p4-clockmod by default, which was not
behaving correctly. Manually loading speedstep_ich fixed the problem.
Simon
next prev parent reply other threads:[~2003-12-04 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 17:02 2G P4M won't go above 1.2 - cpuinfo_max_freq too low Simon
2003-12-04 15:35 ` Thomas Renninger
2003-12-04 16:21 ` Simon Detheridge [this message]
2003-12-09 18:13 ` Anatoli Gorchetchnikov
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=200312041621.54171.simon@symdata.com \
--to=simon@symdata.com \
--cc=cpufreq@www.linux.org.uk \
--cc=trenn@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.