Okay, I found a bug that SGI has hacked around on our boxborough-EX
machines that looks similar. The bug wasn't assigned to me, so I didn't
know it was hacked around. :)
Can you try this (may not apply. I cut & pasted)? Obviously it's a
terribly patch, but it'll show us if it's the same problem.
Index: linux/arch/x86/kdb/kdba_io.c
===================================================================
--- linux.orig/arch/x86/kdb/kdba_io.c 2009-02-11 08:57:34.000000000 -0600
+++ linux/arch/x86/kdb/kdba_io.c 2009-02-12 08:39:09.000000000 -0600
@@ -564,7 +564,7 @@ get_char_func poll_funcs[] = {
void kdba_local_arch_setup(void)
{
-#ifdef CONFIG_VT_CONSOLE
+#ifdef ZZCONFIG_VT_CONSOLE
int timeout;
unsigned char c;
@@ -589,7 +589,7 @@ void kdba_local_arch_setup(void)
void kdba_local_arch_cleanup(void)
{
-#ifdef CONFIG_VT_CONSOLE
+#ifdef ZZCONFIG_VT_CONSOLE
int timeout;
unsigned char c;
This was in our stack of patches that we thought were just working
around bugs in our BIOS. It seems that our BIOS always returns 0xff
while reading from 0x64.
mh
_______________________________________________
kdb mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/kdb
