Public bug reported:

This is a regression in Hardy, as this behaviour was not present in
Gutsy

With the upgrade to hardy (and the new 2.6.24 kernel), the cpu frequency
switching started misbehaving quite badly. Regardless of the system
load, the "scaling_max_freq" value will suddently, but quickly, decrease
(pass through all available middle frequencies) until it reaches the
lowest available frequency. Then, it will stay there for a duration of
time (more than 10 minutes), regardless of the system load. During this
time, it is not possible to raise the cpu frequency in any way.
switching the governor from "ondemand" to "performance" has no effect
(probably because of the limiting factor of "scaling_max_freq"). After
this undefined period of time is over, the value of the
"scaling_max_freq" will quickly rise to its maximum value, passing
through each available frequency in between.

This cycle of maximum frequency change repeats indefinitely, at
seemingly random intervals. Furthermore, it is not possible to change
the "scaling_max_freq" value. Although echoing a new valid value with
not produce any errors, a 'cat' immediately after the echo will show the
old value.

This is some information while the cycle is in its minimum phase:
===============================================
:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_available_frequencies 
2201000 2200000 1600000 1200000 800000 
:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_governor 
ondemand
:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_min_freq 
800000
:/sys/devices/system/cpu/cpu0/cpufreq$ cat scaling_max_freq 
800000
:/sys/devices/system/cpu/cpu0/cpufreq$ uptime
                               load average: 1.43, 1.47, 1.45
:/sys/devices/system/cpu/cpu0/cpufreq$ uname -r
2.6.24-19-generic
===============================================

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
"scaling_max_freq" constantly shifting between minimum and maximum frequency
https://bugs.launchpad.net/bugs/242006
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to