VMware ESXi 5.1.x host fails with a purple diagnostic screen and reports the error: PANIC bora/vmkernel/main/dlmalloc.c:4827 - Usage error in dlmalloc - TcpipAllocPort

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Cannot start VMware ESXi 5.1.x host.
• VMware ESXi 5.1.x host fails with a purple diagnostic screen.
• You see a backtrace similar to:
  

<YYYY-MM_DD><time> cpu26:9842)VMware ESXi 5.1.0 [Releasebuild-1312873 x86_64]
PANIC bora/vmkernel/main/dlmalloc.c:4827 - Usage error in dlmalloc
<YYYY-MM_DD><time> cpu26:9842)cr0=0x80010031 cr2=0x18d9a180 cr3=0x14489f000 cr4=0x42768
<YYYY-MM_DD><time> cpu26:9842)pcpu:0 world:11465 name:"vmm0:ccbv-vpmob-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:1 world:10512 name:"vmm0:ccbv-vdm-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:2 world:10515 name:"vmm2:ccbv-vdm-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:3 world:11467 name:"vmm1:ccbv-vpmob-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:4 world:10516 name:"vmm3:ccbv-vdm-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:5 world:11468 name:"vmm2:ccbv-vpmob-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:6 world:10685 name:"vmm0:ccbv-gis-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:7 world:11469 name:"vmm3:ccbv-vpmob-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:8 world:8200 name:"idle8" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:9 world:10505 name:"vmm2:ccbv-NWSMSPProd" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:10 world:10502 name:"vmm0:ccbv-NWSMSPProd" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:11 world:8203 name:"idle11" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:12 world:10504 name:"vmm1:ccbv-NWSMSPProd" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:13 world:8205 name:"idle13" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:14 world:10674 name:"vmx" (U)
<YYYY-MM_DD><time> cpu26:9842)pcpu:15 world:10506 name:"vmm3:ccbv-NWSMSPProd" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:16 world:8208 name:"idle16" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:17 world:153189 name:"vmm2:ccb-fs-01-new" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:18 world:8210 name:"idle18" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:19 world:8211 name:"idle19" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:20 world:11058 name:"vmx-mks:ccbv-gis-01" (U)
<YYYY-MM_DD><time> cpu26:9842)pcpu:21 world:8213 name:"idle21" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:22 world:8214 name:"idle22" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:23 world:8215 name:"idle23" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:24 world:8248 name:"helper11-0" (SH)
<YYYY-MM_DD><time> cpu26:9842)pcpu:25 world:8217 name:"idle25" (IS)
<YYYY-MM_DD><time> cpu26:9842)pcpu:26 world:9842 name:"dcui" (U)
<YYYY-MM_DD><time> cpu26:9842)pcpu:27 world:10501 name:"vmx" (U)
<YYYY-MM_DD><time> cpu26:9842)pcpu:28 world:10677 name:"vmm1:ccbv-gprc-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:29 world:10678 name:"vmm2:ccbv-gprc-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:30 world:10679 name:"vmm3:ccbv-gprc-01" (V)
<YYYY-MM_DD><time> cpu26:9842)pcpu:31 world:85425 name:"vmm3:ccbv-trsr-01" (V)
<YYYY-MM_DD><time> cpu26:9842)@BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4827 - Usage error in dlmalloc
<YYYY-MM_DD><time> cpu26:9842)Code start: 0x418007800000 VMK uptime: 2:16:08:13.840
<YYYY-MM_DD><time> cpu26:9842)0x412259c9b530:[0x41800787ae0a]PanicvPanicInt@vmkernel#nover+0x61 stack: 0x3000000008
<YYYY-MM_DD><time> cpu26:9842)0x412259c9b610:[0x41800787b6fb]Panic@vmkernel#nover+0xae stack: 0x410027836580
<YYYY-MM_DD><time> cpu26:9842)0x412259c9b630:[0x41800783352d]DLM_free@vmkernel#nover+0x600 stack: 0x27836580
<YYYY-MM_DD><time> cpu26:9842)0x412259c9b670:[0x418007845235]Heap_Free@vmkernel#nover+0x164 stack: 0x0
<YYYY-MM_DD><time> cpu26:9842)0x412259c9b6c0:[0x418007eed622]TcpipAllocPort@<None>#<None>+0x34d stack: 0x412259c9b8f0
<YYYY-MM_DD><time> cpu26:9842)0x412259c9bba0:[0x418007eed945]TcpipOpenPort@<None>#<None>+0x2d4 stack: 0x41220000ffff
<YYYY-MM_DD><time> cpu26:9842)0x412259c9bbe0:[0x418007eee65f]TcpipAttachInterface@<None>#<None>+0x52 stack: 0x41000000ffff
<YYYY-MM_DD><time> cpu26:9842)0x412259c9bc40:[0x418007eeeaa4]Tcpip_VSIPlumbSet@<None>#<None>+0xdb stack: 0xffff
<YYYY-MM_DD><time> cpu26:9842)0x412259c9bd90:[0x418007979fc1]NetVsi_TcpipPlumbSet@vmkernel#nover+0x334 stack: 0x4180079707e0
<YYYY-MM_DD><time> cpu26:9842)0x412259c9be20:[0x418007b321b4]VSI_SetInfo@vmkernel#nover+0x17b stack: 0x41002f5c12f0
<YYYY-MM_DD><time> cpu26:9842)0x412259c9beb0:[0x418007ca861d]UWVMKSyscallUnpackVSI_Set@<None>#<None>+0x1d0 stack: 0x1004180079b86
<YYYY-MM_DD><time> cpu26:9842)0x412259c9bef0:[0x418007c79348]User_UWVMKSyscallHandler@<None>#<None>+0xa3 stack: 0x0
<YYYY-MM_DD><time> cpu26:9842)0x412259c9bf10:[0x4180078a8772]User_UWVMKSyscallHandler@vmkernel#nover+0x19 stack: 0xfff05cd8
<YYYY-MM_DD><time> cpu26:9842)0x412259c9bf20:[0x418007910064]gate_entry@vmkernel#nover+0x63 stack: 0x0
<YYYY-MM_DD><time> cpu26:9842)base fs=0x0 gs=0x418046800000 Kgs=0x0</time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time></time>

Environment

VMware vSphere ESXi 5.1

Cause

This issue occurs if there is an issue with CPU hardware.

Resolution

To resolve this issue, contact your hardware vendor for assistance. Also, consider a BIOS upgrade, if available.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box