ESXi 6.0 and 6.5 host crashes with PSOD (purple screen of death) - bnx2x_dynamic_alloc_rx_queue_single

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• ESXi 6.0 and 6.5 host crashes with PSOD (purple screen of death).
   
• You see stack entries similar to:

@BlueScreen: #PF Exception 14 in world 33046:helper11-0 IP 0x418012ba7b89 addr 0x0

PTEs:0x4b7d074027;0xb62653027;0xbfffffffff001;

Code start: 0x418012200000 VMK uptime: 32:01:46:52.364

0x439148b1b980:[0x418012ba7b89][email protected]#9.2.3.0+0x281 s

0x439148b1b9c0:[0x418012ba7e17][email protected]#9.2.3.0+0x15b stack: 0x1

0x439148b1ba10:[0x418012babcf4][email protected]#9.2.3.0+0x330 stack: 0x0

0x439148b1baf0:[0x41801293bfae][email protected]#9.2+0xc42 stack: 0x0

0x439148b1bc90:[0x4180123fcb97]UplinkNetqOP@vmkernel#nover+0x127 stack: 0x43910000100f

x439148b1bcf0:[0x4180123fe9bf]UplinkTreeActivatePendingRxQueue@vmkernel#nover+0x42b stack: 0x10000

0x439148b1bdb0:[0x4180123ff9cc]UplinkTreeRxQueueCommitChanges@vmkernel#nover+0x4c stack: 0x43045e09

cpu0:33046)0x439148b1bdf0:[0x41801240513a]UplinkLB_LoadBalanceCB@vmkernel#nover+0xd3e stack: 0x4391608a7200

cpu0:33046)0x439148b1bf00:[0x4180123f8513]UplinkAsyncProcessCallsHelperCB@vmkernel#nover+0x13f stack: 0x43051f

cpu0:33046)0x439148b1bf30:[0x41801225019e]helpFunc@vmkernel#nover+0x3c2 stack: 0x0

cpu0:33046)0x439148b1bfd0:[0x418012414c1e]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0

cpu0:33046)base fs=0x0 gs=0x418040000000 Kgs=0x0

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

vmkernel.<3>[bnx2x_esx_init_rx_ring:1944(vmnic1)]was only able to allocate 0 rx sges

vmkernel.<3>[bnx2x_esx_init_rx_ring:1946(vmnic1)]disabling TPA for queue[4]

vmkernel.<3>[bnx2x_dynamic_alloc_rx_queue_single:789(vmnic1)]Could not start queue:4

vmkernel.)<3>[bnx2x_alloc_rx_sge:734(vmnic3)]Can't alloc sge

Environment

VMware vSphere ESXi 6.0
VMware vSphere ESXi 6.5

Cause

This issue caused due to a memory leak issue identified in driver version bnx2x version 2.712.70.x.3.

Resolution

To resolve this issue upgrade bnx2x driver version to version 2.713.70.v60.6 or higher

 

To download the latest drive for 6.0 and 6.5 for bnx2x, refer this KB article