https://bugzilla.kernel.org/show_bug.cgi?id=12389
--- Comment #7 from Thomas Renninger <tr...@suse.de> 2010-11-08 10:00:52 ---
> I built this kernel from Fedora sources
That's great.
Please make sure you have:
CONFIG_CPU_FREQ_DEBUG=y
enabled and boot with cpufreq.debug=1
You should see this message then:
cpufreq_printk("CPU %d: _PPC is %d - frequency %s limited\n", pr->id,
(int)ppc, ppc ? "" : "not");
at boot up (when processor driver gets loaded) and later when you plug/unplug
AC.
When you get a "not limited" at boot up, there is something fishy with your
BIOS and you should provide acpidump output.
If this is the case you could try avoid autoloading then by adding:
blacklist acpi-cpufreq
blacklist processor
blacklist thermal
to /etc/modprobe.conf and try to load acpi-cpufreq (which in turn should load
processor) later after some more acpi drivers got loaded...
If _PPC is not 0 at boot up, but no limit gets applied to bios_limit cpufreq
sysfs file, there is a kernel bug.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
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
