mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Jan Engelhardt" <jengelh@computergmbh.de>
Cc: "Prakhar Krishna" <prakhar2@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: How to compile kernel so it automatically reboots upon a crash instead of generating stack trace and then hang.
Date: Wed, 12 Mar 2008 11:40:36 +0100	[thread overview]
Message-ID: <e2e108260803120340u6e42b1d1hd3fc51bb92f21830@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803120602580.18745@fbirervta.pbzchgretzou.qr>

On Wed, Mar 12, 2008 at 6:04 AM, Jan Engelhardt <jengelh@computergmbh.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.

  reply	other threads:[~2008-03-12 10:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  4:52 Prakhar Krishna
2008-03-12  5:04 ` Jan Engelhardt
2008-03-12 10:40   ` Bart Van Assche [this message]
2008-03-13 12:07     ` Prakhar Krishna
2008-03-12  8:53 ` Sebastien Dugue

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2e108260803120340u6e42b1d1hd3fc51bb92f21830@mail.gmail.com \
    --to=bart.vanassche@gmail.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakhar2@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®