From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756717Ab1AaWw6 (ORCPT ); Mon, 31 Jan 2011 17:52:58 -0500 Received: from ogre.sisk.pl ([217.79.144.158]:55361 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756414Ab1AaWw4 convert rfc822-to-8bit (ORCPT ); Mon, 31 Jan 2011 17:52:56 -0500 From: "Rafael J. Wysocki" To: Ozan =?utf-8?q?=C3=87a=C4=9Flayan?= Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Date: Mon, 31 Jan 2011 23:52:30 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.38-rc2+; KDE/4.4.4; x86_64; ; ) 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 References: <556624.21214.qm@web28409.mail.ukl.yahoo.com> <4D471EC9.6030308@pardus.org.tr> <4D4723EF.60604@pardus.org.tr> In-Reply-To: <4D4723EF.60604@pardus.org.tr> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Message-Id: <201101312352.30883.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, January 31, 2011, Ozan Çağlayan wrote: > On 31.01.2011 22:42, Ozan Çağlayan wrote: > > > Well I've actually a screenshot of the boot hang with tons of debugging > > 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=6554 > > > > Well the line that is printed just after when booting with nolapic is NX > (Execute Disable) protection: active > generated by x86_report_nx(). > > I looked through kernel/setup.c and can't really see anything between > setup_memory_map() which dumps the e820 map and x86_report_nx() which > could be affected by ACPI or nolapic. BTW, I've just seen that nolapic > is only significant on X86_32. I didn't know that. Well, it would be good to verify that the recent changes adding NX protection 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=45192 Rafael