https://bugzilla.kernel.org/show_bug.cgi?id=23412 --- Comment #5 from Thomas Renninger <trenn@xxxxxxx> 2010-12-17 15:25:40 --- > If your ACPI tables are not busted (and you should see this by some obvious > ACPI Error messages in dmesg Not really true, if there is a logical bug, but syntax, etc. in ACPI code is correct you may not see an error message. But ACPI interpreting works pretty well these days and chances that the limit is wanted by the OEM for whatever reasons are high. You can override the BIOS limit by the boot param: processor.ignore_ppc=1 But instead of using this all day, you should better find out why the BIOS vendor/OEM limits your frequency, there is certainly a reason for it. Above helps (and this is hopefully what the bug is about) only if you see the limit here: /sys/devices/system/cpu/cpu0/cpufreq/bios_limit If your frequency is restricted/limited due to other reasons, please open a new bug and state it in the description to avoid confusion and mix ups of several problems in one bug. Hmm, there were quite some people in CC of this bug. I'd be interested how much get fixed by BIOS settings, etc.. I keep the bug open for a while, even I am pretty sure most/all people seeing BIOS frequency limits is *not* due to a kernel bug. -- 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
