[Bugme-new] [Bug 20232] New: kworker consumes ~100% CPU on HP Elitebook 8540w running 2.6.36_rc6-git4

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Tue Oct 12 23:13:41 PDT 2010


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

           Summary: kworker consumes ~100% CPU on HP Elitebook 8540w
                    running 2.6.36_rc6-git4
           Product: ACPI
           Version: 2.5
    Kernel Version: 2.6.36_rc6-git4
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Config-Interrupts
        AssignedTo: acpi_config-interrupts at kernel-bugs.osdl.org
        ReportedBy: ozan at pardus.org.tr
                CC: rjw at sisk.pl, ibrahim at pardus.org.tr
        Regression: Yes


I'm having a serious CPU hogging problem with an HP Elitebook 8540w running
2.6.36_rc6. A kworker consumes ~100% CPU during all the uptime since booting.

I first tried rmmod'ing all the modules but it didn't help. Then I built the
kernel with some ACPI/PM verbose flags turned on and found out that an infinite
number of the following message was written in kernel log:

scsi host1: __pm_runtime_resume() returns 1!

I then passed "on\n" to all power/control files in sysfs but the messages
didn't
disappear. I disabled PM_RUNTIME to see if it was causing the kworker stuff,
but
nope, it still continues.

Then I found a similar report and tried writing "disable" to
/sys/firmware/acpi/interrupts/gpe01 and it stopped the kworker CPU consumation
problem *although the load average doesn't drop under ~1.3*. When enabled the
number of interrupts in /sys/firmware/acpi/interrupts/gpe01 increases very
fast.

The problem is not fixed with the pcie_pme=off trick suggested in the other bug
report related to this laptop.

(CC'ing İbrahim, the owner of the laptop)

Thanks

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