During packet tracing, ESXi 5.5 host halts with purple diagnostic screen error: @BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4892 - Usage error in dlmalloc
Article ID: 317966
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
Symptoms:
- While packet tracing on a VMware ESXi 5.5 host with NetTrace enabled, the host halts with a purple diagnostic screen error.
- You see this or a similar backtrace :
PANIC bora/vmkernel/main/dlmalloc.c:4892 - Usage error in dlmalloc
cpu36:32815)cr0=0x8001003d cr2=0x1c2c44e7588 cr3=0x836fa000 cr4=0x216c
cpu36:32815)@BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4892 - Usage error in dlmalloc
cpu36:32815)Code start: 0x418022800000 VMK uptime: 8:04:06:07.894
cpu36:32815)0x412400bdd530:[0x41802288cf99]PanicvPanicInt@vmkernel#nover+0x575 stack: 0x412400000008
cpu36:32815)0x412400bdd590:[0x41802288d1dd]Panic_NoSave@vmkernel#nover+0x49 stack: 0x4108c349f000
cpu36:32815)0x412400bdd5b0:[0x41802284237f]DLM_free@vmkernel#nover+0x67b stack: 0x0
cpu36:32815)0x412400bdd600:[0x418022858387]Heap_Free@vmkernel#nover+0x107 stack: 0x200
cpu36:32815)0x412400bdd680:[0x41802296bf2e]Pkt_AttrFree@vmkernel#nover+0x56 stack: 0x5000e0e21fb415fc
cpu36:32815)0x412400bdd6a0:[0x418022978d15]Pkt_FreeHandleAndBuf@vmkernel#nover+0x11 stack: 0x42
cpu36:32815)0x412400bdd6e0:[0x4180229691ee]Pkt_DropOrComplete@vmkernel#nover+0x16e stack: 0x4136cf4b0600
cpu36:32815)0x412400bdd760:[0x41802297a60e]Port_IOCompleteList@vmkernel#nover+0xf6 stack: 0x11
cpu36:32815)0x412400bdd800:[0x41802296ba9d]PktListIOCompleteInt@vmkernel#nover+0x171 stack: 0x0
cpu36:32815)0x412400bdd890:[0x418022a23ad7]NetPollWorldletCallback@vmkernel#nover+0x167 stack: 0x0
cpu36:32815)0x412400bdd9f0:[0x4180228eb997]WorldletProcessQueue@vmkernel#nover+0xcf stack: 0x410bb728d8d0
cpu36:32815)0x412400bdda30:[0x4180228ec45c]WorldletBHHandler@vmkernel#nover+0x54 stack: 0x0
cpu36:32815)0x412400bddac0:[0x41802282e9cf]BH_DrainAndDisableInterrupts@vmkernel#nover+0xf3 stack: 0x412400bddd
cpu36:32815)0x412400bddb00:[0x418022864153]IDT_IntrHandler@vmkernel#nover+0x1af stack: 0x412400bddc20
cpu36:32815)0x412400bddb10:[0x4180228f1064]gate_entry@vmkernel#nover+0x64 stack: 0x4018
cpu36:32815)0x412400bddc20:[0x418022ba42ca]Power_HaltPCPU@vmkernel#nover+0x1fe stack: 0x18a800
cpu36:32815)0x412400bddc90:[0x418022a4eb49]CpuSchedIdleLoopInt@vmkernel#nover+0x4bd stack: 0x410900000002
cpu36:32815)0x412400bdddf0:[0x418022a54c20]CpuSchedDispatch@vmkernel#nover+0x1630 stack: 0x478
cpu36:32815)0x412400bdde60:[0x418022a55f55]CpuSchedWait@vmkernel#nover+0x245 stack: 0x1
cpu36:32815)0x412400bddec0:[0x418022a56727]CpuSched_SleepUntilTC@vmkernel#nover+0xfb stack: 0x0
cpu36:32815)0x412400bddfd0:[0x4180229fcab0]NetCoalesceWorldFn@vmkernel#nover+0x298 stack: 0x0
cpu36:32815)0x412400bddff0:[0x418022a53532]CpuSched_StartWorld@vmkernel#nover+0xfa stack: 0x0
Environment
VMware vSphere ESXi 5.5
Cause
This issue can occur if you run the tracenet command in an ESXi Shell (tracenet ip_address), or enable the tracenet option using a vSphere Client, or run the vm-support command during a packet capture operation.
Resolution
This issue affecting VMware ESXi 5.5 is resolved in 5.5 p04 Patch ESXi550-201501401-BG: Updates esx-base (2099266) :
When you configure tracenet using VI Client or run the tracenet command in ESXi Shell (tracenet <ip>), the ESXi host might experience a purple screen with a backtrace similar to the following:
0xnnnnnnnnnnnn VMK uptime: 7:07:26:48.004
[0xnnnnnnnnnnnn]PanicvPanicInt@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Panic_NoSave@vmkernel#nover+0x49 stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]DLM_free@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Heap_Free@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_AttrFree@vmkernel#nover+0xnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_FreeHandleAndBuf@vmkernel#nover+0xnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_DropOrComplete@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_ClearAndRelease@vmkernel#nover+0xnn stack: 0xn
[0xnnnnnnnnnnnn]PktCapWorldCB@vmkernel#nover+0xnnn stack: 0xn
[0xnnnnnnnnnnnn]CpuSched_StartWorld@vmkernel#nover+0xnn stack: 0xn
When you configure tracenet using VI Client or run the tracenet command in ESXi Shell (tracenet <ip>), the ESXi host might experience a purple screen with a backtrace similar to the following:
0xnnnnnnnnnnnn VMK uptime: 7:07:26:48.004
[0xnnnnnnnnnnnn]PanicvPanicInt@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Panic_NoSave@vmkernel#nover+0x49 stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]DLM_free@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Heap_Free@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_AttrFree@vmkernel#nover+0xnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_FreeHandleAndBuf@vmkernel#nover+0xnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_DropOrComplete@vmkernel#nover+0xnnn stack: 0xnnnnnnnnnnnn
[0xnnnnnnnnnnnn]Pkt_ClearAndRelease@vmkernel#nover+0xnn stack: 0xn
[0xnnnnnnnnnnnn]PktCapWorldCB@vmkernel#nover+0xnnn stack: 0xn
[0xnnnnnnnnnnnn]CpuSched_StartWorld@vmkernel#nover+0xnn stack: 0xn
Additional Information
To be alerted when this document is updated, click the Subscribe to Article link in the Actions box
パケットの追跡時に、ESXi 5.5 ホストが停止して紫色の診断画面に次のエラーが表示される: @BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4892 - Usage error in dlmalloc
パケットの追跡時に、ESXi 5.5 ホストが停止して紫色の診断画面に次のエラーが表示される: @BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4892 - Usage error in dlmalloc
Feedback
Yes
No
Powered by
