CONFIG_PREEMPT creates a bootstrap ordering issue as some implicit
scheduling done in printk.c raises exceptions prior to the secondary
cpus being prepared to handle them (seen as no vm86_info: BAD).
The workaround, enclosed below is not to use preempt on NUMA-Q.
Cheers,
Bill
===== arch/i386/config.in 1.40 vs edited =====
--- 1.40/arch/i386/config.in Mon Jun 17 07:03:16 2002
+++ edited/arch/i386/config.in Fri Jul 12 01:12:25 2002
@@ -165,7 +165,9 @@
define_bool CONFIG_X86_IO_APIC y
fi
else
- bool 'Multiquad NUMA system' CONFIG_MULTIQUAD
+ if [ "$CONFIG_PREEMPT" != "y" ]; then
+ bool 'Multiquad NUMA system' CONFIG_MULTIQUAD
+ fi
fi
bool 'Machine Check Exception' CONFIG_X86_MCE
-
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/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:24 EST