aboutsummaryrefslogtreecommitdiffstats
path: root/arch/powerpc/platforms/pseries
diff options
context:
space:
mode:
authorAnton Blanchard <anton@samba.org>2011-01-11 14:46:29 -0500
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2011-01-20 22:08:37 -0500
commit3f9793e6b66efcf196974ee4f0d62de6282eb41b (patch)
tree6c81217c47f23d9c486f0bb60e0806f54b6582bc /arch/powerpc/platforms/pseries
parenta443506b8598bbd784cfe403ad1db2c7083ff465 (diff)
powerpc: Never halt RTAS error logging after receiving an unrecoverable machine check
Newer versions of the System p firwmare send a partial RTAS error log in the machine check handler with a more detailed response appearing sometime later via check event. This means at machine check time we do not have enough information to ascertain exactly what went on. Furthermore, I have found the RTAS error logs in the machine check handler contain no useful information, so halting on them makes little sense. If we want to halt it would make more sense to do it following the error log received sometime later via check event. In light of this, never halt the error log in the pseries machine check handler. Signed-off-by: Anton Blanchard <anton@samba.org> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/powerpc/platforms/pseries')
-rw-r--r--arch/powerpc/platforms/pseries/ras.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/powerpc/platforms/pseries/ras.c b/arch/powerpc/platforms/pseries/ras.c
index a4fc6da87c2e..048e25711c6b 100644
--- a/arch/powerpc/platforms/pseries/ras.c
+++ b/arch/powerpc/platforms/pseries/ras.c
@@ -281,7 +281,7 @@ static int recover_mce(struct pt_regs *regs, struct rtas_error_log * err)
281 nonfatal = 1; 281 nonfatal = 1;
282 } 282 }
283 283
284 log_error((char *)err, ERR_TYPE_RTAS_LOG, !nonfatal); 284 log_error((char *)err, ERR_TYPE_RTAS_LOG, 0);
285 285
286 return nonfatal; 286 return nonfatal;
287} 287}