https://bugzilla.kernel.org/show_bug.cgi?id=12389
Thomas Renninger <tr...@suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |tr...@suse.de
Component|cpufreq |Config-Processors
AssignedTo|cpuf...@vger.kernel.org |acpi_config-process...@kern
| |el-bugs.osdl.org
Product|Power Management |ACPI
--- Comment #3 from Thomas Renninger <tr...@suse.de> 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.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
