Highlighted
Contributor
Contributor

ESXi 6.7 Keep Getting PANIC bora/vmkernel/main/dlmalloc.c: 4924 - Usage error in dlmalloc

Jump to solution

Hi,

     After upgrading to ESXi 6.7 form 6.5, I keep getting this error from my host with a purple screen.

     PANIC bora/vmkernel/main/dlmalloc.c: 4924 - Usage error in dlmalloc

     I reinstalled a few times and still getting the same problem.  Did anyone have the same happening to your hosts?

Eddy

1 Solution

Accepted Solutions
Highlighted
VMware Employee
VMware Employee

This is a known issue with ESXi 6.7.

Symptom: An ESXi host might fail with the error PANIC bora/vmkernel/main/dlmalloc.c:4924 - Usage error in dlmalloc

Description:

When you replicate virtual machines using the VMware Site Replication Manager hbr_filter with vSphere Replication, the ESXi host might fail with purple screen immediately or within 24 hours and reports the error: PANIC bora/vmkernel/main/dlmalloc.c:4924 - Usage error in dlmalloc.

This issue is resolved in vSphere 6.7 EP5 - ESXi670-201811001

We published the following KB https://kb.vmware.com/s/article/55650​.

James Walker VMware Support Moderator

View solution in original post

0 Kudos
30 Replies
Highlighted
Contributor
Contributor

Hi Eddy,

I would recommend opening a ticket with VMware support and share the host log bundle along with the PSOD screenshot.

If you have a dump file available in the host log bundle what you can do is try to look at the vmkernel.log file, vmkwarning.log, vobd.log & hostd.log file to see what happened just before the host has crashed, that is what VMware is going to check prior to analyzing the dump file.

I hope it helps.

Regards
Ravi

0 Kudos
Highlighted
Contributor
Contributor

Hi Ravi,

Thanks for your suggestion. I will do that.

Eddy

8^)

0 Kudos
Highlighted
Hot Shot
Hot Shot

This seems to be a bug in esxi 6.7.

ESXi 6.7 kernel panic during Heap_Free in dlmalloc

0 Kudos
Highlighted
Contributor
Contributor

Hello; I tried to send you a private message but it seemed to fail. VMware support is tracking this issue for us also; however since the last time it occured the Sr. Solution Engineer who had been working the issue is now on PTO until July 3. Have you received any additional information as to a fix or workaround to avoid? We were told the issue was likely something related to VDR (vsphere replication).

Thanks,

John

0 Kudos
Highlighted
Contributor
Contributor

Hello,

I received this same issue twice today on 2 different hosts.  The last response on this thread was back over a month ago.  Is there any solution to this problem? 

0 Kudos
Highlighted
Commander
Commander

Asher - Can you share the complete screenshot of the PSOD screen?

Cheers,

Supreet

0 Kudos
Highlighted
Contributor
Contributor

20180726_112717.jpg

Here is the picture of the purple screen. 

0 Kudos
Highlighted
User Moderator
User Moderator

Hi, check this link: i can't confirm  that it will solve.

Other alternative is update to last buld (ESXi 6.7 EP 02)

VMware Knowledge Base

Diego Oliveira LinkedIn: http://www.linkedin.com/in/dcodiego
0 Kudos
Highlighted
User Moderator
User Moderator

Another thing, what is the server model?

Diego Oliveira LinkedIn: http://www.linkedin.com/in/dcodiego
0 Kudos
Highlighted
Commander
Commander

These heap related PSOD's are tricky. This one does not seem to be reported yet. You might want to raise a case with VMware if you want to get to the bottom of this.

Cheers,

Supreet

0 Kudos
Highlighted
Contributor
Contributor

same here, rolled back to 6.5 u1. Not fixed yet in ESXi 6.7 EP 02a

0 Kudos
Highlighted
User Moderator
User Moderator

Did you upgrade the server firmware?

Diego Oliveira LinkedIn: http://www.linkedin.com/in/dcodiego
0 Kudos
Highlighted
Enthusiast
Enthusiast

If I am not wrong, this seems a BUG. contact VMware support to file a case with their engineering

Ashish Singh VCP-6.5, VCP-NV 6, VCIX-6,VCIX-6.5, vCAP-DCV, vCAP-DCD
0 Kudos
Highlighted
Contributor
Contributor

No,we use bl460c gen8 on on 2015 fw, and we have VR.

0 Kudos
Highlighted
Contributor
Contributor

I have Dell M630 blade servers running current firmware and received this PSOD on the first upgraded machine two hours after installing ESXi 6.7.0 Build 8941472 (Dell specific ISO - VMware-VMvisor-Installer-6.7.0-8941472.x86_64-DellEMC_Customized-A02.iso).  I stopped the upgrade of the rest of the ESXi cluster nodes.  They run fine under 6.5.0 Build 7388607.  The host in question was replicating a VM to our disaster recovery site during the crash.  The VM in question was stuck and did not free up until the host was rebooted.

0 Kudos
Highlighted
Commander
Commander

Based on the functions reported on the PSOD screen, looks like the issue is in the vSphere Replication stack. You may want to pause the replication in case it is happening too frequently. In the meantime, engage VMware support to get further assistance on this.

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

Cheers,

Supreet

Highlighted
Contributor
Contributor

"Engineering is currently investigating PSODs with the exact same trace that is occuring due to a HBR module (OEM Provided - Qlogic, in this case)."

I've updated my NIC drivers as suggested by support and have continued testing a couple of my hosts.  These hosts are now running ESXi 6.7.0 build 9214924.

0 Kudos
Highlighted
Contributor
Contributor

what driver version do you have? we had same problem on 9214924. drv version 1.713.30.v60.6

0 Kudos
Highlighted
Contributor
Contributor

In our case the upgrade left an older QLogic driver on our hosts - qfle3 version 1.0.50.11.  I installed VMware ESXi 6.7 Driver CD for QLogic Network/iSCSI/FCoE Driver Set from the Drivers and Tools tab which contains qfle3 1.0.69.0.  This is the second day of testing but so far no PSODs.  Check your NICs against the VMware compatibility list:

SSH into your ESXi host

esxcli network nic list                          #List your NICs

esxcli network nic get -n vmnic0     #Get your software and firmware versions for each NIC

0 Kudos