From: Willy Tarreau <willy@w.ods.org>
To: Andi Kleen <ak@muc.de>
Cc: "Dr. David Alan Gilbert" <dave@treblig.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
subbie subbie <subbie_subbie@yahoo.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: optional delay after partition detection at boot time
Date: Sun, 12 Jun 2005 15:17:01 +0200 [thread overview]
Message-ID: <20050612131701.GA8907@alpha.home.local> (raw)
In-Reply-To: <m1fyvnd8kc.fsf@muc.de>
On Sun, Jun 12, 2005 at 03:10:59PM +0200, Andi Kleen wrote:
> "Dr. David Alan Gilbert" <dave@treblig.org> writes:
> >
> > 1) could be cured by not actually panic'ing.
>
> Actually one thing I always wanted was to make sysrq still work
> after panic. Then you could add a key to page through the dmesg
> there too and the problem would be solved.
Well, that's why I wrote kmsgdump several years ago :-) You could even print
the messages on a parallel printer or save them to a floppy disk.
> It would be extremly useful to reset remote servers when panic=timeout
> is not set, but something went wrong with mounting /.
I think that more generally, we should reset if there's no panic=timeout,
because the reasons for a panic are multiple and in case of remote servers,
it's always a nightmare to know that may be you will lose access after one
risky operation.
Willy
next prev parent reply other threads:[~2005-06-12 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 6:50 optional delay after partition detection at boot time subbie subbie
2005-06-12 7:10 ` Jan Engelhardt
2005-06-12 7:12 ` Willy Tarreau
2005-06-12 10:15 ` subbie subbie
2005-06-12 10:27 ` Willy Tarreau
2005-06-12 10:32 ` Jan Engelhardt
2005-06-13 2:22 ` David Lang
2005-06-13 4:17 ` Willy Tarreau
2005-06-13 7:02 ` David Lang
2005-06-12 10:27 ` Geert Uytterhoeven
2005-06-12 11:05 ` Dr. David Alan Gilbert
2005-06-12 11:16 ` Willy Tarreau
2005-06-12 12:54 ` Dr. David Alan Gilbert
2005-06-12 13:10 ` Andi Kleen
2005-06-12 13:17 ` Willy Tarreau [this message]
2005-06-13 1:46 ` Valdis.Kletnieks
2005-06-12 13:25 ` Jesper Juhl
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=20050612131701.GA8907@alpha.home.local \
--to=willy@w.ods.org \
--cc=ak@muc.de \
--cc=dave@treblig.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=subbie_subbie@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.