From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?T3phbiDDh2HEn2xheWFu?= Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Date: Mon, 31 Jan 2011 23:04:47 +0200 Message-ID: <4D4723EF.60604@pardus.org.tr> References: <556624.21214.qm@web28409.mail.ukl.yahoo.com> <201101311933.38050.rjw@sisk.pl> <4D4701B7.8030004@pardus.org.tr> <201101312012.42393.rjw@sisk.pl> <4D471D2F.7010008@pardus.org.tr> <4D471EC9.6030308@pardus.org.tr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <4D471EC9.6030308@pardus.org.tr> Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: =?UTF-8?B?UmljaGFyZCBTY2jDvHR6?= , Lionel Debroux , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org List-Id: linux-acpi@vger.kernel.org On 31.01.2011 22:42, Ozan =C3=87a=C4=9Flayan wrote: > Well I've actually a screenshot of the boot hang with tons of debuggi= ng > parameters passed to kernel. Maybe it will give you a clue. It hangs > right after printing e820 system memory map. > > http://bugs.pardus.org.tr/attachment.cgi?id=3D6554 > Well the line that is printed just after when booting with nolapic is N= X=20 (Execute Disable) protection: active generated by x86_report_nx(). I looked through kernel/setup.c and can't really see anything between=20 setup_memory_map() which dumps the e820 map and x86_report_nx() which=20 could be affected by ACPI or nolapic. BTW, I've just seen that nolapic=20 is only significant on X86_32. I didn't know that. --=20 Pardus Linux http://www.pardus.org.tr/eng