[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] PTE Write access is not set
Hello list, Using the 3.1.5 kernel and 4.1.3-rc1-pre xen (Latest ChangeSet: Tue Dec 06 10:53:12 2011 +0000 23199:d9f8316a8291), these crashes occur after about a day or so of running a HVM: =================8<================= (XEN) realmode.c:115:d9 Failed to emulate insn. (XEN) realmode.c:165:d9 Real-mode emulation failed @ e40a:00005f6c: d9 33 01 fc 30 34 (XEN) domain_crash called from realmode.c:166 (XEN) Domain 9 (vcpu#0) crashed on cpu#6: (XEN) ----[ Xen-4.1.3-rc1-pre x86_64 debug=n Not tainted ]---- (XEN) CPU: 6 (XEN) RIP: e40a:[<0000000000005f6c>] (XEN) RFLAGS: 0000000000010002 CONTEXT: hvm guest (XEN) rax: 000000000000e7e5 rbx: 0000000000000000 rcx: 00000000000d0000 (XEN) rdx: 00000000000001f7 rsi: 0000000000000000 rdi: 0000000000000dba (XEN) rbp: 0000000000000182 rsp: 0000000000000db0 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 0000000000000010 cr4: 0000000000000000 (XEN) cr3: 0000000000000000 cr2: 0000000000000000 (XEN) ds: 9fc0 es: 9e00 fs: 0000 gs: 0000 ss: 9e00 cs: e40a =================8<================= (XEN) realmode.c:115:d5 Failed to emulate insn. (XEN) realmode.c:165:d5 Real-mode emulation failed @ c5d5:000242bc: d9 33 01 fc 30 34 (XEN) domain_crash called from realmode.c:166 (XEN) Domain 5 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.1.3-rc1-pre x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: c5d5:[<00000000000242bc>] (XEN) RFLAGS: 0000000000010013 CONTEXT: hvm guest (XEN) rax: 000000000000001b rbx: 0000000000000702 rcx: 0000000000010ba7 (XEN) rdx: 0000000000008fd5 rsi: 0000000000001333 rdi: 000000000000900e (XEN) rbp: 000000000000703e rsp: 000000000000c5cf r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 0000000000000010 cr4: 0000000000000000 (XEN) cr3: 0000000000000000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0000 cs: c5d5 (XEN) [VT-D]iommu.c:856: iommu_fault_status: Primary Pending Fault (XEN) [VT-D]iommu.c:831: DMAR:[DMA Write] Request device [0d:00.1] fault addr d8964f44000, iommu reg = ffff82c3fff57000 (XEN) DMAR:[fault reason 05h] PTE Write access is not set (XEN) print_vtd_entries: iommu = ffff83045ce565c0 bdf = d:0.1 gmfn = d8964f44 (XEN) root_entry = ffff8304519d1000 (XEN) root_entry[d] = 4127af001 (XEN) context = ffff8304127af000 (XEN) context[1] = 2_414aca001 (XEN) l4 = ffff830414aca000 (XEN) l4_index = 1b (XEN) l4[1b] = 0 (XEN) l4[1b] not present =================8<================= If I try to restart the crashed VM, the same crash always occurs again during POST (the last thing I see on the VNC console is the BIOS boot, before the connection terminates). A dom0 reboot is necessary to get things to work again. 0d:00.1 is part of an Intel 82575GB quad port network adapter. The adapter contains three ports, 0d:00.0, 0d:00.1, 0e:00.0, 0e:00.1. Each of them is assigned to a VM. So far the crashes have occurred to VMs using 0d:00.1, 0e:00.0 and 0e:00.1. (Pretty sure a crash involving 0d:00.0 will come soon). Is this a potential bug, or (more likely?) problematic hardware? The relevant PCI subtree looks like this: =================8<================= \-[0000:00]-+-00.0 +-03.0-[01]--+-00.0 | \-00.1 +-05.0-[02-0e]----00.0-[03-0e]--+-00.0-[04]----00.0 +-02.0-[05-0a]----00.0-[06-0a]--+-02.0-[07]----00.0 | +-03.0-[08]----00.0 | +-04.0-[09]----00.0 | \-05.0-[0a]----00.0 \-03.0-[0b-0e]----00.0-[0c-0e]--+-02.0-[0d]--+-00.0 | \-00.1 \-04.0-[0e]--+-00.0 \-00.1 =================8<================= Thanks! _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |