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] [day] [month] [year] [list]

Date:	Thu, 13 Mar 2008 07:07:26 -0500
From:	"Prakhar Krishna" <prakhar2@...il.com>
To:	"Bart Van Assche" <bart.vanassche@...il.com>
Cc:	"Jan Engelhardt" <jengelh@...putergmbh.de>,
	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.

thanks everyone for the information.

can it be presumed that boot option panic=<x> would always reboot the machine
upon a crash/null pointer dereference if it is not stuck in a
deadlock? also, is there any
place in kernel where, if desired, the panic time can be hardcoded and compiled
for my specific test kernel.

intention is to look for a way to make a regular PC with linux OS
behave close to a
customized hardware appliance through software only mechanism. that
way it becomes
much easier to send just software to the users, which they can load on any
PC without requiring them to have additional hardware inserted into it.

please CC me on replies.

thanks
PK

On Wed, Mar 12, 2008 at 5:40 AM, Bart Van Assche
<bart.vanassche@...il.com> wrote:
> On Wed, Mar 12, 2008 at 6:04 AM, Jan Engelhardt <jengelh@...putergmbh.de> wrote:
> >
> >  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.
>
> The best solution in this case is a hardware watchdog. Hardware
> watchdogs are present on some server motherboards, most embedded x86
> CPU boards and also in PowerPC CPU's. The Linux kernel supports some
> hardware watchdogs, see also Device Drivers/Watchdog Timer Support in
> the Linux kernel config.
>
> The nmi_watchdog=<timeout> parameter might be interesting too. See
> also Documentation/nmi_watchdog.txt.
>
> Bart.
>
--
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/