kernel panic

[Ben Holland]

I would be VERY weary of general reboots on kernel panics outside of dev
purposes. I don't believe you actually get any kernel debug output except on
the screen which is lost. Most importantly if you have a bad disk and it
crashes it will cause a kernel panic ioct write or something very close to
that. If you reboot you loose which disk went bad and all it's going to do
is panic on reboot again and you will just perpetually reboot the computer
and it never stops. I actually love the idea of kernel dev in a VM though
i've never done that and would love to know the +/- on that. Overall message
though, kernel panic auto reboots I really don't like. ~Ben



On Thu, Apr 10, 2008 at 11:16 AM, Nuno Sucena Almeida <slug at aeminium.org>
wrote:

> On Thursday 10 April 2008 09:47:45 am Jarod Wilson wrote:
> > On Wed, 2008-04-09 at 23:54 -0700, Anil Saini wrote:
> > > how to recover from kernel panic
> > You can't. Its a panic. You have to hard reset a panicked system.
>
> Wouldn't the following settings work?
>
> # When the kernel panics, automatically reboot in 10 seconds
> kernel.panic = 10
>
> and others like:
> kernel.panic_on_oops = 1
>
> It saved me several times by rebooting (my own) remote machines while
> playing
> recently with a "fix" to a kernel exploit.
>
>                                        Nuno
>
> > And for future reference, your email is quite vague. When asking for
> > help, you really need to provide a bit more information, like a bit of
>
> I agree :-)
>
> --
> http://aeminium.org/slug/
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss
>

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.