Tom Rotenberg
2009-Jun-09 16:49 UTC
[Xen-devel] Problem with Xen 3.4 and vtd on T500 with Intel graphics card
Hi all,
I tried to use the Xen 3.4 on a Lenovo T500 to try and PT the Intel graphics
card (00:02.0, and 00:02.1) to a domU. For some reason, it prints a lot of
messages about iommu page faults, and after that causes dom0 to hang
(sometimes i get a message which tells that there is a soft lockup on
cpu#1).
When i try the same thing on the ATI graphic card on the same T500, it
doesn''t print any iommu page fault messages.
Does anyone knows anything about this issue? i saw a few other mails talking
about what it seems to be the same problem, but none of them had a working
solution for this hang. i don''t understand why dom0 hangs from a domU
PT?
P.S. I am using the ''iommu_inclusive_mapping'' in the boot
parameters (since
otherwise dom0 won''t boot).
These are the last lines of the xen console:
(XEN) [VT-D]iommu.c:1364:d0 domain_context_unmap:PCI: bdf = 0:2.0
(XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:691: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:676: iommu_fault:DMA Write: 0:2.0 addr 0 REASON 2
iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: iommu = ffff83007c22c2c0 bdf = 0:2:0 gmfn = 0
(XEN) root_entry = ffff83007c2ca000
(XEN) root_entry[0] = 789bd001
(XEN) context = ffff8300789bd000
(XEN) context[10] = 0_0
(XEN) ctxt_entry[10] not present
(XEN) [VT-D]iommu.c:1252:d0 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]iommu.c:1252:d0 domain_context_mapping:PCI: bdf = 0:2.0
(XEN) [VT-D]io.c:251:d0 VT-d irq bind: m_irq = ff device = 2 intx = 0
(XEN) domctl.c:835:d0 memory_map:add: gfn=a0 mfn=a0 nr_mfns=20
(XEN) domctl.c:886:d0 ioport_map:add f_gport=3b0 f_mport=3b0 np=30
(XEN) [VT-D]iommu.c:1364:d0 domain_context_unmap:PCI: bdf = 0:2.1
(XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:691: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:676: iommu_fault:DMA Write: 0:2.0 addr 3fef8a000 REASON
5 iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: iommu = ffff83007c22c2c0 bdf = 0:2:0 gmfn = 3fef8a
(XEN) root_entry = ffff83007c2ca000
(XEN) root_entry[0] = 789bd001
(XEN) context = ffff8300789bd000
(XEN) context[10] = 201_2b4ea001
(XEN) l3 = ffff83002b4ea000
(XEN) l3_index = f
(XEN) l3[f] = 0
(XEN) l3[f] not present
(XEN) [VT-D]iommu.c:1252:d0 domain_context_mapping:PCI: bdf = 0:2.1
(XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:691: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:676: iommu_fault:DMA Write: 0:2.0 addr 3fef8a000 REASON
5 iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: iommu = ffff83007c22c2c0 bdf = 0:2:0 gmfn = 3fef8a
(XEN) root_entry = ffff83007c2ca000
(XEN) root_entry[0] = 789bd001
(XEN) context = ffff8300789bd000
(XEN) context[10] = 201_2b4ea001
(XEN) l3 = ffff83002b4ea000
(XEN) l3_index = f
(XEN) l3[f] = 0
(XEN) l3[f] not present
(XEN) [VT-D]iommu.c:722: iommu_page_fault: iommu->reg = ffff828bfff56000
(XEN) [VT-D]iommu.c:691: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:694: iommu_fault_status: Primary Pending Fault
(XEN) [VT-D]iommu.c:676: iommu_fault:DMA Write: 0:2.0 addr 3fef8a000 REASON
5 iommu->reg = ffff828bfff56000
(XEN) print_vtd_entries: iommu = ffff83007c22c2c0 bdf = 0:2:0 gmfn = 3fef8a
(XEN) root_entry = ffff83007c2ca000
(XEN) root_entry[0] = 789bd001
(XEN) context = ffff8300789bd000
(XEN) context[10] = 201_2b4ea001
(XEN) l3 = ffff83002b4ea000
(XEN) l3_index = f
(XEN) l3[f] = 0
(XEN) l3[f] not present
Thanks,
Tom
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel