Skip to contentSkip to conversation

acpi-cpufreq doesn't detect speed limit when cold booted on battery

Bug 12389 [email protected] 1 participant 3 messages Nov 5, 2010 – Nov 6, 2010 1 message not in the archive

lore
Share & tools
lore
#3 lore raw
In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=12389

Thomas Renninger <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |NEEDINFO
                 CC|                            |[email protected]
          Component|cpufreq                     |Config-Processors
         AssignedTo|[email protected]     |acpi_config-processors@kern
                   |                            |el-bugs.osdl.org
            Product|Power Management            |ACPI

--- Comment #3 from Thomas Renninger <[email protected]> 2010-11-06 20:04:54 --- This should be an ACPI, not a cpufreq bug.
Some things you could check:
- BIOS up-to-date?
- Is the limitation done through _PPC:
cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit

The bios limit (_PPC) was not evaluated at (processor.ko) driver load time, but only when CPU notification events where thrown. It sounds like you see this. This got fixed by commit:
455c0d71d46e86b0b7ff2c9dcfc19bc162302ee9

Above patch could make trouble on other systems and you set "Fedora tree". Can you double check that above commit is included in your tested kernel.

Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.