PSOD: NMI IPI: Panic requested by another PCPU. RIPOFF(base):RBP:CS [0x10484d(0x42001e000000):0x42005200068a:0xf48] (Src 0x4, CPU72)
search cancel

PSOD: NMI IPI: Panic requested by another PCPU. RIPOFF(base):RBP:CS [0x10484d(0x42001e000000):0x42005200068a:0xf48] (Src 0x4, CPU72)

book

Article ID: 378067

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • ESXi host fails with PSOD after a DIMM (Memory Module) was replaced or has a fault:

  • ESXi host's /var/run/log/vmkernel.log file has log entries similar to the following:

       YYYY-MM-DDTHH:MM:SS.768Z cpu47:2132341)MCA: 209: CE Intr G0 B7 S9c00004001010090 A9797304cc0 M200005c2a0001086 P9797304cc0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.503Z cpu67:2131023)MCA: 209: CE Intr G0 B7 S9c00004001010090 A9653364cc0 M200000c007c01086 P9653364cc0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.735Z cpu60:2097212)MCA: 209: CE Intr G0 B7 S9c00004001010090 A9797304cc0 M200005c2a0201086 P9797304cc0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.925Z cpu47:2133204)MCA: 209: CE Intr G0 B7 S9c00004001010090 A97ba764cc0 M200001c083c01086 P97ba764cc0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.310Z cpu60:2133698)MCA: 209: CE Intr G0 B7 S9c00004001010090 A9653364cc0 M200001c082e01086 P9653364cc0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.770Z cpu67:2130420)MCA: 209: CE Intr G0 B7 S9c00004001010090 A9653364cc0 M200001c081601086 P9653364cc0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.452Z cpu58:2132215)MCA: 209: CE Intr G0 B7 S9c00004001010090 A97ae764cc0 M200001c080a01086 P97ae764cc0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.634Z cpu59:2202367)MCA: 209: CE Intr G0 B7 S9c00004001010090 Ab73e5ae8c0 M200000c020001086 Pb73e5ae8c0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.688Z cpu66:2098167)MCA: 209: CE Intr G0 B7 S9c00004001010090 Ab73e5ae8c0 M200000c020401086 Pb73e5ae8c0/40 Memory Controller Read Error on Channel 0.
       YYYY-MM-DDTHH:MM:SS.374Z cpu51:2131494)MCA: 209: CE Intr G0 B7 S9c00004001010090 A9797304cc0 M200000c020001086 P9797304cc0/40 Memory Controller Read Error on Channel 0.
  • The ESXi host's vmkernel-zdump analysis shows the below log entries:

    PSOD Message: @BlueScreen: NMI IPI: Panic requested by another PCPU. RIPOFF(base):RBP:CS [0x10484d(0x42001e000000):0x42005200068a:0xf48] (Src 0x4, CPU72)
    Backtrace for Current CPU - 72:
        0x452900482cf0:[0x42001e0fee8b]PanicvPanicInt@vmkernel#nover+0x327 stack: 0x452900482dc8, 0x4302f780a2a8, 0x42001e0fee8b, 0x42001e5f1300, 0x452900482cf0
        0x452900482dc0:[0x42001e0ff43d]Panic_WithBacktrace@vmkernel#nover+0x56 stack: 0x452900482e30, 0x452900482de0, 0x452900482e40, 0x452900482df0, 0x10484d
        0x452900482e30:[0x42001e0fbb90]NMI_Interrupt@vmkernel#nover+0x561 stack: 0x0, 0x0, 0x0, 0x0, 0x0
        0x452900482f00:[0x42001e153392]IDTNMIWork@vmkernel#nover+0x7f stack: 0x420052000000, 0x42001e1546dd, 0x0, 0x452900482fd0, 0x0
        0x452900482f20:[0x42001e1546dc]Int2_NMI@vmkernel#nover+0x19 stack: 0x0, 0x42001e14e068, 0x10b, 0x0, 0x0
        0x452900482f40:[0x42001e14e067]gate_entry@vmkernel#nover+0x68 stack: 0x0, 0x1, 0x2d, 0x1b6ba00000000, 0x2995540
        0x453986e1b730:[0x42001e10484d]MCSLockSpin@vmkernel#nover+0x41 stack: 0x41ffde4501e8, 0x42005200068a, 0x49, 0x42001e104eab, 0x453986e1bc14
        0x453986e1b760:[0x42001e104eaa]MCSLockWait@vmkernel#nover+0x153 stack: 0x453986e1bc14, 0x42001e1053fa, 0x453986e1b7bc, 0x42001e3d35b1, 0x453986e1bc14
        0x453986e1b780:[0x42001e1053f9]MCSLockWork@vmkernel#nover+0x2a stack: 0x453986e1bc14, 0x453986e1bc14, 0x43241760f040, 0x42001e3ce906, 0x5
        0x453986e1b790:[0x42001e3d35b0]MemSchedPolicy_FillCommonStats@vmkernel#nover+0x11 stack: 0x43241760f040, 0x42001e3ce906, 0x5, 0x52000000, 0xfffffffc00000000
     Backtrace for Saved/Locked CPU - 72:
        0x453986e1b730:[0x42001e10484c]MCSLockSpin@vmkernel#nover+0x41 stack: 0x41ffde4501e8
        0x453986e1b760:[0x42001e104eaa]MCSLockWait@vmkernel#nover+0x153 stack: 0x453986e1bc14
        0x453986e1b780:[0x42001e1053f9]MCSLockWork@vmkernel#nover+0x2a stack: 0x453986e1bc14
        0x453986e1b790:[0x42001e3d35b0]MemSchedPolicy_FillCommonStats@vmkernel#nover+0x11 stack: 0x43241760f040
        0x453986e1b7b0:[0x42001e3ce905]MemSchedMemClientFillCommonStats@vmkernel#nover+0x25e stack: 0xfffffffc00000000
        0x453986e1b800:[0x42001e3d0d6d]MemSched_MemClientVsiGet@vmkernel#nover+0x1f2 stack: 0x43010e86b480
        0x453986e1b930:[0x42001e3ec6c0]SchedGetGuestLibVMInfo@vmkernel#nover+0xe9 stack: 0xffffffff
        0x453986e1be30:[0x42001e3ed27f]Sched_GetGuestLibInfo@vmkernel#nover+0x14 stack: 0x432488426000
        0x453986e1beb0:[0x42001e53af33]UW64VMKPrivateSyscallUnpackGetGuestLibInfo@vmkernel#nover+0x38 stack: 0x453986e1bf40
        0x453986e1bee0:[0x42001e4b2806]User_UWVMK64SyscallHandler@vmkernel#nover+0x183 stack: 0x0

Cause

The memory module (DIMM) is either faulty or corrupt.

Resolution

Check the seating of the RAM in the affected host per vendor instructions. Contact the vendor for hardware support if this is not the issue.

Powered by Wolken Software