diff options
| author | Vasant Hegde <hegdevasant@linux.vnet.ibm.com> | 2020-03-04 14:28:07 +0530 |
|---|---|---|
| committer | Oliver O'Halloran <oohall@gmail.com> | 2020-03-11 17:23:49 +1100 |
| commit | daf9215c85f910043c472984683948baaf18da39 (patch) | |
| tree | 44864c41da8b46f168c38818d914026a80f131d3 | |
| parent | 033e797cb0d77b151ab6e47d8fb7666a09641107 (diff) | |
| download | skiboot-daf9215c85f910043c472984683948baaf18da39.zip skiboot-daf9215c85f910043c472984683948baaf18da39.tar.gz skiboot-daf9215c85f910043c472984683948baaf18da39.tar.bz2 | |
errorlog: Increase the severity of abnormal reboot events
Currently Linux will usually call opal_cec_reboot2() in response to
unrecoverable HMIs and other serious hardware errors. OPAL handles
platform errors by sending an error log to the BMC / FSP and
triggering a software checkstop.
Sending error logs to the BMC / FSP is normally an async operation,
but in this path we need to ensure that error logs are sent out before
the xstop is triggered. The easiest way to do that is to escalate the
severity of the generated error log from "abnormal reboot" to "panic"
since we force panic logs to be send synchronusly. It's also a more
accurate description of what's happening.
CC: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com>
Reviewed-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com>
[oliver: commit message]
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
| -rw-r--r-- | core/platform.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/core/platform.c b/core/platform.c index 9593f3a..85b2cd2 100644 --- a/core/platform.c +++ b/core/platform.c @@ -27,7 +27,7 @@ bool manufacturing_mode = false; struct platform platform; DEFINE_LOG_ENTRY(OPAL_RC_ABNORMAL_REBOOT, OPAL_PLATFORM_ERR_EVT, OPAL_CEC, - OPAL_CEC_HARDWARE, OPAL_PREDICTIVE_ERR_FAULT_RECTIFY_REBOOT, + OPAL_CEC_HARDWARE, OPAL_ERROR_PANIC, OPAL_ABNORMAL_POWER_OFF); /* |