public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Sam Bobroff <sbobroff@linux•ibm.com>, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH 1/1] powerpc/eeh: differentiate duplicate detection message
Date: Thu, 14 Nov 2019 20:07:52 +1100 (AEDT)	[thread overview]
Message-ID: <47DFxh45YSz9sRd@ozlabs.org> (raw)
In-Reply-To: <43817cb6e6631b0828b9a6e266f60d1f8ca8eb22.1571288375.git.sbobroff@linux.ibm.com>

On Thu, 2019-10-17 at 04:59:37 UTC, Sam Bobroff wrote:
> Currently when an EEH error is detected, the system log receives the
> same (or almost the same) message twice:
> 
> EEH: PHB#0 failure detected, location: N/A
> EEH: PHB#0 failure detected, location: N/A
> or
> EEH: eeh_dev_check_failure: Frozen PHB#0-PE#0 detected
> EEH: Frozen PHB#0-PE#0 detected
> 
> This looks like a bug, but in fact the messages are from different
> functions and mean slightly different things.  So keep both but change
> one of the messages slightly, so that it's clear they are different:
> 
> EEH: PHB#0 failure detected, location: N/A
> EEH: Recovering PHB#0, location: N/A
> or
> EEH: eeh_dev_check_failure: Frozen PHB#0-PE#0 detected
> EEH: Recovering PHB#0-PE#0
> 
> Signed-off-by: Sam Bobroff <sbobroff@linux•ibm.com>

Series applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/de84ffc3ccbeec3678f95a3d898fc188efa0d9c5

cheers

      reply	other threads:[~2019-11-14  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  4:59 [PATCH 1/1] powerpc/eeh: differentiate duplicate detection message Sam Bobroff
2019-11-14  9:07 ` 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=47DFxh45YSz9sRd@ozlabs.org \
    --to=patch-notifications@ellerman$(echo .)id.au \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=sbobroff@linux$(echo .)ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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