Unable to raise CPU frequency of notebook after AC adapter disconnect and reconnect
A message that is not in the archive (sent off-list or not yet received): [email protected]/
https://bugzilla.kernel.org/show_bug.cgi?id=33742
Rafael J. Wysocki <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |[email protected]
Component|Other |cpufreq
AssignedTo|power-management_other@kern |[email protected]
|el-bugs.osdl.org |--- Comment #4 from Rafael J. Wysocki <[email protected]> 2011-04-20 19:15:15 --- Please attach dmesg output including an AC unplug/replug cycle.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=33742
Thomas Renninger <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected] Component|cpufreq |BIOS AssignedTo|[email protected] |[email protected]. | |org Product|Power Management |ACPI
--- Comment #5 from Thomas Renninger <[email protected]> 2011-04-21 10:13:12 ---
Quoted 2 lines
and the problems that I am seeing date back from at least version 2.6.24, from what I can remember.
Most likely a BIOS, _PPC issue, yes it is:
before:/sys/devices/system/cpu/cpu0/cpufreq/bios_limit:2001000 after:/sys/devices/system/cpu/cpu0/cpufreq/bios_limit:800000
That means _PPC does not return 0 anymore and BIOS tells the OS to limit the frequency. This is an ACPI problem, cpufreq subsystem bevhaves fine (at least this was always the case with similar bug reports recently).
-> Re-assign to ACPI component.
Quoted 1 line
Please attach dmesg output including an AC unplug/replug cycle.
Best boot with log_buf_len=16777216
before you do the unplug/replug cycle copy this into a file, make it executable and follow instructions:
==============
#!/bin/bash
echo 0xFFFFFFFF >/sys/module/acpi/parameters/debug_layer echo 0xF >/sys/module/acpi/parameters/debug_level echo 7 >/sys/module/cpufreq/parameters/debug logger "Before unplug"
echo "It's time to unplug ..."
sleep 5
logger "AC got unplugged"
echo "It's time to re-plug"
sleep 5
echo 0x0 >/sys/module/acpi/parameters/debug_layer echo 0 >/sys/module/cpufreq/parameters/debug
==============
and then attach whole dmesg and also acpidump output.
Hm, before you should check for a BIOS upgrade and whether you find related BIOS settings.
--- Comment #6 from Rogério Brito <[email protected]> 2011-04-22 09:17:19 --- Hi, Rafael, Thomas.
Thank you for your answers. Here comes my follow up.
(In reply to comment #5)
Quoted 4 lines
That means
_PPCdoes not return 0 anymore and BIOS tells the OS to limit the frequency. This is an ACPI problem, cpufreq subsystem bevhaves fine (at least this was always the case with similar bug reports recently).
-> Re-assign to ACPI component.
OK, sorry for assigning that to the wrong component. It is not always obvious where to file some bugs.
Quoted 7 lines
Quoted 1 line
Please attach dmesg output including an AC unplug/replug cycle.
Best boot with log_buf_len=16777216
before you do the unplug/replug cycle copy this into a file, make it executable and follow instructions:
==============
#!/bin/bash
Quoted 12 lines
echo
0xFFFFFFFF>/sys/module/acpi/parameters/debug_layer echo0xF>/sys/module/acpi/parameters/debug_level echo 7 >/sys/module/cpufreq/parameters/debug logger "Before unplug"
echo "It's time to unplug ..."
sleep 5
logger "AC got unplugged"
echo "It's time to re-plug"
sleep 5
echo0x0>/sys/module/acpi/parameters/debug_layer echo 0 >/sys/module/cpufreq/parameters/debug
==============
OK. I did all that. As the logs are very big, I am including them compressed here. Please let me know if that's not what you want.
Quoted 2 lines
Hm, before you should check for a BIOS upgrade and whether you find related BIOS settings.
Unfortunately, I first tried to find the most recent BIOS update from the manufacturer (it's dated from 2010, IIRC) and, then, after flashing and noticing that it wasn't working, I filed the bug.
I don't quite expect any updated version of the BIOS from MSI. Would there be any way to circumvent the buggy BIOS? If not in a clean and generic way, perhaps passing the kernel any extra option?
Thanks,
Rogério Brito.
Signature · 3 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.