From: Stewart Smith <stewart@linux.vnet.ibm.com>
To: Balbir Singh <bsingharora@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com
Subject: Re: [RFC] powerpc/powernv/mce: Don't silently restart the machine
Date: Wed, 21 Feb 2018 15:54:20 +1100 [thread overview]
Message-ID: <87vaeruemb.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180221010111.30517-1-bsingharora@gmail.com>
Balbir Singh <bsingharora@gmail.com> writes:
> On MCE the current code will restart the machine with
> ppc_md.restart(). This case was extremely unlikely since
> prior to that a skiboot call is made and that resulted in
> a checkstop for analysis.
>
> With newer skiboots, on P9 we don't checkstop the box by
> default, instead we return back to the kernel to extract
> useful information at the time of the MCE. While we still
> get this information, this patch converts the restart to
> a panic(), so that if configured a dump can be taken and
> we can track and probably debug the potential issue causing
> the MCE.
I agree with the patch, although I'd be nervous stating that skiboot is
going to keep this behaviour. In *theory* we should only ever get a
platform error when there's actually something that isn't the kernel's
fault.
Like any firmware promise though, it's slightly less reliable than one
from a politician.
I'd say that in this case deferring to policy on what to do in event of
panic() is the right thing.
--
Stewart Smith
OPAL Architect, IBM.
next prev parent reply other threads:[~2018-02-21 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 1:01 [RFC] powerpc/powernv/mce: Don't silently restart the machine Balbir Singh
2018-02-21 2:15 ` Nicholas Piggin
2018-02-21 4:54 ` Stewart Smith [this message]
2018-02-21 5:02 ` Balbir Singh
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=87vaeruemb.fsf@linux.vnet.ibm.com \
--to=stewart@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.