[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201101311933.38050.rjw@sisk.pl>
Date: Mon, 31 Jan 2011 19:33:37 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Ozan Çağlayan <ozan@...dus.org.tr>
Cc: Richard Schütz <r.schtz@...nline.de>,
Lionel Debroux <lionel_debroux@...oo.fr>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org, colin.king@...onical.com
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)
On Monday, January 31, 2011, Ozan Çağlayan wrote:
> On 31.01.2011 20:24, Rafael J. Wysocki wrote:
>
> >>
> >> Or just use the processor.max_cstate parameter then.
> >
> > As I wrote a couple of messages ago, https://lkml.org/lkml/2011/1/31/52 .
>
> The users reported that processor.max_cstate=0 didn't help too. The ones
> which experience random hangs during shutdown tells that the hard disk
> is turned off and the fans are turning faster.
>
> The other user which can't even boot didn't tell the result of adding
> processor.max_cstate=0 to boot params.
Well, I'm kind of not sure what to do next.
The expectation seems to be that the problem is somehow related to cpuidle,
but the above observations fail to confirm that.
Would it be possible to check if running the kernel in uniprocessor mode
makes the problem go away?
Rafael
--
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