VMware Cloud Community
miken1
Contributor
Contributor

ESXI5.5 Corruption in dlmalloc PSOD

I'm very new to to ESXI.

Hardware, Supermicro X10SL7-F

Extracts from PSOD

2014-12-07T22:29:44.590Z cpu4:1415871)VMware ESXi 5.5.0 [Releasebuild-1623387 x86_64]

PANIC bora/vmkernel/main/dlmalloc.c:4704 - Corruption in dlmalloc

2014-12-07T22:29:44.591Z cpu4:1415871)cr0=0x80010031 cr2=0x4005b6b0740 cr3=0x14efc1000 cr4=0x42768

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:0 world:32783 name:"coalesceWorld-0" (S)

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:1 world:532002 name:"vmm0:Main_Windows_2012_R2" (V)

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:2 world:32784 name:"netCoalesce2World" (S)

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:3 world:532007 name:"vmm2:Main_Windows_2012_R2" (V)

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:4 world:1415871 name:"vmx-vcpu-4:Ubuntu" (U)

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:5 world:532011 name:"vmm6:Main_Windows_2012_R2" (V)

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:6 world:532009 name:"vmm4:Main_Windows_2012_R2" (V)

2014-12-07T22:29:44.591Z cpu4:1415871)pcpu:7 world:32851 name:"itRebalance" (S)

2014-12-07T22:29:44.591Z cpu4:1415871)@BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4704 - Corruption in dlmalloc

2014-12-07T22:29:44.591Z cpu4:1415871)Code start: 0x418026200000 VMK uptime: 14:05:03:05.230

2014-12-07T22:29:44.592Z cpu4:1415871)0x4123eafdd6e8:[0x41802628cf99]PanicvPanicInt@vmkernel#nover+0x575 stack: 0x412300000008

2014-12-07T22:29:44.592Z cpu4:1415871)0x4123eafdd748:[0x41802628d1dd]Panic_NoSave@vmkernel#nover+0x49 stack: 0x4180268e3eb8

2014-12-07T22:29:44.592Z cpu4:1415871)0x4123eafdd798:[0x418026243ccb]DLM_malloc@vmkernel#nover+0x15ab stack: 0x4123eafdd808

2014-12-07T22:29:44.593Z cpu4:1415871)0x4123eafdd828:[0x418026259e03]Heap_AlignWithTimeoutAndRA@vmkernel#nover+0x147 stack: 0x40

2014-12-07T22:29:44.593Z cpu4:1415871)0x4123eafdd858:[0x4180269fc35a]usb_get_device_descriptor@com.vmware.usb#9.2.2.0+0x62 stack: 0x0

2014-12-07T22:29:44.593Z cpu4:1415871)0x4123eafdd928:[0x4180269f6633]hub_port_init@com.vmware.usb#9.2.2.0+0x3cb stack: 0x412300000020

2014-12-07T22:29:44.594Z cpu4:1415871)0x4123eafdd9e8:[0x4180269f6c12]usb_reset_and_verify_device@com.vmware.usb#9.2.2.0+0xe6 stack: 0x412

2014-12-07T22:29:44.594Z cpu4:1415871)0x4123eafdda38:[0x4180269f717b]usb_reset_device@com.vmware.usb#9.2.2.0+0xbf stack: 0x410931645a00

2014-12-07T22:29:44.594Z cpu4:1415871)0x4123eafddbc8:[0x4180269eced9]usbdev_ioctl@com.vmware.usb#9.2.2.0+0x2a5 stack: 0x4180264a04e0

2014-12-07T22:29:44.595Z cpu4:1415871)0x4123eafddc38:[0x4180268b9575]LinuxCharIoctl@com.vmware.driverAPI#9.2+0x101 stack: 0x410006968000

2014-12-07T22:29:44.595Z cpu4:1415871)0x4123eafddca8:[0x4180262b37d2]VMKAPICharDevDevfsWrapIoctl@vmkernel#nover+0x8e stack: 0x41804000000

2014-12-07T22:29:44.595Z cpu4:1415871)0x4123eafddd88:[0x4180264ef9a0]DevFSIoctl@vmkernel#nover+0x688 stack: 0x4123eafdde01

2014-12-07T22:29:44.596Z cpu4:1415871)0x4123eafddde8:[0x4180264ca75c]FSS_IoctlByFH@vmkernel#nover+0xd0 stack: 0x5514

2014-12-07T22:29:44.596Z cpu4:1415871)0x4123eafdde08:[0x41802679da1b]UserFile_PassthroughIoctl@<None>#<None>+0x3f stack: 0x4123eafdde68

2014-12-07T22:29:44.596Z cpu4:1415871)0x4123eafdde78:[0x4180267ea7d8]UserVmfs_Ioctl@<None>#<None>+0x28 stack: 0x412e84b111d8

2014-12-07T22:29:44.597Z cpu4:1415871)0x4123eafddeb8:[0x4180267a3f4e]LinuxFileDesc_Ioctl@<None>#<None>+0x5e stack: 0x4123eafddfc0

2014-12-07T22:29:44.597Z cpu4:1415871)0x4123eafddf08:[0x41802677df7c]User_LinuxSyscallHandler@<None>#<None>+0x2f0 stack: 0x4123eafddf28

2014-12-07T22:29:44.597Z cpu4:1415871)0x4123eafddf18:[0x4180262aa67d]User_LinuxSyscallHandler@vmkernel#nover+0x1d stack: 0x3ffdd46bc50

2014-12-07T22:29:44.597Z cpu4:1415871)0x4123eafddf28:[0x4180262f1064]gate_entry@vmkernel#nover+0x64 stack: 0x10b

Anyone got any idea? Apologies if I haven't included enough information.

Is it worth updating to u2? I hadn't because I got display corruption booting from the iso to try aclean install and was hesitant to upgrade because of issues described AST2000 (Aspeed Graphics) Driver/Problem on ESXi 5.5uX

0 Kudos
0 Replies