* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

quoted text
> > This is true if he reverted just the 3def3d6d... commit, but if he 
> > also reverts the similar, and immediately following, 1e934dda... 
> > commit, then his 2.6.26 kernel runs fine.
> 
> interesting,
> 
> David, can you try only comment out
> 
> late_initcall(lapic_insert_resource);

i.e. the patch below?

what's your theory, what could be the reason for David's lockups?

	Ingo

--------------->
Index: linux/arch/x86/kernel/apic_32.c
===================================================================
--- linux.orig/arch/x86/kernel/apic_32.c
+++ linux/arch/x86/kernel/apic_32.c
@@ -1740,4 +1740,4 @@ static int __init lapic_insert_resource(
  * need call insert after e820_reserve_resources()
  * that is using request_resource
  */
-late_initcall(lapic_insert_resource);
+//late_initcall(lapic_insert_resource);
Index: linux/arch/x86/kernel/apic_64.c
===================================================================
--- linux.orig/arch/x86/kernel/apic_64.c
+++ linux/arch/x86/kernel/apic_64.c
@@ -1614,4 +1614,4 @@ static int __init lapic_insert_resource(
  * need call insert after e820_reserve_resources()
  * that is using request_resource
  */
-late_initcall(lapic_insert_resource);
+//late_initcall(lapic_insert_resource);

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/