From: Olaf Hering <olaf@aepfle.de>
To: Mandeep Singh Baines <msb@chromium.org>
Cc: linux-kernel@vger.kernel.org, Hugh Dickins <hughd@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Huang Ying <ying.huang@intel.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] panic: panic=-1 for immediate reboot
Date: Wed, 22 Jun 2011 11:39:03 +0200 [thread overview]
Message-ID: <20110622093903.GA1981@aepfle.de> (raw)
In-Reply-To: <1308612129-12488-1-git-send-email-msb@chromium.org>
On Mon, Jun 20, Mandeep Singh Baines wrote:
> From: Hugh Dickins <hughd@chromium.org>
>
> When kernel BUG or oops occurs, ChromeOS intends to panic and immediately
> reboot, with stacktrace and other messages preserved in RAM across reboot.
> But the longer we delay, the more likely the user is to poweroff and lose
> the info.
I have no strong opinion here, but:
Is delaying one second (instead of say 180 like on powerpc) such a big
deal if the system is dead anyway?
Olaf
next prev parent reply other threads:[~2011-06-22 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 23:22 [PATCH 1/2] panic: panic=-1 for immediate reboot Mandeep Singh Baines
2011-06-20 23:22 ` [PATCH 2/2] panic: do not unblank_screen when panic_timeout < 0 Mandeep Singh Baines
2011-06-22 22:30 ` [PATCH] panic, vt: do not force oops output " Mandeep Singh Baines
2011-07-06 23:33 ` Andrew Morton
2011-07-15 22:57 ` Mandeep Singh Baines
2011-07-07 7:53 ` Alan Cox
2011-07-15 21:39 ` Mandeep Singh Baines
2011-07-15 23:17 ` Alan Cox
2011-06-22 9:39 ` Olaf Hering [this message]
2011-06-22 22:17 ` [PATCH 1/2] panic: panic=-1 for immediate reboot Mandeep Singh Baines
-- strict thread matches above, loose matches on Subject: below --
2011-07-15 22:39 Mandeep Singh Baines
2011-07-15 22:56 ` Mandeep Singh Baines
2011-07-15 22:53 Mandeep Singh Baines
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=20110622093903.GA1981@aepfle.de \
--to=olaf@aepfle.de \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msb@chromium.org \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox