PSOD panic with module vmw_satp_alua
Article ID: 451619
Updated On:
Products
Issue/Introduction
This article addresses a PSOD (Purple Screen of Diagnostic) panic occurring with the vmw_satp_alua module on ESXi 9.1 hosts. The issue occurs primarily during automated switch port failover testing.
Panic Details: Crash at 2026-07-21T01:22:24.072Z on CPU 71 running world 2190474 - Storage periodic device probe. VMK Uptime:20:09:07:11.367
Panic Message: @BlueScreen: #GP Exception 13 in world 2190474:Storage peri IP 0x42002b9f31d1
Backtrace:
0x4538d5c1bb90:[0x42002b9f31d1]DLM_malloc@vmkernel#nover+0x835 stack: 0x20, 0x431f8720b010, 0x4538d5c1bbf8, 0x42002c9c7a04, 0x0
0x4538d5c1bc10:[0x42002b9fe0d6]Heap_AlignWithTimeoutAndRA@vmkernel#nover+0x133 stack: 0x42002d3e8177, 0x1000000, 0x431150230000, 0x800c1f500, 0x4538d5c1bc50
0x4538d5c1bc90:[0x42002d3ea9ad][email protected]_alua#0+0x106 stack: 0x8, 0xea00eb032962f85a, 0x100000000000000, 0x8e00f65c595cbc6b, 0x43115021c240
0x4538d5c1bcf0:[0x42002d3e8176][email protected]_alua#0+0x37 stack: 0x42002d3eb32a, 0x431150202980, 0x4538d5c1be31, 0x0, 0x0
0x4538d5c1bd40:[0x42002d3e869d][email protected]_alua#0+0x14a stack: 0x0, 0x0, 0x0, 0x0, 0x4538d5c1bec8
0x4538d5c1bde0:[0x42002d3e8b08][email protected]_alua#0+0x1d stack: 0x431f872b4c80, 0x3, 0x0, 0x42002c9d576e, 0x420051c06840
0x4538d5c1be10:[0x42002c9d576d][email protected]#v3_1_0_0+0xd2 stack: 0x42002c9c4493, 0x42002b86f454, 0x431f01000080, 0x7900d656a51278b6, 0x43077236d5c0
0x4538d5c1be80:[0x42002c9c46b6][email protected]#v3_1_0_0+0x27 stack: 0x43077236d640, 0x42002be3fa96, 0x0, 0x0, 0x42002b82243c
0x4538d5c1bea0:[0x42002be3fa95]PsaStorPluginDeviceProbe@vmkernel#nover+0xbe stack: 0x42002b82243c, 0x4538d5c1002f, 0x42002c9c4690, 0x42002be3faca, 0x0
0x4538d5c1bf00:[0x42002be41314]PsaStorDeviceProbe@vmkernel#nover+0x99 stack: 0x4538d5c1f000, 0xdbaf814af7e8c, 0x43012e601220, 0x430772108c40, 0x4538d5c1f000
0x4538d5c1bf50:[0x42002ba2722c]HelperQueueFunc@vmkernel#nover+0x1d1 stack: 0x0, 0x4538d5c1f000, 0x0, 0x0, 0x0
0x4538d5c1bfe0:[0x42002b823eef]CpuSched_StartWorld@vmkernel#nover+0xe8 stack: 0x0, 0x42002ba0cb68, 0x0, 0x0, 0x0
0x4538d5c1c000:[0x42002ba0cb67]Debug_IsInitialized@vmkernel#nover+0x10 stack: 0x0, 0x0, 0x0, 0x0, 0x0
Environment
VMware vSphere 9.1
Cause
This is a rare issue where heap corruption is found within the private memory pool of the vmw_satp_alua module. This is characterized by a use-after-free scenario where memory is overwritten after being freed, resulting in a system crash upon re-allocation.
Resolution
Currently, this issue is under investigation. To assist with root cause analysis if this PSOD recurs, enable the corruption detection boot options using the following steps:
- Reboot the ESXi host intended for troubleshooting.
- While the host is booting, press Shift+O to pause the process and access the boot options console.
- Add the following text to the existing boot options line:
heapMetadataProtect=TRUE heapPoisonFreeMem=TRUE heapPoisonTimerChecks=TRUE - Press Enter to continue the boot process.
- Note: These options add system-wide performance overhead and should be enabled only on a dedicated test environment.
- Note: These options add system-wide performance overhead and should be enabled only on a dedicated test environment.
- Gather the vm-support bundle and any crash dump (zdump) files if the issue recurs.
- For defects and enhancements, subscribe to this article to receive updates on fix status: Subscribe to KB Updates.
Additional Information
- For general troubleshooting of PSOD events, refer to Understanding Exception 13 and Exception 14 purple diagnostic screen events.
- For information on configuring advanced kernel settings, refer to Configuring advanced options for ESXi.
- For additional support assistance, refer to Contact Broadcom Support.
Feedback
