[lkml]   [1999]   [May]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
SubjectRe: Oops assist...

> > Wouldn't it be quite reasonable to make "Reboot on Oops" an config-option
> > or a sysctl?
> Obviously, yes. (I think that reboot on Oops should be the default).

No. I've seen many oopses which were completely harmless (few
processes died, who cares? :-).

I advocated putting 10sec delay after oops. It is good so at least you
can see the oops and you can remeber IP if you are fast enough
;-). Much better than quickly rebooting machine. If you extend this
delay to 10min, user will have plenty of time to copy data onto paper

--- clean/arch/i386/kernel/traps.c Fri Feb 26 18:39:57 1999
+++ linux/arch/i386/kernel/traps.c Fri Feb 26 11:49:39 1999
@@ -201,6 +201,18 @@
printk("%s: %04lx\n", str, err & 0xffff);
+ {
+ 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);
+ }

> IMHO, the swapfile is the best & portable solution: NT uses
> the swapfile, I've read the Solaris uses the swapfile, too.

Unfortunately, there were cases when this destroyed valuable data.

I'm really Look at Pavel
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:51    [W:0.115 / U:0.232 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site