linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 1/1] powerpc/eeh: differentiate duplicate detection message
@ 2019-10-17  4:59 Sam Bobroff
  2019-11-14  9:07 ` Michael Ellerman
  0 siblings, 1 reply; 2+ messages in thread
From: Sam Bobroff @ 2019-10-17  4:59 UTC (permalink / raw)
  To: linuxppc-dev

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>
---
 arch/powerpc/kernel/eeh_driver.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/powerpc/kernel/eeh_driver.c b/arch/powerpc/kernel/eeh_driver.c
index d9279d0ee9f5..c031be8d41ff 100644
--- a/arch/powerpc/kernel/eeh_driver.c
+++ b/arch/powerpc/kernel/eeh_driver.c
@@ -897,12 +897,12 @@ void eeh_handle_normal_event(struct eeh_pe *pe)
 
 	/* Log the event */
 	if (pe->type & EEH_PE_PHB) {
-		pr_err("EEH: PHB#%x failure detected, location: %s\n",
+		pr_err("EEH: Recovering PHB#%x, location: %s\n",
 			pe->phb->global_number, eeh_pe_loc_get(pe));
 	} else {
 		struct eeh_pe *phb_pe = eeh_phb_pe_get(pe->phb);
 
-		pr_err("EEH: Frozen PHB#%x-PE#%x detected\n",
+		pr_err("EEH: Recovering PHB#%x-PE#%x\n",
 		       pe->phb->global_number, pe->addr);
 		pr_err("EEH: PE location: %s, PHB location: %s\n",
 		       eeh_pe_loc_get(pe), eeh_pe_loc_get(phb_pe));
-- 
2.22.0.216.g00a2a96fc9


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH 1/1] powerpc/eeh: differentiate duplicate detection message
  2019-10-17  4:59 [PATCH 1/1] powerpc/eeh: differentiate duplicate detection message Sam Bobroff
@ 2019-11-14  9:07 ` Michael Ellerman
  0 siblings, 0 replies; 2+ messages in thread
From: Michael Ellerman @ 2019-11-14  9:07 UTC (permalink / raw)
  To: Sam Bobroff, linuxppc-dev

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-11-14  9:39 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-17  4:59 [PATCH 1/1] powerpc/eeh: differentiate duplicate detection message Sam Bobroff
2019-11-14  9:07 ` Michael Ellerman

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).