PSOD occurs at VERIFY bora/vmkernel/sched/cpusched.c

Products

• VMware vSphere ESXi

Issue/Introduction

ESXi Host fails with PSOD "VERIFY bora/vmkernel/sched/cpusched.c"

Backtrace of PSOD will be similar to this:

0x45390a61ae30:[0x4200064fee4f]PanicvPanicInt@vmkernel#nover+0x327 stack: 0x45390a61af08, 0x0, 0x4200064fee4f, 0x0, 0x45390a61ae30
0x45390a61af00:[0x4200064ff3a8]Panic_NoSave@vmkernel#nover+0x4d stack: 0x45390a61af60, 0x45390a61af20, 0x420006aeb96c, 0x4200069f4150, 0x2b8c
0x45390a61af60:[0x4200064ff939]Panic_OnAssertAt@vmkernel#nover+0xba stack: 0x2b8c00000000, 0x4200069f4150, 0x420006ab6e8f, 0x420006ac7846, 0x420006ad2c15
0x45390a61afe0:[0x420006555716]Int6_UD2Assert@vmkernel#nover+0x27f stack: 0x0, 0x0, 0x0, 0x42000654e068, 0x0
0x45390a61b010:[0x42000654e067]gate_entry@vmkernel#nover+0x68 stack: 0x0, 0x4, 0x41ffc68319a0, 0x326262600000000, 0x45390a61f000
0x45390a61b0d0:[0x4200067b2800]CpuSchedWait@vmkernel#nover+0x2e4 stack: 0x68f880e, 0x4200064bffb3, 0x0, 0x0, 0x0
0x45390a61b250:[0x420006504075]SemaphoreLockInt@vmkernel#nover+0xe6 stack: 0x0, 0x45390a61b2a8, 0x420006ac6eb5, 0x43126525a530, 0x4305c5f06140
0x45390a61b2a0:[0x420006423c31]RCU_WaitForGracePeriod@vmkernel#nover+0x42 stack: 0x1000000, 0x300000100, 0xbad0014, 0x420006518bc2, 0x0
0x45390a61b2d0:[0x420006518bc1]vmk_HashRelease@vmkernel#nover+0x66 stack: 0x420006ac6eb5, 0x420007175487, 0x516574616572436b, 0x4307194064d0, 0x30303062
0x45390a61b2f0:[0x420007175486]NetSchedHClkConnect@(netsched_hclk)#<None>+0x6ab stack: 0x30303062, 0x4300d3f27f48, 0x43126525a638, 0x0, 0x26
0x45390a61b760:[0x420006637719]NetSched_DevConnect@vmkernel#nover+0x20a stack: 0x8000000000000, 0x430719406080, 0x430715224650, 0x45390a61b801, 0x4300d3f27f64
0x45390a61b910:[0x420006690180]UplinkDev_ConnectSched@vmkernel#nover+0xd1 stack: 0x0, 0x4300d3f27680, 0x42000668fa28, 0x420006681498, 0x42000669e58c
0x45390a61b990:[0x4200066903fc]UplinkEnableResPoolsSched@vmkernel#nover+0x55 stack: 0x0, 0x4302c5828440, 0x8600000b, 0x42000664413a, 0x45390a61ba38
0x45390a61b9c0:[0x420006644139]NetEvent_PostEvent@vmkernel#nover+0x12a stack: 0x433a7acfb230, 0x3, 0x4305e34d3930, 0x4302c5828480, 0xb
0x45390a61ba50:[0x42000666e79c]Port_PostEventWithCtx@vmkernel#nover+0x131 stack: 0x4305c5e03138, 0x4305e34a4cb4, 0x0, 0x6b, 0xffffffff
0x45390a61baa0:[0x4200066390f6]NetSchedDVPPropResPoolsCfgSet@vmkernel#nover+0x6bb stack: 0x8600000be34d3920, 0x4305c5f06140, 0x4305e34a5670, 0x1, 0x4305e37e2000
0x45390a61bb30:[0x42000660d2fe]DVSClient_PortDataWrite@vmkernel#nover+0x8f stack: 0x7d, 0x4300d3c18000, 0x42000660d321, 0x4305e34a4c20, 0x45390a61bc50
0x45390a61bb90:[0x4200066049dc]DVSPortClientInit@vmkernel#nover+0x99 stack: 0x2065756575712074, 0x120726f66206469, 0x4305e34a4cb4, 0x4300d3c18000, 0x45b941ff000a
0x45390a61bc00:[0x4200066168f0]DVSState_PortDataForEach@vmkernel#nover+0x25 stack: 0x200, 0x4305e34a5670, 0x4305c5f06140, 0x8600000b, 0x8600000b
0x45390a61bc40:[0x42000660a144]DVS_PortLinkUp@vmkernel#nover+0xc5 stack: 0x0, 0x4305e34a5670, 0x0, 0x0, 0x4305e34a3ad0
0x45390a61bcb0:[0x42000666f0b4]Port_Enable@vmkernel#nover+0x2b9 stack: 0x4000, 0x2fed, 0x4307194064d0, 0x430719406080, 0x0
0x45390a61bd00:[0x420006696085]UplinkDev_ConnectAndEnable@vmkernel#nover+0xca stack: 0x4305c5f06140, 0x430723e6fc00, 0x0, 0x42000664a8b8, 0x45390a61be48
0x45390a61bd30:[0x42000664a8b7]NetqueueBalUpdateLSpaceStateToUplink@vmkernel#nover+0xb8 stack: 0x4307194064d0, 0x430723e6fc00, 0xff, 0x430719406080, 0x430723e701d0
0x45390a61bd80:[0x420006651ada]UplinkNetqueueBal_BalanceCB@vmkernel#nover+0x2647 stack: 0x4307194064d0, 0x0, 0x430723e00007, 0x430700000020, 0x7
0x45390a61bf10:[0x42000675a520]UplinkAsyncProcessCallsHelperCB@vmkernel#nover+0x119 stack: 0x148ec076d196d38, 0x4301a9601220, 0x43099ae01750, 0x4200064da06a, 0x6
0x45390a61bf40:[0x4200064da069]HelperQueueFunc@vmkernel#nover+0x1d2 stack: 0x45390a620b48, 0x43099ae01238, 0x45390a61f000, 0x45390a61f000, 0x43099ae012c0
0x45390a61bfe0:[0x4200067b33e1]CpuSched_StartWorld@vmkernel#nover+0x86 stack: 0x0, 0x4200064c4b50, 0x0, 0x0, 0x0
0x45390a61c000:[0x4200064c4b4f]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0, 0x0, 0x0, 0x0, 0x0

Environment

VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Cause

This issue occurs due to a known issue under the high resource usage.

Resolution

Currently, there is no resolution.
VMware by Broadcom Engineering notices this issue and will be fixed in the future release.