mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Andi Kleen <andi@firstfloor.org>
Cc: Bodo Eggert <7eggert@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Introduce softpanic
Date: Sat, 2 Feb 2008 14:15:55 +0000	[thread overview]
Message-ID: <20080202141554.GB4456@ucw.cz> (raw)
In-Reply-To: <p73ejc67xvb.fsf@bingen.suse.de>

On Fri 2008-01-25 16:01:28, Andi Kleen wrote:
> Bodo Eggert <7eggert@gmx.de> writes:
> 
> > Enabling this option changes a hard panic on boot errors to a
> > soft panic, which does not stop the system completely.
> > You can still scroll the screen and read the messages.
> 
> I don't think it's a good idea to keep the network running in the
> soft panic. A lot of people have set ups that use ping was a watchdog
> and with nfsroot/ip=dhcp ping does work quite well before
> mounting root and then the watchdog might not pick up the 
> soft panic.
> 
> Using a polled keyboard driver after panic seems to be the better
> option to me, but if you want softpanic you should probably
> at least add a suitable panic notifier to the network stack 
> to shut it all down.

OTOH this will allow netconsole/sysrq over it to still work after
softpanic, which is good. Lets not over engineer it, I think current
code is fine.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2008-02-02 18:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 14:54 Bodo Eggert
2008-01-25 15:01 ` Andi Kleen
2008-01-25 15:22   ` Jan Engelhardt
2008-01-25 17:31   ` Bodo Eggert
2008-02-02 14:15   ` Pavel Machek [this message]
2008-01-25 15:21 ` Jan Engelhardt
2008-01-25 17:37   ` Bodo Eggert
2008-01-28 19:07     ` [PATCH] Introduce softpanic V.2 Bodo Eggert
2008-01-25 15:26 ` [PATCH] Introduce softpanic Jiri Kosina
2008-01-25 17:16   ` Valdis.Kletnieks

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=20080202141554.GB4456@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=7eggert@gmx.de \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®