From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: Lionel Debroux <lionel_debroux@yahoo.fr>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, colin.king@canonical.com
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)
Date: Mon, 31 Jan 2011 10:50:49 +0100 [thread overview]
Message-ID: <201101311050.49722.rjw@sisk.pl> (raw)
In-Reply-To: <4D467882.9060304@pardus.org.tr>
On Monday, January 31, 2011, Ozan Çağlayan wrote:
> On 31.01.2011 00:48, Rafael J. Wysocki wrote:
>
> > Does booting with "nolapic" help on all of the affected systems?
> >
> > Also, does disabling the CPUidle during boot help?
> >
> > Finally, is the problem reproducible with CONFIG_NO_HZ unset?
>
> Well on two machines, nolapic cures the boot hang and on one machine it
> cures the random shutdown hangs.
>
> I'll compile a kernel with CONFIG_NO_HZ to see what happens but how do I
> disable cpuidle during boot? I've checked the kernel-parameters.txt but
> there's no cpuidle related boot parameter there.
Booting with intel_idle.max_cstate=0 should do the trick.
Thanks,
Rafael
next prev parent reply other threads:[~2011-01-31 9:51 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 14:28 Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Ozan Çağlayan
2011-01-23 15:00 ` Richard Schütz
2011-01-23 15:11 ` Gene Heskett
2011-01-23 16:49 ` Ozan Çağlayan
2011-01-23 16:56 ` Ozan Çağlayan
2011-01-23 20:24 ` Ozan Çağlayan
2011-01-24 9:00 ` Ozan Çağlayan
2011-01-24 9:04 ` Lionel Debroux
2011-01-24 9:21 ` Ozan Çağlayan
2011-01-24 9:47 ` Lionel Debroux
2011-01-24 20:14 ` Lionel Debroux
2011-01-25 2:56 ` Len Brown
2011-01-26 7:41 ` Lionel Debroux
2011-01-27 7:59 ` Lionel Debroux
2011-01-25 6:22 ` Ozan Çağlayan
2011-01-25 19:38 ` Rafael J. Wysocki
2011-01-25 19:45 ` Ozan Çağlayan
2011-01-25 19:54 ` Rafael J. Wysocki
2011-01-25 20:00 ` Ozan Çağlayan
2011-01-29 17:49 ` Ozan Çağlayan
2011-01-30 20:30 ` Ozan Çağlayan
2011-01-30 22:48 ` Rafael J. Wysocki
2011-01-31 8:53 ` Ozan Çağlayan
2011-01-31 9:50 ` Rafael J. Wysocki [this message]
2011-01-31 10:03 ` Ozan Çağlayan
2011-01-31 10:14 ` Rafael J. Wysocki
2011-01-31 10:20 ` Richard Schütz
2011-01-31 10:23 ` Rafael J. Wysocki
2011-01-31 10:29 ` Richard Schütz
2011-01-31 18:24 ` Rafael J. Wysocki
2011-01-31 18:29 ` Ozan Çağlayan
2011-01-31 18:33 ` Rafael J. Wysocki
2011-01-31 18:38 ` Ozan Çağlayan
2011-01-31 19:12 ` Rafael J. Wysocki
2011-01-31 20:35 ` Ozan Çağlayan
2011-01-31 20:42 ` Rafael J. Wysocki
2011-01-31 20:42 ` Ozan Çağlayan
2011-01-31 21:04 ` Ozan Çağlayan
2011-01-31 22:52 ` Rafael J. Wysocki
2011-02-03 21:10 ` Ozan Çağlayan
2011-02-03 22:04 ` Rafael J. Wysocki
2011-02-03 22:13 ` Ozan Çağlayan
2011-02-03 22:51 ` Rafael J. Wysocki
2011-02-04 6:44 ` Ozan Çağlayan
2011-02-04 20:36 ` Rafael J. Wysocki
2011-02-05 13:21 ` Ozan Çağlayan
2011-02-05 18:16 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201101311050.49722.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=colin.king@canonical.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lionel_debroux@yahoo.fr \
--cc=ozan@pardus.org.tr \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).