http://bugzilla.kernel.org/show_bug.cgi?id=12788 ------- Comment #10 from trenn@xxxxxxx 2009-03-05 15:18 ------- This one looks rather different. In this case it should be acpi producing that much interrupts. Hmm, I remember an endless loop for Dells (with docking?). But you really should see an interrupt source heavily increasing? Could you change the component, please. Best to ACPI, there are several people looking at ACPI bugs. It very much looks like an interrupt source goes wild waking up the processor all the time. If it's acpi and you have ACPI_DEBUG compiled in you could shortly increase debug level: echo 0x21F > /sys/module/acpi/parameters/debug_level echo 0xFFFFFFFF > /sys/module/acpi/parameters/debug_layer sleep 1 echo 0xF > /sys/module/acpi/parameters/debug_level and have a look which ACPI parts are processed. Hmm, there are also GPEs exported now somewhere in /sys. On each acpi interrupt a GPE should increase. Is there one going up very quickly after suspend? You can then guess from the DSDT table to what device (battery/thermal/...) the GPE belongs and at what driver to look at. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
