mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Jiri Kosina <jikos@jikos.cz>
Cc: Bodo Eggert <7eggert@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Introduce softpanic
Date: Fri, 25 Jan 2008 12:16:57 -0500	[thread overview]
Message-ID: <10536.1201281417@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 25 Jan 2008 16:26:45 +0100." <Pine.LNX.4.64.0801251624480.5521@twin.jikos.cz>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

On Fri, 25 Jan 2008 16:26:45 +0100, Jiri Kosina said:
> On Fri, 25 Jan 2008, Bodo Eggert wrote:
> 
> > 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.
> 
> Hi Bodo,
> 
> if you are willing to put some effort into the ability to scroll the 
> console after panic, it might be worthwile to look making the keyboard 
> driver work even after panic (i.e. poll the keyboard, rather than relying 
> on interrupts).
> 
> That has significantly smaller potential of breaking because the system is 
> expected to be dead after panic (watchdogs, broken data structures in 
> memory, etc).

I think Bodo is trying to address one specific (but quite common) corner
case, where we currently panic() only because there's nothing else that
makes sense - if we can't find the root fs, we're hosed.  But (barring *other*
oops/etc issues), we're still up and running, our data structures are intact,
and there's no real reason we can't use such kernel services as we want (such
as the screen scroller) to help the sysadmin figure out what he misconfigured.

If we were trying to do a *general case* handler for post-panic, yes, we'd
want to do the polled keyboard and all that....

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

      reply	other threads:[~2008-01-25 17:17 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
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 [this message]

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=10536.1201281417@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=7eggert@gmx.de \
    --cc=jikos@jikos.cz \
    --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®