From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mandeep Singh Baines <msb@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Huang Ying <ying.huang@intel.com>,
Andi Kleen <ak@linux.intel.com>, Hugh Dickins <hughd@google.com>,
Olaf Hering <olaf@aepfle.de>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Dave Airlie <airlied@gmail.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: [PATCH 2/2] panic, vt: do not force oops output when panic_timeout < 0
Date: Sat, 16 Jul 2011 00:15:51 +0100 [thread overview]
Message-ID: <20110716001551.52e817e4@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1310770401-10739-2-git-send-email-msb@chromium.org>
> already storing the panic in RAM and are going to reboot immediately, there
> is no benefit in mode switching back to the vc in order to display the panic
> output. The log buffer will get flushed by the console_unblank() call so
> remote management consoles should see all output.
Doesn't seem too unreasonable and its probably a behaviour (although with
netconsole) that a lot of server farms would prefer too.
Acked-by: Alan Cox <alan@linux.intel.com>
next prev parent reply other threads:[~2011-07-15 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 22:53 [PATCH 1/2] panic: panic=-1 for immediate reboot Mandeep Singh Baines
2011-07-15 22:53 ` [PATCH 2/2] panic, vt: do not force oops output when panic_timeout < 0 Mandeep Singh Baines
2011-07-15 23:15 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-15 22:39 [PATCH 1/2] panic: panic=-1 for immediate reboot Mandeep Singh Baines
2011-07-15 22:40 ` [PATCH 2/2] panic, vt: do not force oops output when panic_timeout < 0 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=20110716001551.52e817e4@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=airlied@gmail.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=hughd@google.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msb@chromium.org \
--cc=olaf@aepfle.de \
--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
all inboxes | Powered by JetHome®