ESXi 6.5 Host Fails With a Purple Screen Diagnostic, Indicating That CPU XX / World XXXXXX Tried to Re-Acquire a Lock

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• ESXi 6.5 host crashes with PSOD
• In the coredump.log, You see entries similar to:

@BlueScreen: CPU 48 / World 69844 tried to re-acquire lock

Code start: 0x418029800000 VMK uptime: 42:07:48:15.264

0x4391c6a1a9b0:[0x4180298ec611]PanicvPanicInt@vmkernel#nover+0x545 stack: 0x4180298ec611

0x4391c6a1aa50:[0x4180298ec69d]Panic_NoSave@vmkernel#nover+0x4d stack: 0x4391c6a1aab0

0x4391c6a1aab0:[0x418029821921]LockCheckSelfDeadlockInt@vmkernel#nover+0x95 stack: 0x43065f5e38e0

0x4391c6a1aad0:[0x4180298f2017]MCS_LockWait@vmkernel#nover+0xff stack: 0x43065f5e38e0

0x4391c6a1ab70:[0x4180298f25c3]MCSLockWithFlagsWork@vmkernel#nover+0x23 stack: 0x430758102200

0x4391c6a1ab80:[0x41802982fb68]vmk_SpinlockLock@vmkernel#nover+0x18 stack: 0x43079abff6e0

0x4391c6a1aba0:[0x41802a27cbd7]charOpen@(hpe-ilo)#<None>+0x5b stack: 0x41802985649f

0x4391c6a1ac00:[0x418029900963]VMKAPICharDevDevfsWrapOpen@vmkernel#nover+0x143 stack: 0x41802990095a

0x4391c6a1ac60:[0x418029856722]CharDriverOpenDevice@vmkernel#nover+0x2d6 stack: 0x2

0x4391c6a1acb0:[0x418029852794]FDS_OpenDeviceByDirOID@vmkernel#nover+0x18c stack: 0x4300c810c108

0x4391c6a1ad40:[0x4180298679ec]DevFSFileOpen@vmkernel#nover+0x234 stack: 0x0

0x4391c6a1aeb0:[0x41802983cef4]FSSVec_OpenFile@vmkernel#nover+0x58 stack: 0x5c6a1b340

0x4391c6a1aef0:[0x4180298391a5]FSS_OpenFile@vmkernel#nover+0x19d stack: 0x418029be3cdd

0x4391c6a1b1d0:[0x418029839dc1]FSS_LookupAndOpen@vmkernel#nover+0x16d stack: 0x4180298fd3d8

0x4391c6a1b310:[0x418029ef24af]UserFileOpen@(user)#<None>+0x22b stack: 0x8200000080

0x4391c6a1b480:[0x418029eae7fe]UserObj_TraversePath@(user)#<None>+0x30a stack: 0x43082c84a040

)0x4391c6a1bd10:[0x418029eaee96]UserObj_Open@(user)#<None>+0x52 stack: 0x0

0x4391c6a1be60:[0x418029ef4a3d]LinuxFileDesc_Open@(user)#<None>+0x125 stack: 0x2000000000000

0x4391c6a1bec0:[0x418029f0a3b4]User_ArchLinux32SyscallHandler@(user)#<None>+0x6c stack: 0x0

0x4391c6a1bee0:[0x418029ea7c47]User_LinuxSyscallHandler@(user)#<None>+0xeb stack: 0x33a4af8

0x4391c6a1bf20:[0x41802990e961]User_LinuxSyscallHandler@vmkernel#nover+0x1d stack: 0x0

0x4391c6a1bf30:[0x41802993c044]gate_entry_@vmkernel#nover+0x0 stack: 0x0

base fs=0x0 gs=0x41804c000000 Kgs=0x0

Environment

VMware vSphere ESXi 6.5

Resolution

To resolve the issue, Reboot the host and then upgrade the hpe-ilo driver to version 10.x.x.x, available as follows:

http://vibsdepot.hpe.com/hpe/jan2017/esxi-650-bundles