From: Russell Currey <ruscur@russell.cc>
To: Stewart Smith <stewart@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V2] powerpc/powernv: Add a kmsg_dumper that flushes console output on panic
Date: Fri, 27 Nov 2015 17:15:13 +1100 [thread overview]
Message-ID: <1448604913.1291.2.camel@russell.cc> (raw)
In-Reply-To: <m3oaegm24h.fsf@oc8180480414.ibm.com>
On Fri, 2015-11-27 at 16:40 +1100, Stewart Smith wrote:
> Russell Currey <ruscur@russell.cc> writes:
> > On BMC machines, console output is controlled by the OPAL firmware and is
> > only flushed when its pollers are called. When the kernel is in a panic
> > state, it no longer calls these pollers and thus console output does not
> > completely flush, causing some output from the panic to be lost.
> >
> > This patch adds a new kmsg_dumper which gets called at panic time to ensure
> > panic output is not lost. It accomplishes this by calling
> > OPAL_CONSOLE_FLUSH
> > in the OPAL API, and if that is not available, the pollers are called
> > enough
> > times to (hopefully) completely flush the buffer.
>
> You may want to add to commit message that this depends on:
> https://patchwork.ozlabs.org/patch/547379/
>
It doesn't *depend* on it, it's just preferred. It still works with older
Skiboot versions. I will mention it in the actual commit message for the
next revision, though.
> (which I'm about to go review)
>
> Considering this does address an actual bug, should this go to stable@ ?
>
> (Same question for the skiboot patch)
>
Yes, both this patch and the corresponding Skiboot patch should go to stable.
next prev parent reply other threads:[~2015-11-27 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 3:26 [PATCH V2] powerpc/powernv: Add a kmsg_dumper that flushes console output on panic Russell Currey
2015-11-27 5:12 ` Andrew Donnellan
2015-11-27 5:40 ` Stewart Smith
2015-11-27 6:15 ` Russell Currey [this message]
2015-11-27 7:21 ` Stewart Smith
2015-11-30 2:07 ` Russell Currey
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=1448604913.1291.2.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stewart@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).