 |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | About BLU |
|
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | About BLU |
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
[hidden email]
http://lists.blu.org/mailman/listinfo/discuss
