Merhaba,
Esxi 5.0 install sırasında veya IBM x3650 M2 server üzerinde bulunan Esxi 5.0 boot etmek istediğinizde PSOD ile karşılaşabilirsiniz.
Aynı problemi Esxi 4.1 versiyonun’da da yaşayabilirsiniz.
@BlueScreen: PCPU 0: no heartbeat (but 2/2 IPIs received). Code start: 0x418017200000 VMK uptime: 0:00:01:58.634 Saved backtrace from: pcpu 0 Heartbeat NMI 0x417fd7206d70:[0x418017262e59]Mod_ExportVmkernelSym@vmkernel#nover+0x118 stack: 0x4100012c8000 0x417fd7206e60:[0x418017200add]LegacyBootVMKernel@vmkernel#nover+0xa04 stack: 0x1400000100 0x417fd7206fe0:[0x4180172019e2]BootVMKernel@vmkernel#nover+0xa1 stack: 0x490fa8 base fs=0x0 gs=0x418041800000 Kgs=0x0 Heartbeat: 618: PCPU 0 didn't have a heartbeat for 21 seconds. *may* be locked up NMI: 1943: NMI IPI received. Was eip(base):ebp:cs [0x62e30(0x418017200000):0x417fd7206d70:0x4010](Src 0x1, CPU0) Heartbeat: 618: PCPU 0 didn't have a heartbeat for 7 seconds. *may* be locked up CacheSched: 943: The measured L2 cache miss cost 1686 is not within the expected range, using 40 instead Heartbeat: 618: PCPU 0 didn't have a heartbeat for 21 seconds. *may* be locked up Backtrace for current CPU #6, worldID=2054, ebp=0x412200187a68 0x412200187a68:[0x41801726ce78]Panic_WithBacktrace@vmkernel#nover+0xa3 stack: 0x412200187a98, 0x210 0x412200187ad8:[0x4180174d9bb7]Heartbeat_DetectCPULockups@vmkernel#nover+0x2be stack: 0x0, 0x4, 0x4 0x412200187b78:[0x418017296ba7]Timer_BHHandler@vmkernel#nover+0x20a stack: 0x220125000000df, 0xdf, 0x412200187bb8:[0x41801721878d]BH_Check@vmkernel#nover+0x80 stack: 0x412200187d88, 0x412200187cc0, 0x412200187bf8:[0x41801724203d]IDT_HandleInterrupt@vmkernel#nover+0x13c stack: 0x418041800140, 0x0, 0x412200187c18:[0x41801724289d]IDT_IntrHandler@vmkernel#nover+0xa4 stack: 0x412200187d28, 0x4180175 0x412200187c28:[0x4180172f2047]gate_entry@vmkernel#nover+0x46 stack: 0x4018, 0x4018, 0x0, 0x0, 0x0 0x412200187d28:[0x4180175001e1]Power_HaltPCPU@vmkernel#nover+0x274 stack: 0x3398b1c16b, 0x0, 0x4122 0x412200187e58:[0x4180173f05fa]CpuSchedIdleLoopInt@vmkernel#nover+0xb3d stack: 0x412200187e98, 0x41 0x412200187e68:[0x4180173f75f6]CpuSched_IdleLoop@vmkernel#nover+0x15 stack: 0x1, 0x6, 0x0, 0x1, 0x4 0x412200187e98:[0x4180172460ea]Init_SlaveIdle@vmkernel#nover+0x13d stack: 0x0, 0x200000000, 0x0, 0x 0x412200187fe8:[0x4180175063d9]SMPSlaveIdle@vmkernel#nover+0x310 stack: 0x0, 0x0, 0x0, 0x0, 0x0 WARNING: SP: CheckSpinCount: "ModLock" (held by 0): Spin count exceeded 1 time(s) - possible deadlock. WARNING: SP: CheckSpinCount: "ModLock" (held by 0): Spin count exceeded 2 time(s) - possible deadlock. WARNING: SP: CheckSpinCount: "ModLock" (held by 0): Spin count exceeded 3 time(s) - possible deadlock. WARNING: SP: CheckSpinCount: "ModLock" (held by 0): Spin count exceeded 4 time(s) - possible deadlock. WARNING: SP: CheckSpinCount: Forcibly granting lock ModLock. vmkernel 0x0 .data 0x0 .bss 0x0 No place on disk to dump data.
Bu PSOD‘u almanızın sebebi, IBM x3650 M2 server’in bios’unda Memory sekmesi altında Non-Numa seçeneği seçili olduğu için bu PSOD ile karşılaşıyorsunuz.
Bu hatanın çözümü için, IBM sunucunun bios’una girip “System Settings -> Memory-> Socket Interleave -> daha sonra burada karşımıza çıkan seçeneği NUMA olarak değiştirmemiz gerekiyor. Bu şekilde bu PSOD’ dan kurtulabilirsiniz.
Umarım faydalı olmuştur.
İyi çalışmalar.
