【vSphere故障案例】案例十一：粉屏死机PSOD-3
【vSphere故障案例】
案例十一：紫屏死机PSOD-3（或者粉屏死机）
这个图片是我在其它地方看到的，收集下哈~
解决方法也是VMware论坛社区提供的。
PF exception 14 in world 4460:helper23-20
Received this PSoD on UCS-B, 96GB RAM, Boot from SAN. PSoD is random. Blade boots ok but PSoDs after some time. No memory errors in any event logs. Do receive some strange PCIe errors。如下图所示：
粉屏死机和紫屏死机一样，都是由于硬件问题引起的。
VMware提供的参考解决方法：http://kb.vmware.com/kb/1020181
Overview
Operating systems manage the physical memory on a system by employing several methods:
•Virtual memory or paging is designed to abstract the physical memory into virtual memory. This abstraction allows the operating system to allocate memory specific to programs and allows for other forms of memory management, including Memory Swapping, Shared Memory, and Memory Protection.
•Memory Swapping occurs when operating systems optimize memory by moving data that is not being used to slower mediums and vice versa.
•Shared Memory is a method commonly used if multiple programs need to communicate with each other. Shared memory allows multiple programs to access the same page of memory.
•Memory Protection prevents a malicious or malfunctioning program from accessing memory pages from other programs.
When a critical application has difficulty accessing memory, it generally manifests with an error involving one of these memory management operations.
Exception 14: Page Fault
A page fault (Exception 14) occurs when the page being requested has not been successfully loaded into memory. There are both healthy and unhealthy page faults:
•A healthy page fault results in the page being loaded from swapped memory to physical memory. The program is then allowed to proceed after the data has been properly loaded into physical memory.
•An unhealthy page fault occurs when the page is not loaded in memory, and the operating system is unable to load the page from swapped to physical memory.
This is a sample of a Page Fault generated by ESX:
[VMware ESX Server [Releasebuild-123630]Exception type 14 in world 1024:console @ 0x67f0ae
frame=0x1402824 ip=0x67f0ae cr2=0x405f6000 cr3=0x13401000 cr4=0x6f0
es=0x4028 ds=0x40404028 fs=0xffff0000 gs=0x0
eax=0x409f6000 ebx=0x1000 ecx=0x400 edx=0x409f6000
ebp=0x14028b4 esi=0x407c8000 edi=0x409f6000 err=11 eflags=0x10206
*0:1024/console 1:1092/mks:ubunt 2:1089/vmware-vm 3:1027/idle3
4:1028/idle4 5:1029/idle5 6:1030/idle6 7:1091/vmware-vm
8:1032/idle8 9:1033/idle9 10:1034/idle10 11:1093/vcpu-0:ub
12:1036/idle12 13:1037/idle13 14:1038/idle14 15:1039/idle15
@BlueScreen: Exception type 14 in world 1024:console @ 0x67f0ae
0x14028b4:[0x67f0ae]genericCopy+0x155 stack: 0xc0bbc60, 0x40081800, 0x0
0x14028dc:[0x67f3d6]vmk_SgCopy+0x41 stack: 0xc0bbc60, 0x40081800, 0x0
0x140292c:[0x7cef13]SCSICompleteFragment+0x1ae stack: 0xc005d00, 0x0, 0xc3100
0x14029c4:[0x7d081c]SCSICompletePathCommand+0x453 stack: 0xc005d00, 0x125, 0x148a4f8
0x1402a60:[0x7cafff]SCSICompleteAdapterCommand+0x3da stack: 0xc005d00, 0x2, 0x1402de0
0x1402ac0:[0x88343f]vmk_scsi_dump_active+0x20e stack: 0x0, 0x10a, 0x6a525f0
0x1402b30:[0x61811e]BHCallHandlersInt+0xf5 stack: 0x2ad0, 0x0, 0x1402b88
0x1402b88:[0x618614]BH_Check+0x2bb stack: 0x1, 0x1402bac, 0x1752d49
0x1402bac:[0x61fb8e]IDT_HandleInterrupt+0x85 stack: 0x1402bf8, 0x0, 0xb638000
0x1402bc0:[0x61fcb5]IDT_IntrHandler+0x4c stack: 0x1402bf8, 0x4028, 0x1454028
0x1402c70:[0x692c6c]CommonIntr+0xb stack: 0x1489500, 0x0, 0x1402de0
0x1402e1c:[0x7615e4]CpuSchedDispatch+0x487 stack: 0x2390a60, 0x1489500, 0x0
0x1402e88:[0x763eaa]CpuSchedDoWaitDirectedYield+0x351 stack: 0x0, 0x1f55e60, 0x0
0x1402ea4:[0x763fda]CpuSched_WaitIRQ+0x31 stack: 0xfedcba90, 0x6, 0x1f55e60
0x1402ec4:[0x69197f]VMNIXVMKSyscall_Idle+0xe2 stack: 0x1402f6c, 0x6915cf, 0x0
0x1402ecc:[0x68669c]VMNIXVMKSyscallUnpackIdle+0x7 stack: 0x0, 0x0, 0x0
0x1402f6c:[0x6915cf]HostSyscall+0xf6 stack: 0x1402fbc, 0xc03d9f98, 0x1c
0x1402fe8:[0x6909e3]HostVMKEntry+0xce stack: 0x0, 0x0, 0x0
VMK uptime: 0:01:58:34.004 TSC: 15137542595232
Starting coredump to disk Starting coredump to disk Dumping using slot 1 of 1... using slot 1 of 1... log