Red Hat Bugzilla – Bug 121246
CPU speed always set to c.a. 600MHZ
Last modified: 2015-01-04 17:05:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312
Description of problem:
I have a HP NX7010 Centrino based laptop.
[root@xo root]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 9
model name : Intel(R) Pentium(R) M processor 1600MHz
stepping : 5
cpu MHz : 598.312
cache size : 1024 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 mce cx8 sep mtrr pge mca cmov
pat clflush dts acpi mmx fxsr sse sse2 tm pbe tm2 est
bogomips : 1185.79
For some strange reason the system decides to start slowing the cpu
down immediatly after booting. I rebooted my machine and checked the
reported cpu speed and it was about 1300 mhz. then it slowly drops
to 598.312 mhz and stays there.
It should be noted that the laptop is docked and on mains power.
Also, this is a Fedora Core test2 (fully up2date via rawhide)
[root@xo root]# cd /sys/devices/system/cpu/cpu0/cpufreq
[root@xo cpufreq]# cat cpuinfo_max_freq
[root@xo cpufreq]# cat cpuinfo_min_freq
[root@xo cpufreq]# cat scaling_available_frequencies
1600000 1400000 1200000 1000000 800000 600000
[root@xo cpufreq]# cat scaling_available_governors
[root@xo cpufreq]# cat scaling_driver
[root@xo cpufreq]# cat scaling_governor
[root@xo cpufreq]# cat scaling_max_freq
[root@xo cpufreq]# cat scaling_min_freq
[root@xo cpufreq]# cat scaling_setspeed
[root@xo cpufreq]# echo 1600000 > scaling_setspeed
[root@xo cpufreq]# grep "cpu MHz" /proc/cpuinfo
cpu MHz : 1595.500
will attach more diagnostics info.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot a centrino based laptop and monitor the CPU speed
Created attachment 99533 [details]
Output from dmesg
Output from dmesg
Created attachment 99534 [details]
Output from lspci -v
Yup :) Fedora Core 1 also does this :) Meaning I've been running
my laptop at 600Mhz from the getgo ;)
I guess this sais more about me than the laptop... :)
I found a service running called "cpuspeed". did a chkconfig cpuspeed
off and rebooted.
[root@xo root]# grep "cpu MHz" /proc/cpuinfo
cpu MHz : 1595.606
Now this slow scaling down to 600 mhz does not happen and I do feel a
This service seems to be starting "/usr/sbin/cpuspeed" that reads
/etc/cpuspeed.conf which is basicly empty on my box (only has VMAJOR=1
and VMINOR=1 that are not comments).
This programs seems to come from the kernel-utils package and has no
man page or other documentation.
I've investigated this and as far as I can see (from the limited help
cpuspeed --help is) all the criteria the program needs to run
correctly are met except I cant find any thermal_zone file on my machine.
[root@xo thermal_zone]# pwd
[root@xo thermal_zone]# ls -l
ok. you guys can shoot me.
I RTFS (the code for cpuspeed) and ofcource its all as it should be.
Something like "dump 0af - / | gzip -9 > /dev/null" will load the CPU
right up and then cpuspeed will kick the CPU directly up to max speed.
I guess the only issue here is that thermal_zone is missing so I cant
so some of the more advanced things here.
cpuspeed looks like something really neat but unfortionately my laptop
doesn't do speedstep (unlike it was advertized ;( ) so I can't test
it's tuning etc myself. If there's something that makes it work better
for you please play around with the settings and let me know....
Arjan, I've been looking at the kernel source and I dont see why the
thermal info is not there. The .configs you ship with the kernel are
From what google tells me the thermal stuff in the Centrino chipset
should work just fine. Should I log a specific case for that issue ?
It's not a CPU thing, it's an ACPI problem. Either your laptop doesn't
report the temperature, or the ACPI implementation doesn't.
ACPI: Processor [CPU0] (supports C1 C2 C3, 8 throttling states)
ACPI: Processor [CPU0] (supports C1 C2, 8 throttling states)
ACPI: Thermal Zone [ATF0] (51 C)
Could you make sure that the "acpi" module is loaded (speedstepping
via ACPI)? If it is, your best bet is to file a bug upstream,
following the instructions at: