Panic Details: Crash at 20##-##-##T##:##:##.###Z on CPU 62 running world 20#####. VMK Uptime:###:##:##:##.###
Panic Message: @BlueScreen: VERIFY bora/vmkernel/sched/cpusched.c:11252
Backtrace (top 8 lines):
#####a####bb##:[##########bbc#]PanicvPanicInt@vmkernel#nover+####c stack: #####a####f###, ##########bbc#, ###, #############1, ##########bbc#
#####a####bc##:[##########c##c]Panic_NoSave@vmkernel#nover+###d stack: #####a####bc##, #####a####bc##, ###, ###########ea#, ###bf#
#####a####bc##:[##########c###]Panic_OnAssertAt@vmkernel#nover+0#ba stack: ###bf#00000000, ###########ea#, ###########d##, ###########f##, ##############
#####a####bd##:[#########a##e#]Int6_UD2Assert@vmkernel#nover+0###0 stack: 0#0, 0#0, 0#0, 0#########b#c#, 0#0
#####a####bd##:[##########b#c#]gate_entry@vmkernel#nover+##a# stack: 0#0, ##bfffffff, 0#0, #####ffeeb#c####, 0#0
#####a####bdf#:[#########d###f]CpuSchedWait@vmkernel#nover+####b stack: ##################, 0#0, 0#0, ####e##c######, #####a####bf##
#####a####bf##:[#########e###a]TcpipDispatchWorld@(tcpip4)#<None>+##### stack: 0#0, 0#0, 0#0, 0#0, 0#0
#####a####bfe#:[#########d##b#]CpuSched_StartWorld@vmkernel#nover+##bf stack: 0#0, ###########cf#, 0#0, 0#0, 0#0
VMware vSphere ESXi 8.x
The crash is caused by an incorrect CPU preemption state. This is a per-CPU state monitored by the VMkernel scheduler; when an unexpected state is detected, the kernel triggers an assertion failure.
There is currently no resolution. Broadcom Engineering is working on code changes which will be included in a future release.
Engage the hardware vendor to perform exhaustive diagnostics on CPU and memory to rule out underlying physical defects.
If the issue is reproducible Contact Support.