Most recent kernel where this bug did not occur:
Hardware Environment: IBM T42
Software Environment: Debian GNU/Linux 4.0 (kernel 2.6.21)
When the system boots up (freshly), the cpu frequency (governer conservative) works properly and switches the cpu speed smoothly from low to high and viceversa based on the application using the system
When the system is suspended to disk, and the system comes back after suspend, the conservative governer stops working. Occasionally it starts working after a very long time
Steps to reproduce:
Can you try a bit more.., e.g.:
does it work with ondemand governor
after conservative governor broke, does switching to other governors, e.g. powersave, performance still work?
These are the easy to test..., if you know how to compile and a kernel it would be great if you could test the latest 188.8.131.52 or -git kernel. Then also enable CONFIG_CPU_FREQ_DEBUG=y (or similar), boot with cpufreq.debug=7 (or enable it at runtime: "echo 7 >/sys/module/cpufreq/parameters/debug") and attach syslog/klog output.
Not sure, but I think I saw a report with ondemand governor breaking away after suspend..., I try to find it.
This bug is a duplicate of #8581. If you're alright with compiling
your own kernel, please try the patch I've uploaded to fix #8581.
*** This bug has been marked as a duplicate of bug 8581 ***