[Bugme-new] [Bug 19702] New: i5-450M CPU gets stuck in low/lowest state

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Sun Oct 3 23:41:32 PDT 2010


https://bugzilla.kernel.org/show_bug.cgi?id=19702

           Summary: i5-450M CPU gets stuck in low/lowest state
           Product: ACPI
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Power-Processor
        AssignedTo: acpi_power-processor at kernel-bugs.osdl.org
        ReportedBy: htd at fancy-poultry.org
                CC: trenn at suse.de
        Regression: No


Created an attachment (id=32502)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=32502)
Outout of acpidump

Hi,

I own a brand new ASUS U45JC laptop with an Intel i5-450M CPU built in.
During the first compile on it, I noticed that the CPU reached max. 1.33 GHz
using governor "ondemand". Kicking the CPU with a kernel compile using
"make -j4" didn't help either, max. frequency was nailed at 1.33 GHz.
Both the latest stable 2.6.35.7 and release candidate 2.6.36-rc6-git2 are
affected.

After 2 days investigating (I'm not primarily a kernel programmer/developer),
I came across the solution, and there was already a patch available from
Thomas Renninger @suse, which I have included in this mail. I blindly
guess now that a lot of people own a notebook with an Intel i5 inside, and
maybe (could) have the same problem.

Any chance to get this included in the kernel, or is it just me who
encounters this problem? The patch applies cleanly against the latest rc,
and I can confirm that it also fixes the above mentioned problem in
2.6.35.7 (I backported it and did try).

Attached are the output of acpidump and dmesg, and the patch from Thomas
Renninger which fixes the problem for me. BIOS is the latest version 207 from
Asus.

Thanks,
Heinz.

-- 
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.


More information about the Bugme-new mailing list