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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 31 Jan 2011 23:52:30 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Ozan Çağlayan <ozan@...dus.org.tr>
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
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)

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
--
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/