From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Date: Mon, 31 Jan 2011 23:52:30 +0100 Message-ID: <201101312352.30883.rjw@sisk.pl> References: <556624.21214.qm@web28409.mail.ukl.yahoo.com> <4D471EC9.6030308@pardus.org.tr> <4D4723EF.60604@pardus.org.tr> Mime-Version: 1.0 Content-Type: Text/Plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <4D4723EF.60604@pardus.org.tr> Sender: platform-driver-x86-owner@vger.kernel.org To: Ozan =?utf-8?q?=C3=87a=C4=9Flayan?= Cc: Richard =?utf-8?q?Sch=C3=BCtz?= , 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 Monday, January 31, 2011, Ozan =C3=87a=C4=9Flayan wrote: > On 31.01.2011 22:42, Ozan =C3=87a=C4=9Flayan wrote: >=20 > > Well I've actually a screenshot of the boot hang with tons of debug= ging > > parameters passed to kernel. Maybe it will give you a clue. It hang= s > > right after printing e820 system memory map. > > > > http://bugs.pardus.org.tr/attachment.cgi?id=3D6554 > > >=20 > Well the line that is printed just after when booting with nolapic is= NX=20 > (Execute Disable) protection: active > generated by x86_report_nx(). >=20 > 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 nolapi= c=20 > is only significant on X86_32. I didn't know that. Well, it would be good to verify that the recent changes adding NX prot= ection to kernel data pages aren't causing these issues to appear. Hmm. Perhaps it's possible to test this patch on the affected boxes: https://bugzilla.kernel.org/attachment.cgi?id=3D45192 Rafael