Something has happened to the ondemand cpufreq governor making it close to useless. It almost never increases the frequency, even when running a core at 98% usage (and it was not a nice:d process).
I've seen this on two F11 machines now, and this used to work just fine with earlier releases.
The scaling itself works nicely as it will occasionally jump up to full speed. Performance also works fine, but the difference between ondemand and powersave is more or less non-existent.
Which kernel version? It works just fine for me with 184.108.40.206-43 on an AMD notebook...
Might be a Intel problem. This machine is a Core 2 laptop with the 220.127.116.11-43.fc11.x86_64 kernel. The other machine is a Core 2 workstation with 18.104.22.168-217.2.16.fc11.x86_64.
You can try changing UP_THRESHOLD in /etc/sysconfig/cpuspeed and see if that helps.
I did fiddle with /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold without any real improvement. And I guess UP_THRESHOLD does nothing more than that.
If I'm not mistaken, the threshold used to be 80, not 95 as it is now. I don't remember what the other settings used to be though.
Does it go to full speed if you start more than one cpu-intensive process?
I am hitting this on a four-processor AMD machine, where starting just one process that uses 100% of one CPU does not cause a speed increase.
Hmm... this might be a case of the kernel now lying to userspace. I see a frequency change on the second core on these systems, but these processors are to my knowledge not capable of changing the freq of just one core.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.