PowerEdge: CPU0704 Machine Check Errors Reflect Inaccurate CPU Index in iDRAC10 Lifecycle Log

Dell PowerEdge 17G servers adopted Open Compute Project's Data Center Modular Hardware System (DC-MHS) architecture. As part of the standard, CPUs are indexed starting with "0" on the Host Processor Module (HPM). The internal library leveraged by iDRAC10 is shared with previous generations of PowerEdge servers that started CPU indexing with "1." iDRAC10 firmware versions earlier than v1.20.80.50 inaccurately reflects the CPU index number within CPU0704 MCE events. Both the SEL and LCLOG reflect a +1 value within the error message string.
 

iDRAC10 UI >> System >> Overview >> Components >> Processor Indexing Example:

In the SEL and LCLOG examples below, the CPU machine check error occurred on CPU1 while the event string indicates that an error occurred on CPU2. An MCE event on CPU0 would be recorded as CPU1 in the event string.

SEL Example:

2025-07-07 17:50:51        1004        CPU 2 machine check error detected.

LCLOG Example:

2025-07-07 17:50:51        5617        CPU0704        CPU 2 machine check error detected.

2025-07-07 17:50:51        5615        CPU0000        Internal error has occurred check for additional logs.

2025-07-07 17:48:15        5591        CPU0704        CPU 2 machine check error detected.

2025-07-07 17:48:14        5589        CPU0000        Internal error has occurred check for additional logs.

iDRAC10 leverages a shared library with iDRAC9 that previously parsed CPU indexing starting with value 1 when processing the argument for the CPU0704 error event string.

iDRAC10 firmware 1.20.80.50 and December 2025 17G PowerEdge server BIOS releases add logic to properly parse the CPU index information received from the server BIOS.
BIOS release versions vary by server product model. Refer to table below for the BIOS Releases that introduce the corrected enumeration support for iDRAC10.