[OpenPower-Firmware] poor correctable MC errors logging

Sergey Kachkin s.kachkin at gmail.com
Thu Mar 15 00:35:06 AEDT 2018


Hi,

recently there was a number of HMI logging improvements which may help to
isolate the source of HMI errors, but troubleshooting MCs like below is
also challenging.
Can we have additional logging for MCs also?


   1. Feb 15 02:56:33 host kernel: Severe Machine check interrupt
   [Recovered]
   2. Feb 15 02:56:33 host kernel:   Initiator: CPU
   3. Feb 15 02:56:33 host kernel:   Error type: ERAT [Multihit]
   4. Feb 15 02:56:33 host kernel:     Effective address: c00003eefc12f018
   5. Feb 15 03:04:19 host kernel: Severe Machine check interrupt
   [Recovered]
   6. Feb 15 03:04:19 host kernel:   Initiator: CPU
   7. Feb 15 03:04:19 host kernel:   Error type: ERAT [Multihit]
   8. Feb 15 03:04:19 host kernel:     Effective address: c00003eefc12f018
   9.



* [282d5fee5c4f](https://github.com/open-power/skiboot/commit/282d5fee5c4f)
core/hmi: Use pr_fmt macro for tagging log messages
* [c531ff957669](https://github.com/open-power/skiboot/commit/c531ff957669)
opal/hmi: HMI logging with location code info.
* [b33ed1e6b6b0](https://github.com/open-power/skiboot/commit/b33ed1e6b6b0)
core/hmi: Do not display FIR details if none of the bits are set.
* [45a961515be6](https://github.com/open-power/skiboot/commit/45a961515be6)
core/hmi: Display chip location code while displaying core FIR.


thanks,

regards,
Sergey
YADRO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openpower-firmware/attachments/20180314/c2f5d4e1/attachment.html>


More information about the OpenPower-Firmware mailing list