[Bugme-new] [Bug 9151] New: Something broke cpufreq on laptop with lid behavior

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Fri Oct 12 10:07:15 PDT 2007


http://bugzilla.kernel.org/show_bug.cgi?id=9151

           Summary: Something broke cpufreq on laptop with lid behavior
           Product: ACPI
           Version: 2.5
     KernelVersion: 2.6.23
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
        AssignedTo: acpi_other at kernel-bugs.osdl.org
        ReportedBy: stevenm at umd.edu


Hello. I am on a Dell Inspiron 600m laptop with a 2GHz Pentium-M.

I've had 2.6.17.6 on my laptop and all worked splendidly.
I just switched to 2.6.23 and now the following power annoyances happen. As far
as I can tell, these things happen without any sort of helper daemon running,
ie a system just booted to a VT (but I guess I could be wrong)

When AC power is unplugged, the system clocks to its lowest speed but it also
throttles to 25%. I don't want the throttling and have to un-throttle it by
hand.

If the system runs on AC power, lid behavior is fine (backlight turns off via
radeontool). But if the system is on battery power and the lid is closed,
STRANGE things happen. The governor switches to powersave. If the lid is closed
on battery power, the CPU frequency begones the HIGHEST (2GHz).
scaling_min_freq and scaling_max_freq report 600MHz but scaling_cur_freq
reports 2GHz. 
If I try changing the frequency to 600MHz (via cpuspeedy), the frequency won't
change unless I switch to some intermediate speed first, and then go all the
way down to 600MHz.

This seems most likely to be a kernel issue since it broke between 2.6.17.6 and
2.6.23 (maybe closer to 2.6.20). Switching back to the older kernel makes
everything work properly again. Have there been any major cpufreq changes?


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


More information about the Bugme-new mailing list