From: Michael Ellerman <mpe@ellerman.id.au>
To: Ganesh Goudar <ganeshgr@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Ganesh Goudar <ganeshgr@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>
Subject: Re: [PATCH v2] powerpc/mce: log the error for all unrecoverable errors
Date: Tue, 31 Jan 2023 22:29:23 +1100 [thread overview]
Message-ID: <87bkmfeycs.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20230127182943.73073-1-ganeshgr@linux.ibm.com>
Ganesh Goudar <ganeshgr@linux.ibm.com> writes:
> For all unrecoverable errors we are missing to log the
> error, Since machine_check_log_err() is not getting called
> for unrecoverable errors.
>
> Raise irq work in save_mce_event() for unrecoverable errors,
> So that we log the error from MCE event handling block in
> timer handler.
But the patch also removes the irq work raise from machine_check_ue_event().
That's currently done unconditionally, regardless of the disposition. So
doesn't this change also drop logging of recoverable UEs?
Maybe that's OK, but the change log should explain it.
> Log without this change
>
> MCE: CPU27: machine check (Severe) Real address Load/Store (foreign/control memory) [Not recovered]
> MCE: CPU27: PID: 10580 Comm: inject-ra-err NIP: [0000000010000df4]
> MCE: CPU27: Initiator CPU
> MCE: CPU27: Unknown
>
> Log with this change
>
> MCE: CPU24: machine check (Severe) Real address Load/Store (foreign/control memory) [Not recovered]
> MCE: CPU24: PID: 1589811 Comm: inject-ra-err NIP: [0000000010000e48]
> MCE: CPU24: Initiator CPU
> MCE: CPU24: Unknown
> RTAS: event: 5, Type: Platform Error (224), Severity: 3
>
> Signed-off-by: Ganesh Goudar <ganeshgr@linux.ibm.com>
> Reviewed-by: Mahesh Salgaonkar <mahesh@linux.ibm.com>
> ---
> V2: Rephrasing the commit message.
> ---
> arch/powerpc/kernel/mce.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/mce.c b/arch/powerpc/kernel/mce.c
> index 6c5d30fba766..a1cb2172eb7b 100644
> --- a/arch/powerpc/kernel/mce.c
> +++ b/arch/powerpc/kernel/mce.c
> @@ -131,6 +131,13 @@ void save_mce_event(struct pt_regs *regs, long handled,
> if (mce->error_type == MCE_ERROR_TYPE_UE)
> mce->u.ue_error.ignore_event = mce_err->ignore_event;
>
> + /*
> + * Raise irq work, So that we don't miss to log the error for
> + * unrecoverable errors.
> + */
> + if (mce->disposition == MCE_DISPOSITION_NOT_RECOVERED)
> + mce_irq_work_queue();
> +
> if (!addr)
> return;
>
> @@ -235,7 +242,6 @@ static void machine_check_ue_event(struct machine_check_event *evt)
> evt, sizeof(*evt));
>
> /* Queue work to process this event later. */
This comment is meaningless without the function call it's commenting
about, ie. the comment should be removed too.
> - mce_irq_work_queue();
> }
>
cheers
next prev parent reply other threads:[~2023-01-31 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 18:29 [PATCH v2] powerpc/mce: log the error for all unrecoverable errors Ganesh Goudar
2023-01-31 11:29 ` Michael Ellerman [this message]
2023-02-01 9:28 ` Ganesh G R
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=87bkmfeycs.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ganeshgr@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.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).