Dear,
A PSOD appeared on a server with VMWare ESXi 5.5.0 [Releasebuild-2143827 x86_64] (27/12/2015 at 3.00 AM).
The informationon on the PSOD screen :
VMWare ESXi 5.5.0 [Releasebuild-2143827 x86_64]
LNT1/NMI (motherboard nonmaskable interrupt), undiagnosed. This may be a hardware problem; please contact you vendor
PCPU:34307/rhttpproxy-work
.. start : 0x418028800000 VMK uptime : 73:0206:08.951
0x4123980dd900:[0x41802888d149]PanicvPanicInt@vmkernel#nover+0x575 stack: 0x412300000008
0x4123980dd960:[0x41802888d38d]Panic_Nosave@vmkernel#nover+0x49 stack: 0x4123980dda00
0x4123980dd970:[0x41802888998]NMICheckL int1Bottom@@vmkernel#nover+0x50 stack: 0x4123980dd9b0
0x4123980dda00:[0x418028829ff]BH_DrainAndDisableInterrupts@vmkernel#nover+0xf3 stack: 0x4123980dda
0x4123980dda40:[0x418028864277]IDT_IntrHandler@vmkernel#nover+0xIaf stack: 0x4123980ddb60
0x4123980dda50:[0x4180288f1064]gate_entry@vmkernel#nover+0x0x64 stack: 0x0
0x4123980ddb60:[0x4180288ba683a]Power_Halt@vmkernel#nover+0x0xIfe stack: 0x0
0x4123980ddbd0:[0x4180288a50cb1]CpuSchedDispatch@vmkernel#nover+0x245 stack: 0x0410800000001
0x4123980dde40:[...]CpuSchedWait@vmkernel#nover+0x245 stack: 0x0410800000001
0x....:[...]worldWaitInt@vmkernel#nover+0x... stack: 0x...
0x....:[...]Userthread_Sleep@vmkernel#nover+0x... stack: 0x...
0x....:[...]LinuxThread_Nanosleep@vmkernel#nover+0x... stack: 0x...
0x....:[...]User_LinuxSyscallHandler@<none>#<none>+0x... stack: 0x...
0x....:[...]User_LinuxSyscallHandler@vmkernel#nover+0x... stack: 0x...
0x....:[...]gate_entry@vmkernel#nover+0x... stack: 0x...
Coredump to disk. slot 1 of 1
Finalized dump header (12/12) DiskDump : Successful.
No file configured to dump data.
Debugger waiting(world 34307) -- no port for remote debugger. "Escape" for local debugger.
I took the vm-support.tgz file yesterday, and the Vmkernel.log is starting 2015-12-28T13:47 then I cannot see the previous instrustion just after the PSOD.
I made this verification (after the PSOD) :
- Log => like I said they cycling.
- Hardware => all are "normal" in vpshere and in command line.
- DataStore => there is enough space
I understood that the issue seems due to a hardware component, but I cannot find it.
I hope some body will help me.
Best regards
