cpufreq stops working after a while
One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor. This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
Sometimes rebooting doesn't even restore it.
/sys/devices/system/cpu/cpu0/cpufreq is all very normal looking, showing the available frequencies and other info. All of the attribs there look fine, except for "scaling_max_freq", which is what seems to gradually get set smaller. For instance, right now it is set to 800000, and it won't let me change it (echo 11000000 > scaling_max_freq has no effect.
WHY? And how can I fix it?
Quoted 10 lines · Mark Lord
One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor. This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
Sometimes rebooting doesn't even restore it.
Quoted 7 lines
/sys/devices/system/cpu/cpu0/cpufreqis all very normal looking, showing the available frequencies and other info. All of the attribs there look fine, except for "scaling_max_freq", which is what seems to gradually get set smaller. For instance, right now it is set to 800000, and it won't let me change it (echo 11000000 >scaling_max_freqhas no effect.WHY? And how can I fix it?
boot with cpufreq.debug=7, and capture dmesg output after it fails to transition. This might be another manifestation of the mysterious "highest frequency isnt accessable" bug, that seems to come from some recent change in acpi.
Dave
Signature · 1 line
http://www.codemonkey.org.uk
Quoted 10 lines · On Fri, 11 Aug 2006 14:25:26 -0400 Mark Lord <[email protected]> wrote:
One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor. This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
Sometimes rebooting doesn't even restore it.
Quoted 7 lines
/sys/devices/system/cpu/cpu0/cpufreqis all very normal looking, showing the available frequencies and other info. All of the attribs there look fine, except for "scaling_max_freq", which is what seems to gradually get set smaller. For instance, right now it is set to 800000, and it won't let me change it (echo 11000000 >scaling_max_freqhas no effect.WHY?
cpufreq seems to have relatively frequent problems.
Quoted 1 line
And how can I fix it?
You could start by telling us which kernel versions are affected ;)
Quoted 1 line · Andrew Morton
Mark Lord <[email protected]> wrote:
..
Quoted 4 lines
Quoted 4 lines
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
..
Quoted 7 lines
Quoted 1 line
WHY?
cpufreq seems to have relatively frequent problems.
Quoted 1 line
And how can I fix it?
You could start by telling us which kernel versions are affected ;)
Heh. 2.6.17.6 and 2.6.18-rc3-git4 are the two kernels I have for it, and both exhibit the problem.
Quoted 1 line · Dave Jones
boot with cpufreq.debug=7, and capture dmesg output after it fails
I'll reboot with the debug options and see..
Cheers
Quoted 19 lines · Andrew Morton
Quoted 16 lines · On Fri, 11 Aug 2006 14:25:26 -0400 Mark Lord <[email protected]> wrote:
One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor. This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
Sometimes rebooting doesn't even restore it.
/sys/devices/system/cpu/cpu0/cpufreqis all very normal looking, showing the available frequencies and other info. All of the attribs there look fine, except for "scaling_max_freq", which is what seems to gradually get set smaller. For instance, right now it is set to 800000, and it won't let me change it (echo 11000000 >scaling_max_freqhas no effect.
Quoted 7 lines
Quoted 1 line
WHY?
cpufreq seems to have relatively frequent problems.
Quoted 1 line
And how can I fix it?
You could start by telling us which kernel versions are affected ;)
Mmm.. since it appears to be related, kbuild dumps this out when building the kernel:
WARNING: drivers/acpi/processor.o - Section mismatch: reference to .init.data: from .text between 'acpi_processor_power_init' (at offset 0xf29) and 'acpi_processor_cst_has_changed'
A possible source for the bug, or total red herring ?
Quoted 6 lines · On Fri, 11 Aug 2006 15:10:16 -0400 Mark Lord <[email protected]> wrote:
Quoted 6 lines
Quoted 1 line
WHY?
cpufreq seems to have relatively frequent problems.
Quoted 1 line
And how can I fix it?
Quoted 8 lines
Quoted 1 line
You could start by telling us which kernel versions are affected ;)
Mmm.. since it appears to be related, kbuild dumps this out when building the kernel:
WARNING:
drivers/acpi/processor.o- Section mismatch: reference to .init.data: from .text between 'acpi_processor_power_init' (at offset0xf29) and 'acpi_processor_cst_has_changed'A possible source for the bug, or total red herring ?
An RH. acpi_processor_power_init() is actually non-buggy, due to its interesting games with `first_run'.
A section error would usually trigger a wild oops if you're affected by it.
Quoted 5 lines · Dave Jones
boot with cpufreq.debug=7, and capture dmesg output after it fails to transition. This might be another manifestation of the mysterious "highest frequency isnt accessable" bug, that seems to come from some recent change in acpi.
booting with that option doesn't seem to give me any new messages in dmesg (or /var/log/messages). I also tried editing cpufreq.c and hardcoding debug = 7 on the variable declaration. Still no new messages.
??
Quoted 11 lines · Mark Lord
Quoted 5 lines · Dave Jones
boot with cpufreq.debug=7, and capture dmesg output after it fails to transition. This might be another manifestation of the mysterious "highest frequency isnt accessable" bug, that seems to come from some recent change in acpi.
booting with that option doesn't seem to give me any new messages in dmesg (or
/var/log/messages). I also tried editingcpufreq.cand hardcoding debug = 7 on the variable declaration. Still no new messages.
Mmm.. that's interesting.. this time, the scaling_max_freq went back up to 1100000 all by itself after a longish idle period, before which it had dropped to 800000 and got "stuck" there.
Currently using the "ondemand" governor -- it doesn't seem to call the central cpufreq_debug_printk() thingie from cpufreq.c.
I did hack cpufreq_debug_printk() to force output anytime it gets called, but still no new output in the logs.
Cheers
Quoted 17 lines · Mark Lord
Quoted 11 lines · Mark Lord
Quoted 5 lines · Dave Jones
boot with cpufreq.debug=7, and capture dmesg output after it fails to transition. This might be another manifestation of the mysterious "highest frequency isnt accessable" bug, that seems to come from some recent change in acpi.
booting with that option doesn't seem to give me any new messages in dmesg (or
/var/log/messages). I also tried editingcpufreq.cand hardcoding debug = 7 on the variable declaration. Still no new messages.Mmm.. that's interesting.. this time, the
scaling_max_freqwent back up to 1100000 all by itself after a longish idle period, before which it had dropped to 800000 and got "stuck" there.
Quoted 5 lines
Currently using the "ondemand" governor -- it doesn't seem to call the central
cpufreq_debug_printk()thingie fromcpufreq.c.I did hack
cpufreq_debug_printk()to force output anytime it gets called, but still no new output in the logs.
Do you have CONFIG_CPU_FREQ_DEBUG enabled ?
Dave
Signature · 1 line
http://www.codemonkey.org.uk
Quoted 7 lines · On Fri, 11 Aug 2006 14:25:26 -0400 Mark Lord <[email protected]> wrote:
One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor. This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
Can't it be TM2 pulling the handbrake?
_______________________________________________
Cpufreq mailing list
[email protected]
http://lists.linux.org.uk/mailman/listinfo/cpufreq
Quoted 9 lines · Erik Slagter
Quoted 7 lines · On Fri, 11 Aug 2006 14:25:26 -0400 Mark Lord <[email protected]> wrote:
One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor. This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
After a few hours, urgh.
Dells limit their frequency to lowest after unplugging AC and allow all freqs after some time (some secs) again.
There were two issues solved on the Dells some months ago:
- The frequency after you unplug AC adapter is already reduced by BIOS, that confused the cpufreq driver.
- There was a race in sysfs writes. If you e.g. change governor or possibly some other cpufreq related sysfs file while the frequency got limited by BIOS, the real max freq value got overridden by the temporarily limited max freq value and you are stuck to lowest freq forever.
Do you use any userspace daemon (cpuspeed, powersaved, ...) to control cpuspeed?
If yes, you should first try without. It should be enough to:
- load your hw cpufreq module
- load the ondemand governor module
- echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
If it still happens we know at least it can't be some kind of sysfs race again or userspace tools do not remember the wrong max_freq value. Then some debug output or how to reproduce this a bit faster would be nice...
Maybe with something like that:
LOAD_FACTOR=40 # adjust this one to the power of your machine to let
# cpufreq switch up and down, or if it does not switch
# up and down in the beginning it should stay at
# 800 (could be 5-20 on yours?),
# check with (in separate console):
# cd /sys/devices/system/cpu/cpu0/cpufreq/
# watch -n1 cat scaling_cur_freq scaling_max_freqfor ((x=200;x<1000;x+=5));do
# give load
for ((y=0;y<$LOAD_FACTOR;y++)); do
echo "10 k 2 v p" |dc >/dev/null
done;
# then sleep
usleep $((x*1000)) # maybe the right value here triggers the bug?
echo "sleep $x milli secs"
done;Maybe it's triggered if you start some other process(es) while this is running?
Thomas
Quoted 10 lines · Thomas Renninger
Quoted 9 lines · Erik Slagter
Quoted 7 lines · On Fri, 11 Aug 2006 14:25:26 -0400 Mark Lord <[email protected]> wrote:
One of my notebooks (Dell Latitude X1) has a 1.1GHz Pentium-M ULV processor. This chip can change CPU speeds from 600 -> 800 -> 1100 Mhz.
I use speedstep-centrino with it, and after boot all is usually okay. But after a few hours of operation, it stops shifting to the highest frequency even under continuous 100% load (or not). Eventually it gets stuck at 600Mhz and stays there until I reboot.
I have the same problem. My laptop is Dell Latitude D600 (Intel(R) Pentium(R) M processor 1.60GHz). If I'm compiling something, for example, that takes a long time, scaling_max_freq is set to 600000 (the lowest). If I try to echo 1600000 to scaling_max_freq it do nothing. Only after some time if the cpu load is not high I can echoing 1600000 again and it works without need to reboot.
Quoted 15 lines
After a few hours, urgh.
Dells limit their frequency to lowest after unplugging AC and allow all freqs after some time (some secs) again.
There were two issues solved on the Dells some months ago:
- The frequency after you unplug AC adapter is already reduced by BIOS, that confused the cpufreq driver.
- There was a race in sysfs writes. If you e.g. change governor or possibly some other cpufreq related sysfs file while the frequency got limited by BIOS, the real max freq value got overridden by the temporarily limited max freq value and you are stuck to lowest freq forever.
Quoted 2 lines
Do you use any userspace daemon (cpuspeed, powersaved, ...) to control cpuspeed?
In my case I use conservative governor and kernel version is 2.6.18-rc4.
Quoted 8 lines
If yes, you should first try without. It should be enough to:
- load your hw cpufreq module
- load the ondemand governor module
- echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governorIf it still happens we know at least it can't be some kind of sysfs race again or userspace tools do not remember the wrong
max_freqvalue. Then some debug output or how to reproduce this a bit faster would be nice...
It happens to me every time I try to compile something that takes a long time (evolution, mozilla, even kernel)
Quoted 29 lines
Maybe with something like that:
LOAD_FACTOR=40 # adjust this one to the power of your machine to let# cpufreq switch up and down, or if it does not switch # up and down in the beginning it should stay at # 800 (could be 5-20 on yours?), # check with (in separate console): # cd /sys/devices/system/cpu/cpu0/cpufreq/ # watch -n1 cat scaling_cur_freq scaling_max_freqfor ((x=200;x<1000;x+=5));do
# give load for ((y=0;y<$LOAD_FACTOR;y++)); do echo "10 k 2 v p" |dc >/dev/null done; # then sleep usleep $((x*1000)) # maybe the right value here triggers the bug? echo "sleep $x milli secs" done;Maybe it's triggered if you start some other process(es) while this is running?
Thomas
_______________________________________________
Cpufreq mailing list
[email protected]
http://lists.linux.org.uk/mailman/listinfo/cpufreq
Signature · 5 lines
Carlos Garcia Campos (KaL) [email protected] [email protected] http://carlosgc.linups.org PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462
_______________________________________________
Cpufreq mailing list
[email protected]
http://lists.linux.org.uk/mailman/listinfo/cpufreq