Flashes (Alerts)
Abstract
The CPU register data is not processed or saved when the POWER Hypervisor (PHYP) terminates the LPAR and the FADump is configured on the Linux LPAR.
Content
Linux Releases Affected
All Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES) releases
IBM Systems Affected
All IBM® Power Systems
All IBM® Power Systems
Description
An IBM Power System LPAR can be terminated by the PHYP for different reasons. If the FADump was configured on the Linux LPAR when PHYP terminated the LPAR, then the platform-assisted dump is initiated to save the kernel dump. However, the CPU register data is not processed or saved in the vmcore because the CPU mask is set in crash_fadump() at the time of kernel crash and it remains unset when the LPAR is terminated abruptly by PHYP.
Look at reference code (B700F104) from the HMC to confirm whether a PHYP initiated platform-assisted dump was triggered. Word 13 in the SRC indicates the reason PHYP terminated the LPAR.
Workaround
None. However, data in the vmcore can be inspected to identify the root cause. Only the CPU register data, which gives a better understanding of the system context when PHYP terminated the LPAR, is missing.
Fix Outlook
IBM is working on a fix. This fix will ensure the CPU register data is also part of the vmcore for such scenarios. The fix will come as part of a future RHEL or SLES release. If a fix pack is needed before the next release, open a support ticket with Red Hat or SUSE.
[{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SGMV157","label":"IBM Support for Red Hat Enterprise Linux Server"},"ARM Category":[{"code":"a8m0z000000Gnl7AAC","label":"Red Hat Enterprise Linux"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
05 May 2022
UID
ibm16573191