[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201101312142.37773.rjw@sisk.pl>
Date: Mon, 31 Jan 2011 21:42: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 21:12, Rafael J. Wysocki wrote:
>
> > Booting with maxcpus=0 also disables the I/O APIC, which probably is a bit too
> > much, but let's see what happens in that case.
>
> Well the only-booting-with-nolapic one doesn't boot with maxcpus=0. Pff,
> are there any compile-time(Kconfig) or runtime parameters related to
> debugging various subsystems that you'll suggest which will show where
> the boot hangs? That way we can maybe pinpoint the issue to a specific
> function call.
Booting with initcall_debug causes all of the initcalls to be shown (start,
finish and duration), so it may allow you to find the culprit if you can
collect the messages.
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