From: Ralf Baechle <ralf@linux-mips.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: "James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
linux-mips@linux-mips.org, linux-parisc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] MIPS/PA-RISC: panic immediately when panic_on_oops
Date: Thu, 10 Mar 2016 01:09:07 +0100 [thread overview]
Message-ID: <20160310000907.GD15652@linux-mips.org> (raw)
In-Reply-To: <1457554123-18491-1-git-send-email-aaro.koskinen@iki.fi>
On Wed, Mar 09, 2016 at 10:08:41PM +0200, Aaro Koskinen wrote:
> MIPS and PA-RISC want to sleep 5 seconds before panicking when
> panic_on_oops is set, with no apparent reason. We should remove
> this feature, since some users may want their systems to fail as
> quickly as possible.
>
> Users who want to delay reboot after panic can use PANIC_TIMEOUT.
>
> Also, this change will unify the behaviour with other architectures.
I did a bit of dumpster diving, commit cea6a4ba8acfba6f59cc9ed71e0d05cb770b9d9c
("[PATCH] panic_on_oops: remove ssleep()") removed the 5 second delay
from ARM, i386, ia64, powerpc, x86_64 and xtensa on 2006-03-07.
The idea once upon a time probably was to keep the panic message on the
console long enough so somebody has _maybe_ a chance to read it. Which
is a pretty weak solution.
Ralf
prev parent reply other threads:[~2016-03-10 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 20:08 [PATCH 0/2] MIPS/PA-RISC: panic immediately when panic_on_oops Aaro Koskinen
2016-03-09 20:08 ` [PATCH 1/2] MIPS: " Aaro Koskinen
2016-03-09 20:08 ` [PATCH 2/2] PA-RISC: " Aaro Koskinen
2016-03-09 21:03 ` Helge Deller
2016-03-10 0:09 ` Ralf Baechle [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=20160310000907.GD15652@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=aaro.koskinen@iki.fi \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@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