PowerEdge: What is DDR4 Self-healing with Intel Xeon Scalable Processors

There are ongoing improvements and enhancements to the Dell PowerEdge BIOS to improve memory event messaging, error handling, and "self-healing" that occur upon a server reboot. This prevents the need for a scheduled maintenance window or onsite presence to replace a DDR4 memory DIMM that was logging error events.

There are two main memory-related "self-healing" BIOS enhancements that were implemented for PowerEdge Servers with DDR4 running BIOS version 2.1.x and later. These enhancements do change the recommended steps or actions to take if memory events occur and are logged to the LifeCycle log.

1. Memory retraining enhancements

Memory retraining which happens during boot (early in the Configuring Memory steps), optimizes the signal timing and margining for each DIMM/slot for best access. Memory signal timing and margining characteristics of a DIMM may change over time for several different reasons:

• Changes in Server memory configuration
• BIOS changes (Memory Reference Code - MRC)
• Different operating temperatures of the server or DIMM
• The general age of the DIMM

Previously, BIOS updates or memory configuration changes being detected would have resulted in memory retraining occurring during the subsequent boot. Starting with BIOS 2.1.x, additional correctable and uncorrectable memory errors "triggers" were added for scheduled retraining:

Warning - MEM0701 - "Correctable memory error rate exceeded for DIMM_XX."
Critical - MEM0702 - "Correctable memory error rate exceeded for DIMM_XX."
Critical - MEM0005 - "Persistent correctable memory error limit reached for a memory device at location XX."

Any of these errors being logged in the SEL or Lifecycle logs result in Memory retraining being scheduled for the next reboot (warm or cold). BIOS automatically forces a cold reboot regardless of what is initiated.

Critical - MEM0001 - "Multi-bit memory errors detected on memory device at location DIMM_XX."

This Multi-bit error may result in the server rebooting due to a fatal error if the Operating System is unable to handle that error. Memory retraining automatically occur during that boot. If the multi-bit error occurs in a noncritical memory location that that operating system can handle, a reboot must be scheduled.

Memory retraining during POST may "self-heal" the failing DIMM and associated slot by optimizing the signal timing and margining. A DIMM replacement for these errors is not necessary unless memory retraining fails (UEFI0106) during boot or these same errors continue to occur.
 

2. Post Package Repair (PPR)

The second "self-healing' memory enhancement is PPR. PPR repairs a failing memory location by disabling the location or address at the hardware layer enabling a spare memory row to be used instead. The exact number of spare memory rows available depends on the DRAM device and DIMM size.

Previously, this functionality was limited to the manufacturing process. As with the memory retraining enhancements mentioned earlier, there are certain correctable memory errors that result in PPR being scheduled on a specific DIMM slot for the next reboot (warm or cold). BIOS automatically forces a cold reboot regardless of what is initiated. Since the PPR operation is scheduled on a specific DIMM slot, DO NOT change DIMM slot locations until the PPR operation has been run. Examples of the errors are:

Warning - MEM0701- "Correctable memory error rate exceeded for DIMM_XX."
Critical - MEM0702 - "Correctable memory error rate exceeded for DIMM_XX."
Critical - MEM0005 - "Persistent correctable memory error limit reached for a memory device at location XX."

Any of these events in the logs results in PPR being scheduled for the next reboot (warm or cold) early in the Configuring Memory phase

After the reboot, verify that the PPR operation was successfully performed. An example of a successful PPR operation is similar to:

MEM9060 - "The Post Package Repair operation is successfully completed on the Dual In-line Memory Module (DIMM) device that was failing earlier."

A DIMM replacement for these correctable memory errors is not necessary unless the PPR operation. An example of a failing critical PPR message is:

UEFI0278 - "Unable to complete the Post Package Repair (PPR) operation because of an issue in the DIMM memory slot X."

A newly published Whitepaper (version 1.0) describing Dell PowerEdge server Memory-related Reliability, Availability, and Serviceability (RAS) features is now available that describes the various RAS features and capabilities available on the PowerEdge Servers - Memory Errors and Dell PowerEdge YX4X Server Memory RAS Features.

Updated April 24, 2020

Dell is continuing to enhance our "self-healing" capabilities. The following section lists the updates and enhancements associated with the different BIOS versions.

BIOS 2.1.x - Initial article publication of the "self-healing" capabilities available starting with BIOS 2.1.6 and higher, including example error messages and recommended actions.

BIOS 2.4.x and newer changes (December 2019)

• MEM0702 (Correctable error rate exceeded…) - Message updated from a critical to warning. With recommended actions updated to reboot the server to allow "self-healing" to occur - For example, Post Package Repair.
  • December 2019 or newer iDRAC to also be installed to get the updated message
  • Recommended Action: Reboot the server to allow PPR to run
• MEM9060 - Message description updated to indicate "self-healing" was successfully completed

BIOS 2.5.x and newer changes (February 2020)

• A "Correctable Error Logging" BIOS option was added to allow customers to disable all Lifecycle or SEL logging related to correctable errors. All the "self-healing" features continue to function - For example, PPR and memory retraining are still scheduled and run during the next reboot (early in the Configuring Memory process).
• Addition of MEM08xx errors for RDIMMs and LRDIMMs replacing existing error messages and actions. Existing error messages are still used for platforms that do not support the "self-healing" capabilities.
  • February 2020 or newer iDRAC is required for the new messages to be logged.

• MEM0802 - Replaced MEM0702 - correctable error rate exceeded
  • Recommended Action: Reboot the server to allow PPR to run. Confirm that PPR was successful (MEM0802)
• MEM0804 - Replaced MEM9060 indicating PPR was successful. Now includes DIMM slot location that ran PPR
  • Recommended Action: None, this event indicates "self-healing" occurred, no DIMM replacement is needed.
• MEM0805 - Replaced UEFI0278 indicating PPR failed
  • Recommended Action: Replace failing DIMM

Updated July 10, 2020

BIOS 2.7.x and newer changes (July 2020 block BIOS - targeted mid-July for web posting)

• MEM8000 (Correctable error logging disabled) - Starting with BIOS ~2.0.x, Dell Engineering made a BIOS change to enhance the rate of correctable error detection that may impact performance. This change resulted in an uptick in MEM8000 events that were not substantiated from results from DIMM failure analysis. Starting with BIOS 2.7.x there are two changes related to MEM8000. The first is that signaling of the MEM8000 event has been modified. Second, BIOS schedules self-healing (PPR) for the next reboot. iDRAC messages are not yet updated to reflect the new actions.
  • Recommended Action: Reboot the server to allow self-healing/PPR to run. Confirm that PPR was successful (MEM0804).
• MEM0001 (Uncorrectable error) - Results in self-healing (PPR) to be scheduled for the next reboot. iDRAC messages are not yet updated to reflect the new actions.
  • Recommended Action: None needed if the MEM0001 is associated with a critical page that the Operating System is unable to recover - Is still a fatal error resulting in a reboot. If the MEM0001 is associated with a noncritical page that the Operation System can recover from, a reboot must be scheduled to all self-healing (PPR) to occur. Confirm that PPR was successful (MEM0804).

UPDATED January 13, 2021

BIOS 2.8.2 and newer changes (September 2020 block BIOS)

• MEM9072 (Uncorrectable error identified by the memory patrol scrub process- page is not consumed or in use) - Results in self-healing (PPR) to be scheduled for the next reboot. iDRAC messages are not yet updated to reflect the new actions.
  • Recommended Action: Schedule a reboot soon. Delaying the reboot could result in the page being consumed resulting in a MEM0001 error that could result in a reboot occurring. Memory self-healing (PPR) runs during that reboot. Confirm that PPR was successful (MEM0804).

There are additional RAS feature enhancements being evaluated for inclusion in future BIOS updates.

This article is updated as new information becomes available.


Downloads and Drivers: Drivers & Downloads