https://bugzilla.kernel.org/show_bug.cgi?id=14771 Thomas Renninger <trenn@xxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@xxxxxxx --- Comment #16 from Thomas Renninger <trenn@xxxxxxx> 2010-04-23 15:43:20 --- Without re-reading the whole thread: There are generally two possibilities how BIOS can tell OS to limit freq: ... Ok, I've better written it down for further referencing and placed it here, eventually it's going to help you (oh dear, I have to wrap up the lines...): ftp://ftp.suse.com/pub/people/trenn/ACPI_BIOS_on_Linux_guide/Frequency_is_limited_how_to.txt Reading your power supply experiences, I could imagine you see two phenomenons: - BIOS tells the OS to limit frequency because power supply requirements are not met -> max_frequency gets limited - If processor.ignore_ppc=1 is passed OS frequency switching might get ignored by HW and HW still limits frequency behind OS back -> max_frequency should still be high then, but you might see "out of sync" messages with cpufreq_debug and cpuinfo_cur_freq won't raise. Anyway, this looks like a HW and not a kernel issue and should get closed, right? Hm, I cannot modify the bugs status... -- 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
