From: Andi Kleen <andi@firstfloor.org>
To: Clemens Koller <clemens.koller@anagramm.de>
Cc: Bodo Eggert <7eggert@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] introduce panic_gently
Date: 06 Jul 2007 14:03:05 +0200 [thread overview]
Message-ID: <p73hcoh20zq.fsf@bingen.suse.de> (raw)
In-Reply-To: <468DF5D9.4040803@anagramm.de>
Clemens Koller <clemens.koller@anagramm.de> writes:
> Bodo Eggert schrieb:
> > If the boot process failes to find init or the root fs, the cause
> > has usually scrolled off the screen, and because of the panic, it
> > can't be reached anymore.
> > This patch introduces panic_gently, which will allow to use the
> > scrollback buffer and to reboot, but it can't be called from unsafe
> > context.
>
> In the case where you introduced panic_gently() there is IMHO no reason
> to panic() at all. There is no bug which got hit, the machine just needs
> user intervention because of wrong boot parameters (in most cases).
>
> What about asking the user for the correct root= or init= parameters
> and just retry/continue the boot process?
BSDs have a boot shell for this. But not sure it's a good idea.
On EFI systems it might be better to just drop back to the boot environment
where a "re-boot" could be initiated.
> The 180seconds reboot timeout also doesn't make sense here. The problem
> won't go away after a reboot without user interaction.
It will when lilo -R/grubonce were used or the NFS server fixed itself
on nfs root or ... There can be many reasons for it being a good idea.
-Andi
next prev parent reply other threads:[~2007-07-06 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 23:07 [RFC][PATCH] introduce panic_gently Bodo Eggert
2007-07-06 7:57 ` Clemens Koller
2007-07-06 12:03 ` Andi Kleen [this message]
2007-07-06 20:52 ` Oleg Verych
2007-07-06 18:00 ` Chuck Ebbert
2007-07-08 17:24 ` Clemens Koller
2007-07-06 12:05 ` Andi Kleen
2007-07-06 15:24 ` Bodo Eggert
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=p73hcoh20zq.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=7eggert@gmx.de \
--cc=clemens.koller@anagramm.de \
--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