Skip to contentSkip to conversation

intel_idle .. Was: __pm_runtime_resume() returns -1 Was: Regression in 2.6.36

DISCUSSION Christian Ruediger Bahls 1 participant 1 message Oct 24, 2010 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 7 lines · [2010-10-23 19:49] Len Brown <[email protected]> wrote:
Quoted 3 lines

and yes indeed booting with "intel_idle.max_cstate=0" makes the system work again

Please file a sighting here:
https://bugzilla.kernel.org/enter_bug.cgi?product=Power%20Management
component: intel_idle

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

Quoted 5 lines · [2010-10-23 19:58] Rafael J. Wysocki <[email protected]> wrote:
Quoted 3 lines

in later versions of the kernel it throws the
"__pm_runtime_resume() returns -1"-warnings

Do you have CONFIG_PM_VERBOSE set in your .config by chance?

Yes i have

Quoted 1 line · [2010-10-23 20:04] Len Brown <[email protected]> wrote:

describe symptoms (I think this is a fully reproducible boot hang, yes?)

yes, fully reproducible boot hang
(hangs "best" with max_cstate=2

Quoted 3 lines

try intel_idle.max_cstate=1, include dmesg
and increase the '1' until it fails
My guess is that 1 will work, but some higher number will start failing.

yes, max_cstate=4 works better(like in: hanging less often) than max_cstate=2

Quoted 1 line

without any other bootparams, try "nolapic_timer"

yes .. this helps .. dmesg's attach to bug report mentioned above

Quoted 2 lines

thanks,
Len Brown, Intel Open Source Technology Center

Thank you very much as well :)

yours
Christian