Commit cb5b242c ("powerpc/eeh: Escalate error on non-existing PE")
escalates the frozen state on non-existing PE to fenced PHB. It
was to improve kdump reliability. After that, commit 361f2a2a
("powrpc/powernv: Reset PHB in kdump kernel") was introduced to
issue complete reset on all PHBs to increase the reliability of
kdump kernel.

Commit cb5b242c becomes unuseful and it would be reverted.

Signed-off-by: Gavin Shan <gws...@linux.vnet.ibm.com>
---
 arch/powerpc/platforms/powernv/eeh-ioda.c | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/arch/powerpc/platforms/powernv/eeh-ioda.c 
b/arch/powerpc/platforms/powernv/eeh-ioda.c
index 65feec6..1b5982f 100644
--- a/arch/powerpc/platforms/powernv/eeh-ioda.c
+++ b/arch/powerpc/platforms/powernv/eeh-ioda.c
@@ -884,13 +884,12 @@ static int ioda_eeh_next_error(struct eeh_pe **pe)
                         * it again.
                         */
                        if (ioda_eeh_get_pe(hose, frozen_pe_no, pe)) {
-                               *pe = phb_pe;
-                               pr_err("EEH: Escalated frozen PHB#%x-"
-                                      "PE#%llx (%s) detected\n",
-                                       hose->global_number,
-                                       frozen_pe_no,
-                                       eeh_pe_loc_get(phb_pe));
-                               ret = EEH_NEXT_ERR_FENCED_PHB;
+                               /* Try best to clear it */
+                               pr_info("EEH: Clear non-existing 
PHB#%x-PE#%llx\n",
+                                       hose->global_number, frozen_pe_no);
+                               opal_pci_eeh_freeze_clear(phb->opal_id, 
frozen_pe_no,
+                                       OPAL_EEH_ACTION_CLEAR_FREEZE_ALL);
+                               ret = EEH_NEXT_ERR_NONE;
                        } else if ((*pe)->state & EEH_PE_ISOLATED) {
                                ret = EEH_NEXT_ERR_NONE;
                        } else {
-- 
1.8.3.2

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to