>Just got a reboot on my box that has been running 2.1.127 since last
>night. :(
Argg bad! Is that a SMP machine with a SMP kernel? Which compiler are you
using? Can you send me the tty_io.o file privately by email?
>>>EIP: c01ad8ca <do_tty_hangup+14a/2d0>
>Trace: c0111ba2 <schedule+c6/2f4>
>Trace: c0111a6c <schedule_timeout+3c/ac>
>Trace: c0130a28 <do_select+130/224>
>Trace: c0130ab8 <do_select+1c0/224>
>Trace: c0130e49 <sys_select+32d/48c>
>Trace: c0119525 <do_bottom_half+85/a8>
>Trace: c0108c48 <system_call+34/38>
Argg bad trace... It could eventually make sense...
>Hopefully this will be of help to someone.
Yes at least we have the EIP that will make more sense when I' ll have the
.o object. Forget to tell to be sure to not strip such file. Please try
to reproduce!! Before trying to reproduce remeber to hack
arch/i386/traps.c and comment out the lines:
printk("\nCode: ");
for(i=0;i<20;i++)
printk("%02x ", ((unsigned char *)regs->eip)[i]);
If you have the patience to run without X trying to reproduce, you can not
remove such lines and instead put a for(;;) before them so when you' ll
get the first Oops your machine will lock but you' ll have the good Oops
on the console. Then you can write by hand at least the EIP and the stack
trace addressess and that would be very helpful...
>Let me know if you need further information.
Done ;->. I am going to recompile my kernel as SMP (even on UP) hoping to
reproduce something of such bad. Here everything is too much rock solid
:-(.
Thanks Kevin.
Andrea Arcangeli
-
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/