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.
--
Pardus Linux
http://www.pardus.org.tr/eng
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
