From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v3 1/3] powernv/mce: reduce mce console logs to lesser lines.
Date: Fri, 3 May 2019 16:59:26 +1000 (AEST) [thread overview]
Message-ID: <44wNKV0SlRz9sPX@ozlabs.org> (raw)
In-Reply-To: <155656174872.20636.6539465047019566013.stgit@jupiter>
On Mon, 2019-04-29 at 18:15:48 UTC, Mahesh Salgaonkar wrote:
> Also add cpu number while displaying mce log. This will help cleaner logs
> when mce hits on multiple cpus simultaneously.
>
> before the changes the mce o/p was:
>
> [ 127.223515] Severe Machine check interrupt [Recovered]
> [ 127.223530] NIP [d00000000ba80280]: insert_slb_entry.constprop.0+0x278/0x2c0 [mcetest_slb]
> [ 127.223539] Initiator: CPU
> [ 127.223544] Error type: SLB [Multihit]
> [ 127.223550] Effective address: d00000000ba80280
>
> After this patch series changes the mce o/p will be:
>
> [ 471.959843] MCE: CPU80: machine check (Warning) Host SLB Multihit [Recovered]
> [ 471.959870] MCE: CPU80: NIP: [d00000000b550280] insert_slb_entry.constprop.0+0x278/0x2c0 [mcetest_slb]
> [ 471.959892] MCE: CPU80: Probable software error (some chance of hardware cause)
>
> UE in host application:
>
> [ 1001.831517] MCE: CPU48: machine check (Severe) Host UE Load/Store DAR: 00007fffc6079a80 paddr: 0000000f8e260000 [Not recovered]
> [ 1001.831518] MCE: CPU48: PID: 4584 Comm: find NIP: [0000000010023368]
> [ 1001.831519] MCE: CPU48: Hardware error
>
> and for MCE in Guest:
>
> [ 1289.447571] MCE: CPU80: machine check (Warning) Guest SLB Multihit DAR: 000001001b6e0320 [Recovered]
> [ 1289.447615] MCE: CPU80: PID: 24765 Comm: qemu-system-ppc Guest NIP: [00007fffa309dc60]
> [ 1289.447634] MCE: CPU80: Probable software error (some chance of hardware cause)
>
> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/d6e8a150850601277039a548ffcdddd1
cheers
prev parent reply other threads:[~2019-05-03 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 18:15 [PATCH v3 1/3] powernv/mce: reduce mce console logs to lesser lines Mahesh Salgaonkar
2019-04-29 18:15 ` [PATCH v3 2/3] powernv/mce: Print correct severity for mce error Mahesh Salgaonkar
2019-04-29 18:16 ` [PATCH v3 3/3] powernv/mce: print additional information about " Mahesh Salgaonkar
2019-05-03 6:59 ` Michael Ellerman [this message]
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=44wNKV0SlRz9sPX@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--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 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).