linux-kernel - Re: How to compile kernel so it automatically reboots upon a crash instead of generating stack trace and then hang.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0803120602580.18745@fbirervta.pbzchgretzou.qr>
Date:	Wed, 12 Mar 2008 06:04:15 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Prakhar Krishna <prakhar2@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: How to compile kernel so it automatically reboots upon a crash
 instead of generating stack trace and then hang.

On Mar 11 2008 23:52, Prakhar Krishna wrote:
>
>[I did search the mailing lists archives and the Web but did not find an answer,
> apololgies if this is duplicate question]
>
>i need my linux box to automatically reboot if it ever runs into a
>kernel panic/crash etc.

panic=<timeout> boot parameter, as per 
Documentation/kernel-parameters.txt.

>For my production evvironment, it is not desired that kernel generate the stack
>trace and then wait there. We want it to reboot and comeback up again.

Kernel panic is not the only problem one can run into; there are
also deadlocks-after-oops situations, in which case some sort of
watchdog is best for triggering reboots.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/