From: Nicholas Piggin <npiggin@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/2] sreset driven panic/oops message printing fixes
Date: Sun, 24 Dec 2017 02:49:21 +1000 [thread overview]
Message-ID: <20171223164923.10587-1-npiggin@gmail.com> (raw)
Here's a couple of fixes that should go into 4.15 and possibly
stable kernels as well. Most of the time when you hit the system
reset button, either you're a developer with xmon enabled or
customer with a crash dumper enabled. But if neither is the case,
then the result is currently pretty useless. After these patches
we get nice oops trace on each CPU.
Nicholas Piggin (2):
powerpc: System reset avoid interleaving oops using die
synchronisation
powerpc/pseries,ps3: panic flush kernel messages before halting system
arch/powerpc/include/asm/bug.h | 3 ++-
arch/powerpc/kernel/traps.c | 26 +++++++++++++++++++++++++-
arch/powerpc/platforms/powernv/opal.c | 18 ++++--------------
arch/powerpc/platforms/ps3/setup.c | 1 +
arch/powerpc/platforms/pseries/setup.c | 8 +++++++-
5 files changed, 39 insertions(+), 17 deletions(-)
--
2.15.0
next reply other threads:[~2017-12-23 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 16:49 Nicholas Piggin [this message]
2017-12-23 16:49 ` [PATCH 1/2] powerpc: System reset avoid interleaving oops using die synchronisation Nicholas Piggin
2018-01-03 0:49 ` David Gibson
2018-01-22 3:34 ` [1/2] " Michael Ellerman
2017-12-23 16:49 ` [PATCH 2/2] powerpc/pseries, ps3: panic flush kernel messages before halting system Nicholas Piggin
2018-01-03 0:49 ` [PATCH 2/2] powerpc/pseries,ps3: " David Gibson
2018-01-29 4:13 ` [2/2] powerpc/pseries, ps3: " Michael Ellerman
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=20171223164923.10587-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).