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 platform-driver-x86" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
