[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20101024024024.GA2459@pfau.e-technik1.uni-rostock.de>
Date: Sun, 24 Oct 2010 04:40:24 +0200
From: Christian Ruediger Bahls <lkml@...52.de>
To: Len Brown <lenb@...nel.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Eric Dumazet <eric.dumazet@...il.com>,
Len Brown <len.brown@...el.com>
Subject: Re: intel_idle .. Was: __pm_runtime_resume() returns -1 Was:
Regression in 2.6.36
[2010-10-23 19:49] Len Brown <lenb@...nel.org> wrote:
>
> > 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
[2010-10-23 19:58] Rafael J. Wysocki <rjw@...k.pl> wrote:
>
> > 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
[2010-10-23 20:04] Len Brown <lenb@...nel.org> wrote:
> describe symptoms (I think this is a fully reproducible boot hang, yes?)
yes, fully reproducible boot hang
(hangs "best" with max_cstate=2
> 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
> without any other bootparams, try "nolapic_timer"
yes .. this helps .. dmesg's attach to bug report mentioned above
> thanks,
> Len Brown, Intel Open Source Technology Center
Thank you very much as well :)
yours
Christian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists