vSAN ESA PSOD with Panic Message of "@BlueScreen: <object_UUID>: Failed to wait for object exit."

Products

• VMware vSAN

Issue/Introduction

Customers may be carrying out host/cluster maintenance and experience a PSOD.

Work tasks may include the below, but are not limited to:

1) Placing a host into maintenance mode (full data evacuation)

2) Running backup processes

3) Increasing cluster workload

The PSOD message may display similar information as the below panic snippet:

2024-09-17T07:44:53.435Z cpu65:2101073)@BlueScreen: 7018a243-d616-2f11-b422-00620ba0a23c: Failed to wait for object exit.
2024-09-17T07:44:53.435Z cpu65:2101073)Code start: 0x420015a00000 VMK uptime: 33:12:57:27.008
2024-09-17T07:44:53.436Z cpu65:2101073)0x453ae299b920:[0x420015b19bda]PanicvPanicInt@vmkernel#nover+0x202 stack: 0x453ae299b970
2024-09-17T07:44:53.436Z cpu65:2101073)0x453ae299b9d0:[0x420015b1a4fc]Panic_vPanic@vmkernel#nover+0x25 stack: 0x0
2024-09-17T07:44:53.436Z cpu65:2101073)0x453ae299b9f0:[0x420015b325e0]vmk_PanicWithModuleID@vmkernel#nover+0x41 stack: 0x453ae299ba50
2024-09-17T07:44:53.436Z cpu65:2101073)0x453ae299ba50:[0x42001815f635][email protected]#0.0.0.1+0xf36 stack: 0x2f
2024-09-17T07:44:53.437Z cpu65:2101073)0x453ae299bec0:[0x420018212d09][email protected]#0.0.0.1+0x12 stack: 0x148acc37b8ddfe
2024-09-17T07:44:53.437Z cpu65:2101073)0x453ae299bee0:[0x420017a9be97][email protected]#0.0.0.1+0x230 stack: 0x148acc37b9537e
2024-09-17T07:44:53.437Z cpu65:2101073)0x453ae299bfa0:[0x420015b3a244]vmkWorldFunc@vmkernel#nover+0x31 stack: 0x420015b3a240
2024-09-17T07:44:53.437Z cpu65:2101073)0x453ae299bfe0:[0x420015e2c149]CpuSched_StartWorld@vmkernel#nover+0xe2 stack: 0x0
2024-09-17T07:44:53.438Z cpu65:2101073)0x453ae299c000:[0x420015adbe7f]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0

 

Environment

vSAN ESA 8.0.2

Cause

The bnxtnet async driver has a known packet leak issue since version 224.0.x

Resolution

The packet leak issue is fixed in NIC driver version 226.0.145.4-1.

Customers with this issue are to upgrade their NIC driver to 226.0.145.4-1 or higher, making sure that the driver and firmware combination also match/are supported.