linux-kernel - Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D471D2F.7010008@pardus.org.tr>
Date:	Mon, 31 Jan 2011 22:35:59 +0200
From:	Ozan Çağlayan <ozan@...dus.org.tr>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
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 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.


-- 
Pardus Linux
http://www.pardus.org.tr/eng
--
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/