ESXi 6.5 host fails with a Purple Diagnostic Screen with error: World nnnn tried to re-acquire lock

Products

• VMware vSphere ESXi

Issue/Introduction

The purpose of this article is to make aware of the address lock issues seen on the HP hardware.

Symptoms:

• The ESXi host 6.5 fails with a purple diagnostic screen similar to.
  
  CPU 29 / World 67970 tried to re-acquire lock
  
  Note: The CPU Number World ID will vary.
  
  
• You see the backtrace mentioning LockCheckSelfDeadlock, similar to:
  
  PanicvPanicInt
  Panic_NoSave
  LockCheckSelfDeadlockInt
  MCS_LockWait
  MCSLockWithFlagsWork
  vmk_SpinlockLock
  charOpen@(hpe-ilo)
  VMKAPICharDevDevfsWrapOpen
  CharDriverOpenDevice
  FDS_OpenDeviceByDirOID
  DevFSFileOpen
  FSSVec_OpenFile
  FSS_OpenFile
  FSS_LookupAndOpen
  UserFileOpen
  UserObj_TraversePath
  UserObj_Open
  LinuxFileDesc_Open
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vSphere ESXi 6.5

Cause

This issue occurs due to a known issue in the hp-ilo driver 650.10.0.1-24.

Resolution

To resolve this issue, update the hp-ilo driver to version 650.10.0.2 or later. For more information, see the HPE article c05378386.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Additional Information

ESXi 6.5 主机失败并显示紫色诊断屏幕及以下错误：域 nnnn 尝试重新获取锁定 (World nnnn tried to re-acquire lock)
ESXi 6.5 ホストが、パープル スクリーンに表示される次のエラーで失敗する：ワールド nnnn でロックの再取得を試みました (World nnnn tried to re-acquire lock)