> Unfortunately, the only properly decoded oops I've seen isn't very helpful...
>
> >> >>EIP: c0109a65 <show_registers+24d/280>
> >> Trace: c4800000
> >> Trace: c0109ac8 <die+30/38>
>
> Michel - could you repeat the problem, and try to catch the _first_ oops of
> the pair. Then decode it as you did the other one, and post it to the mailing
> list. Someone should then be able to take a closer look, and if they don't
> then I'll have a look when I get back in a fortnight.
>
> Try using a bigger video mode, if the first one was scrolling
> off-screen.
Or try this patch: (Kernel gods, are you hearing? I think that having
this in kernel would be _very_ helpfull, because Oopses just _love_ to
scroll away much too fast for you to _anything_).
Pavel
--- clean/arch/i386/kernel/traps.c Sat Nov 14 23:16:00 1998
+++ linux/arch/i386/kernel/traps.c Fri Dec 4 19:32:10 1998
@@ -192,6 +192,18 @@
spin_lock_irq(&die_lock);
printk("%s: %04lx\n", str, err & 0xffff);
show_registers(regs);
+ {
+ long flags;
+ int i;
+ save_flags(flags); cli();
+ printk( "Oops -> waiting" );
+ for(i=0; i<10; i++) {
+ mdelay(1000);
+ printk( "." );
+ }
+ printk( "\n" );
+ restore_flags(flags);
+ }
spin_unlock_irq(&die_lock);
do_exit(SIGSEGV);
}
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/