Public bug reported:
Using ondemand governor, frequency scaling works as expected when the battery is
in the system, both with A/C plugged in or unplugged. When the bettery is
removed, if the CPU is busy, it keeps running at 1.66GHz,
/sys/devices/system/cpu/cpu[01]/cpufreq/scaling_max_freq shows 1667000. When
the busy job quits, the CPU drops back to 1GHz and
/sys/devices/system/cpu/cpu[01]/cpufreq/scaling_max_freq also changes to 1000000
and can no longer be increased. After reinserting the battery,
/sys/devices/system/cpu/cpu[01]/cpufreq/scaling_max_freq accepts larger
frequencies again.
** Affects: linux (upstream)
Importance: Unknown
Status: Unknown
** Affects: linux-source-2.6.17 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Description changed:
Using ondemand governor, frequency scaling works as expected when the battery
is
in the system, both with A/C plugged in or unplugged. When the bettery is
- removed, if the CPU is busy, it keeps running at 1.83GHz,
+ removed, if the CPU is busy, it keeps running at 1.66GHz,
/sys/devices/system/cpu/cpu[01]/cpufreq/scaling_max_freq shows 1667000. When
the busy job quits, the CPU drops back to 1GHz and
/sys/devices/system/cpu/cpu[01]/cpufreq/scaling_max_freq also changes to
1000000
and can no longer be increased. After reinserting the battery,
/sys/devices/system/cpu/cpu[01]/cpufreq/scaling_max_freq accepts larger
frequencies again.
** Bug watch added: Linux Kernel Bug Tracker #7060
http://bugzilla.kernel.org/show_bug.cgi?id=7060
** Also affects: linux (upstream) via
http://bugzilla.kernel.org/show_bug.cgi?id=7060
Importance: Unknown
Status: Unknown
--
Intel Core Duo stuck at low speed without battery
https://launchpad.net/bugs/75462
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
