ESXi 6.5 host experiences a PSOD with errors related to vmkusb module

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• ESXi 6.5 host experiences a PSOD with errors related to vmkusb module
• The Backtrace will contain entries similar to:

0x43923a59b930:[0x418001d24483]m_allocm@(vmkusb)#<None>+0x2f stack: 0x439569ce23c0
0x43923a59b950:[0x418001d245f7]if_tx_pkt@(vmkusb)#<None>+0x3f stack: 0x4305d1ec0d60
0x43923a59b980:[0x418001d2af87]UetherUplinkTx@(vmkusb)#<None>+0x4f stack: 0x0
0x43923a59b9b0:[0x41800162b2ba]UplinkDevTransmit@vmkernel#nover+0x43e stack: 0x1
0x43923a59ba80:[0x418001e463c5]NetSchedFIFORunLocked@(netsched_fifo)#<None>+0xcd stack: 0x0
0x43923a59baf0:[0x418001e46808]NetSchedFIFOInput@(netsched_fifo)#<None>+0x280 stack: 0x33a59be10
0x43923a59bba0:[0x4180015d9381]IOChain_Resume@vmkernel#nover+0x1b5 stack: 0x4303533103c0
0x43923a59bc50:[0x418001609980]PortOutput@vmkernel#nover+0x118 stack: 0x439d02d31048
0x43923a59bcb0:[0x418001e1241d]TeamES_Output@(etherswitch)#<None>+0x3a5 stack: 0x43035330ffc0
0x43923a59bd10:[0x418001e00ae0]EtherswitchPortDispatch@(etherswitch)#<None>+0x1770 stack: 0x43923a5a7000
0x43923a59bee0:[0x418001609b7c]Port_InputResume@vmkernel#nover+0x120 stack: 0x418001609b6a
0x43923a59bf30:[0x418001fa0435]TcpipTxDispatch@(tcpip4)#<None>+0x8d stack: 0x63
0x43923a59bf50:[0x418001fa0111]TcpipDispatch@(tcpip4)#<None>+0x111 stack: 0x0
0x43923a59bfe0:[0x4180016c8bd5]CpuSched_StartWorld@vmkernel#nover+0x99 stack: 0x0

 

• In the var/log/vmkernel.log, you will see entries similar to:

WARNING: Heap: 3526: Heap vmkusb already at its maximum size. Cannot expand.
WARNING: Heap: 3526: Heap vmkusb already at its maximum size. Cannot expand.
WARNING: Heap: 4157: Heap_Align(vmkusb, 288/288 bytes, 8 align) failed. caller: 0x418001d2447f
WARNING: malloc:169: malloc (size=288, type=0x417fc6a00080, flags=0x101) failed: Out of memory

Environment

VMware Update Manager 6.5
VMware vSphere ESXi 6.5
VMware vCenter Server 6.5.x
VMware vCenter Server Appliance 6.5.x

Resolution

This issue is resolved in ESXi 6.5 U1.