/var/log/hostlog/kern.log prints the below MCE Hardware Error:

2024-12-03T22:08:22.721334+05:30 intel-x86-64 kernel: mce: [Hardware Error]: PROCESSOR 0:406f1 TIME 1733243872 SOCKET 1 APIC 20 microcode b00002e

2024-12-03T22:08:22.721341+05:30 intel-x86-64 kernel: mce: [Hardware Error]: PROCESSOR 0:406f1 TIME 1733243872 SOCKET 1 APIC 28 microcode b00002e

Above said MCE logs are printed intermittently causing no service impact.

At times, this could result System Abnormal Shutdown.

These MCE Errors are an indication of possible HW issue.

However, if the Errors are printed occasionally, those can be considered Transient and can be ignored.

Aggressive logging of these MCE Errors needs thorough investigation.

• Check the History of the log line inception. Since when it started and how frequently its appearing.
• Co-relate the MCE logs with chassisd and messages log.
• If PCI or other FPC errors in chassisd or messages logs are supported by the MCE Errors, consider RMA of the Unit.

These MCE logs are related to the PROCESSOR:

2024-12-03T22:08:22.721334+05:30 intel-x86-64 kernel: mce: [Hardware Error]: PROCESSOR 0:406f1 TIME 1733243872 SOCKET 1 APIC 20 microcode b00002e

2024-12-03T22:08:22.721341+05:30 intel-x86-64 kernel: mce: [Hardware Error]: PROCESSOR 0:406f1 TIME 1733243872 SOCKET 1 APIC 28 microcode b00002e

For getting the exact CPU reporting issue, the APIC ID and the microcode will help narrowing it down:

From the RSI:

-------------

=== fpc0> show usp jsf rtcom client 13

processor : 9

model name : Intel(R) Xeon(R) CPU E5-2658 v4 @ 2.30GHz

microcode : 0xb00002e <<<<<

apicid : 20 <<<<<<<<<<<<

initial apicid : 20

processor : 13

model name : Intel(R) Xeon(R) CPU E5-2658 v4 @ 2.30GHz

microcode : 0xb00002e <<<<<<

apicid : 28 <<<<<<<<<<<<<

initial apicid : 28

Raise a JTAC ticket if the errors are persistent with RSI and All Logs.