<div dir="ltr"><div>Hi Mahesh, </div><div><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">thanks for your reply.</span><br></div><div><span class="gmail-" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><br></span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">>We can improve it to print CPU pir number. Do you also want location </span><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">code info there ?</span><br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div>Yes, I would prefer as much info as possible that may help to distinguish one MC problem from another and isolate the root cause. So adding more details would be beneficial. </div><div>Am I correct that CPU numbers etc  will be printed for other similar recoverable errors also?  I have never seen anything except ERAT but wondering if it could be also SLB / TLB multihit etc. </div><div><br></div><div><br></div><div>regards,</div><div>Sergey </div><div>YADRO</div><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 16, 2018 at 6:52 PM, Mahesh Jagannath Salgaonkar <span dir="ltr"><<a href="mailto:mahesh@linux.vnet.ibm.com" target="_blank">mahesh@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03/14/2018 07:05 PM, Sergey Kachkin wrote:<br>
> Hi,<br>
><br>
> recently there was a number of HMI logging improvements which may help to<br>
> isolate the source of HMI errors, but troubleshooting MCs like below is<br>
> also challenging.<br>
> Can we have additional logging for MCs also?<br>
<br>
</span>We can improve it to print CPU pir number. Do you also want location<br>
code info there ?<br>
<br></blockquote><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
><br>
><br>
>    1. Feb 15 02:56:33 host kernel: Severe Machine check interrupt<br>
>    [Recovered]<br>
>    2. Feb 15 02:56:33 host kernel:   Initiator: CPU<br>
>    3. Feb 15 02:56:33 host kernel:   Error type: ERAT [Multihit]<br>
>    4. Feb 15 02:56:33 host kernel:     Effective address: c00003eefc12f018<br>
>    5. Feb 15 03:04:19 host kernel: Severe Machine check interrupt<br>
>    [Recovered]<br>
>    6. Feb 15 03:04:19 host kernel:   Initiator: CPU<br>
>    7. Feb 15 03:04:19 host kernel:   Error type: ERAT [Multihit]<br>
>    8. Feb 15 03:04:19 host kernel:     Effective address: c00003eefc12f018<br>
>    9.<br>
<span class="">><br>
><br>
><br>
> * [282d5fee5c4f](<a href="https://github.com/open-power/skiboot/commit/282d5fee5c4f" rel="noreferrer" target="_blank">https://github.<wbr>com/open-power/skiboot/commit/<wbr>282d5fee5c4f</a>)<br>
> core/hmi: Use pr_fmt macro for tagging log messages<br>
> * [c531ff957669](<a href="https://github.com/open-power/skiboot/commit/c531ff957669" rel="noreferrer" target="_blank">https://github.<wbr>com/open-power/skiboot/commit/<wbr>c531ff957669</a>)<br>
> opal/hmi: HMI logging with location code info.<br>
> * [b33ed1e6b6b0](<a href="https://github.com/open-power/skiboot/commit/b33ed1e6b6b0" rel="noreferrer" target="_blank">https://github.<wbr>com/open-power/skiboot/commit/<wbr>b33ed1e6b6b0</a>)<br>
> core/hmi: Do not display FIR details if none of the bits are set.<br>
> * [45a961515be6](<a href="https://github.com/open-power/skiboot/commit/45a961515be6" rel="noreferrer" target="_blank">https://github.<wbr>com/open-power/skiboot/commit/<wbr>45a961515be6</a>)<br>
> core/hmi: Display chip location code while displaying core FIR.<br>
><br>
><br>
> thanks,<br>
><br>
> regards,<br>
> Sergey<br>
> YADRO<br>
><br>
><br>
><br>
</span>> ______________________________<wbr>_________________<br>
> OpenPower-Firmware mailing list<br>
> <a href="mailto:OpenPower-Firmware@lists.ozlabs.org">OpenPower-Firmware@lists.<wbr>ozlabs.org</a><br>
> <a href="https://lists.ozlabs.org/listinfo/openpower-firmware" rel="noreferrer" target="_blank">https://lists.ozlabs.org/<wbr>listinfo/openpower-firmware</a><br>
><br>
<br>
</blockquote></div><br></div></div>