https://bugzilla.kernel.org/show_bug.cgi?id=12389 Thomas Renninger <trenn@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |trenn@xxxxxxx Component|cpufreq |Config-Processors AssignedTo|cpufreq@xxxxxxxxxxxxxxx |acpi_config-processors@kern | |el-bugs.osdl.org Product|Power Management |ACPI --- Comment #3 from Thomas Renninger <trenn@xxxxxxx> 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 the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
