From: Simon <simon@highlyillogical.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.0-test10] cpufreq: 2G P4M won't go above 1.2G - cpuinfo_max_freq too low
Date: Thu, 27 Nov 2003 11:39:07 +0000 [thread overview]
Message-ID: <200311271139.07260.simon@highlyillogical.org> (raw)
Sorry... I posted this to the cpufreq list yesterday but I didn't get a
response. Apologies for crossposting.
I've just upgraded to 2.6.0-test10 and am trying to use the new cpufreq stuff
in there. I had everything working perfectly with 2.4.21-ac2, and the old
/proc/cpufreq interface.
I have a P4 2ghz (in a thinkpad), but it's not running at over about 1.2ghz
now. If I `cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq` it
tells me: "1198976". It should go faster than that. Similarly,
scaling_available_frequencies says "149872 299744 449616 599488 749360 899232
1049104 1198976"
Enabling the old interface in the kernel and doing a `echo -n
0%0%100%performance > /proc/cpufreq` doesn't change things either.
Here is my /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz
stepping : 7
cpu MHz : 1198.976
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid
bogomips : 2359.29
Any ideas?
Cheers,
Simon
next reply other threads:[~2003-11-27 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 11:39 Simon [this message]
2003-11-27 12:18 ` [2.6.0-test10] cpufreq: 2G P4M won't go above 1.2G - cpuinfo_max_freq too low Marco Roeland
2003-11-27 13:23 ` Simon
2003-11-27 13:42 ` Marco Roeland
2003-11-27 14:57 ` Simon
2003-11-27 15:23 ` Marco Roeland
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=200311271139.07260.simon@highlyillogical.org \
--to=simon@highlyillogical.org \
--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