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

30 Replies
Highlighted
Contributor
Contributor

         Driver: qfle3

         Firmware Version: FW: 7.13.109.0 BC: 7.10.39

         Version: 1.0.69.0

0 Kudos
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
Highlighted
Contributor
Contributor

Hmm this still isnt fixed....the issue i have is looking at the date this was first reported, and im on the phone to VMware now with no fix still....that is a long time to have a critical issue like this!

Your VMware not some back street company knocking our a hypervisor...you make us pay through the nose for the product but at the moment its not fit for purpose!

0 Kudos
Highlighted
Enthusiast
Enthusiast
0 Kudos
Highlighted
Contributor
Contributor

Hello guys,

It seems that EP5 doesn't help me. I'm with ESXi 6.7 U2, build 13006603 and I'm still getting the same PSOD.

Am I missing something?

Thank you in advance!

0 Kudos
Highlighted
Enthusiast
Enthusiast

I am having the same issue with 6.7 U2

0 Kudos
Highlighted
Contributor
Contributor

pastedImage_0.png

Since i installed 6.7u2 this bug has resurfaced. Anyone know anything about this?

0 Kudos
Highlighted
Contributor
Contributor

Hi TomasAZ01,

in my case the issue was caused by the qfle3 driver and I see a very similar situation in your PSOD.

check for similar errors in the logs -

ql_fcoe:vmhba64:PortLoginCallback:1218:Info: PortLoginCallback: Sess 0x430e95197000 000000 PLOGI timeout or cancel

*The PLOGI timeout indicates that the HBA does not get a reply from the storage after sending a PLOGI

for me - the storage was OK and next step was to check the Driver / FW

- here again - everything was fine as the HCL

and our vendor told me for some known issues caused by the qfle3 driver and as workaround was to revert to bnx2x driver.

so far everything is stable.

hope that will help you!

0 Kudos
Highlighted
Contributor
Contributor

Thank you for your answer, i´ll have a look and see what i can find. Smiley Happy

0 Kudos
Highlighted
Contributor
Contributor

I see nothing about:

ql_fcoe:vmhba64:PortLoginCallback:1218:Info: PortLoginCallback: Sess 0x430e95197000 000000 PLOGI timeout or cancel

*The PLOGI timeout indicates that the HBA does not get a reply from the storage after sending a PLOGI

But i see alot of obscure messages about qfle3 driver in the kernel logs.
How did you exchange the driver?

0 Kudos
Highlighted
Contributor
Contributor

Hello TomasAZ01,

what I have done -

check your VIBs - all 3 drivers should be qfle3, qfle3f and qfle3i

then disable them -

esxcli system module set --enabled=false --module=native_driver_name

- check in the HCL for your card and chose the latest bnx2x driver.

VIB or offline bundle (the ZIP file that you will download)

----------------

1. Copy the VIB or offline bundle to the ESX server.  Technically, you can

           place the file anywhere that is accessible to the ESX console shell,

           but for these instructions, we'll assume the location is in '/tmp'.

2. Issue the following command (full path to the file must be specified):

              esxcli software vib install -v {VIBFILE}

           or

              esxcli software vib install -d {OFFLINE_BUNDLE}

and last - match the FW as the new driver / HCL.

BR

0 Kudos