Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 176561

ESXi 5.5.0 on HP DL360 G6 PSOD on warm boot

$
0
0

Good morning,

 

I just updated one of my ESXi servers from 5.0 to 5.5.   Everything seemed to go OK during the update, until the ESXi server rebooted, when it came up with a PSOD.

 

If I cold boot the server from a power-off state, it boots fine with no errors and comes up and reports "compliant" to vCenter.

 

If I reboot it via vCenter, it comes up with the PSOD again.

 

The details of the PSOD are below.    Has anyone else seen anything similar, or know what the issue is?

I got the PSOD by taking a cameraphone pic of the PSOD screen, running it through OCR, and fixing the errors, so if something doesn't make sense, there may still be some typos in it.   I've attached the original PSOD screenshot for reference.

 

 

VMware ESXi 5.5.0 [Releasebuild-1331820 x86_64]

PANIC bora/vmkerne1/main/dlmalloc.c:4892 - Usage error in dlmalloc

cr0=0x8001003d cr2=0x164e8080 cr3=0x800f0000 cr4=0x216c

*PCPU6:32820/helper11-0

PCPU  0: SHSSSSSHSHS

Code start: 0x41803ba00000 VMK uptime: 0:15:35:38.411

0x412380d1dbf0:[0x41803ba8ccd9]PanicvPanicInt@vmkernel#nover+0x575 stack: 0x412300000008

0x412380d1dc50:[0x41803ba8cfld]Panic_NoSave@vmkernel#nover+0x49 stack: 0x4109509b4000

0x412380d1dc70:[0x41803ba422eflDLM_free@vmkerne1#nover+0x67b stack: 0x20

Ox412380d1dcc0:[0x41803ba58017]Heap_Free@vmkernel#nover+Ox107 stack: 0x410954b060b0

0x412380d1dce0:[0x41803c1a7bldlooo_free_buf_single@com.broadcom.cnic#9.2.2.0+0x3d stack: 0x410954b0

0x412380d1dd20:[0x41803c1a93e5]cnic_free_resc@com.broadcom.cnic*9.2.2.0+0x16d stack: Ox412380d1dda0

Ox412380d1dd50:[0x41803cla674a]cnic_stop_hw@com.broadcom.cnic#9.2.2.0+Ox102 stack: Ox0

Ox412380d1ddb0:[0x41803c1ad8a2]cnic_ctl@com.broadcom.cnic#9.2.2.0+0x1a6 stack: Ox1

0x412380d1de50:[0x41803c193b0c]bnx2_cnic_stop@com.broadcom.bnx2#9.2.2.0+Ox7c stack: Ox1

0x412380d1de90:[0x41803c194784]bnx2_close@com.broadcom.bnx2#9.2.2.0+0x20 stack: 0x412300001018

Ox412380d1ded0:[0x41803c0b06b4]dev_close@com.vmware.driverAPI#9.2*Oxa5 stack: 13x41088ec56280

Ox412380d1def0:[0x41003c8b06b4]CloseNetDev@com.vmware.driverAPI#9.2+0x7c stack: 0x4108a0e28840

0x412380dldf30:[0x41803bc3a9231Up1inkAsyncProcessCallsHelperCB@vmkernel#nover+0x223 stack: Ox0

Ox412380dldfd0:[0x41803ba60f8a]helpFunc@vmkernel#nover+0x6b6 stack: Ox0

0x412380d1df10:[0x41803bc53242]CpuSched_StartWorld@vmkernel#nover+0xfa stack: Ox0

base fs=0x0 gs=0x418041800000 Kgs=0x0

Coredump to disk. Slot 1 of 1.

Finalized dump header (12/12) DiskDump: Successful.

Debugger waiting(world 32820) -- no port for remote debugger. "Escape" for local debugger.


Viewing all articles
Browse latest Browse all 176561

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>