| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Trying to pass-through Intel graphics device - causes a
Hi Tom,
IGD passthrough is not supported on xen-unstable yet. We are working on it,
will send out the patches in near future.
Regards,
Weidong
Tom Rotenberg wrote:
> Hi,
>
> I tried to pass-through the 00:02.0 & 00:02.1 devices (Intel
> integrated graphics device) on a Lenovo T500, using the latest
> xen-unstable, and i got a xen panic.
> Here are the last lines of the console log:
> "
> .....
> (XEN) [VT-D]iommu.c:1296:d0 domain_context_unmap:PCI: bdf = 0:2.0
> (XEN) [VT-D]iommu.c:716: iommu_page_fault: iommu->reg =
> ffff828bfff56000 (XEN) [VT-D]iommu.c:685: iommu_fault_status: Fault
> Overflow (XEN) [VT-D]iommu.c:688: iommu_fault_status: Primary Pending
> Fault (XEN) [VT-D]iommu.c:670: iommu_fault:DMA Write: 0:2.0 addr 0
> REASON 2 iommu->reg = ffff828bfff56000
> (XEN) [VT-D]iommu.c:1182:d0 domain_context_mapping:PCI: bdf = 0:2.0
> (XEN) print_vtd_entries: iommu = ffff83007c4bd0d0 bdf = 0:2:0 gmfn = 0
> (XEN) root_entry = ffff83007c4ce000
> (XEN) root_entry[0] = 78910001
> (XEN) context = ffff830078910000
> (XEN) context[10] = 0_0
> (XEN) ctxt_entry[10] not present
> (XEN) [VT-D]iommu.c:1182:d0 domain_context_mapping:PCI: bdf = 0:2.0
> (XEN) [VT-D]io.c:280:d0 VT-d irq bind: m_irq = 37 device = 5 intx = 0
> (XEN) [VT-D]iommu.c:1296:d0 domain_context_unmap:PCI: bdf = 0:2.1
> (XEN) [VT-D]iommu.c:716: iommu_page_fault: iommu->reg =
> ffff828bfff56000 (XEN) [VT-D]iommu.c:685: iommu_fault_status: Fault
> Overflow (XEN) [VT-D]iommu.c:688: iommu_fault_status: Primary Pending
> Fault (XEN) [VT-D]iommu.c:1182:d0 domain_context_mapping:PCI: bdf =
> 0:2.1 (XEN) [VT-D]iommu.c:670: iommu_fault:DMA Write: 0:2.0 addr
> ffffff000
> REASON 5 iommu->reg = ffff828bfff56000
> (XEN) print_vtd_entries: iommu = ffff83007c4bd0d0 bdf = 0:2:0 gmfn =
> ffffff (XEN) root_entry = ffff83007c4ce000
> (XEN) root_entry[0] = 78910001
> (XEN) context = ffff830078910000
> (XEN) context[10] = 201_75131001
> (XEN) l3 = ffff830075131000
> (XEN) l3_index = 3f
> (XEN) l3[3f] = 0
> (XEN) l3[3f] not present
> (XEN) [VT-D]iommu.c:716: iommu_page_fault: iommu->reg =
> ffff828bfff56000 (XEN) [VT-D]iommu.c:685: iommu_fault_status: Fault
> Overflow (XEN) [VT-D]iommu.c:688: iommu_fault_status: Primary Pending
> Fault (XEN) [VT-D]iommu.c:670: iommu_fault:DMA Write: 0:2.0 addr
> ffffff000
> REASON 5 iommu->reg = ffff828bfff56000
> (XEN) print_vtd_entries: iommu = ffff83007c4bd0d0 bdf = 0:2:0 gmfn =
> ffffff (XEN) root_entry = ffff83007c4ce000
> (XEN) root_entry[0] = 78910001
> (XEN) context = ffff830078910000
> (XEN) context[10] = 201_75131001
> (XEN) l3 = ffff830075131000
> (XEN) l3_index = 3f
> (XEN) l3[3f] = 0
> (XEN) l3[3f] not present
> (XEN) [VT-D]iommu.c:716: iommu_page_fault: iommu->reg =
> ffff828bfff56000 (XEN) [VT-D]iommu.c:685: iommu_fault_status: Fault
> Overflow (XEN) [VT-D]iommu.c:688: iommu_fault_status: Primary Pending
> Fault (XEN) [VT-D]iommu.c:670: iommu_fault:DMA Write: 0:2.0 addr
> ffffff000
> REASON 5 iommu->reg = ffff828bfff56000
> (XEN) print_vtd_entries: iommu = ffff83007c4bd0d0 bdf = 0:2:0 gmfn =
> ffffff (XEN) root_entry = ffff83007c4ce000
> (XEN) root_entry[0] = 78910001
> (XEN) context = ffff830078910000
> (XEN) context[10] = 201_75131001
> (XEN) l3 = ffff830075131000
> (XEN) l3_index = 3f
> (XEN) l3[3f] = 0
> (XEN) l3[3f] not present
> (XEN) [VT-D]iommu.c:716: iommu_page_fault: iommu->reg =
> ffff828bfff56000 (XEN) [VT-D]iommu.c:685: iommu_fault_status: Fault
> Overflow (XEN) [VT-D]iommu.c:688: iommu_fault_status: Primary Pending
> Fault (XEN) [VT-D]iommu.c:670: iommu_fault:DMA Write: 0:2.0 addr
> ffffff000
> REASON 5 iommu->reg = ffff828bfff56000
> (XEN) print_vtd_entries: iommu = ffff83007c4bd0d0 bdf = 0:2:0 gmfn =
> ffffff (XEN) root_entry = ffff83007c4ce000
> (XEN) root_entry[0] = 78910001
> (XEN) context = ffff830078910000
> (XEN) context[10] = 201_75131001
> (XEN) l3 = ffff830075131000
> (XEN) l3_index = 3f
> (XEN) l3[3f] = 0
> (XEN) l3[3f] not present
> (XEN) Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at
> irq.c:749 (XEN) ----[ Xen-3.5-unstable x86_64 debug=y Not tainted
> ]---- (XEN) CPU: 0
> (XEN) RIP: e008:[<ffff828c801534ad>] do_IRQ+0x2c3/0x690
> (XEN) RFLAGS: 0000000000010046 CONTEXT: hypervisor
> (XEN) rax: 00000000000000c0 rbx: ffff83007c080a80 rcx:
> ffff828c8024c6c0 (XEN) rdx: 0000000000000001 rsi: 00000000000000c0
> rdi: 0000000000000001 (XEN) rbp: ffff828c802d7d18 rsp:
> ffff828c802d7c78 r8: 0000000000000002 (XEN) r9: 0000ffff0000ffff
> r10: 00ff00ff00ff00ff r11: 0f0f0f0f0f0f0f0f (XEN) r12:
> 0000000000000014 r13: ffff828c802d7d28 r14: ffff83007c0dac50
> (XEN) r15: ffff83007c4bcb60 cr0: 000000008005003b cr4:
> 00000000000026f0 (XEN) cr3: 000000007aaf9000 cr2: 0000000000d51550
> (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008
> (XEN) Xen stack trace from rsp=ffff828c802d7c78: (XEN)
> 0000000000000004 0000000000000004 ffff8300751311f8 ffff830075131000
> (XEN) 0000000000000014 ffff83007c080ab4 00000014802d7cf8
> ffff828c8013ad01 (XEN) 000000008011be55 0000000000000000
> ffff83007c080a80 0000000000000086 (XEN) ffff828c802d7cf8
> ffff828c8011be30 ffff83007c4bd108 0000000000000002 (XEN)
> 0000000000000001 ffff828c80168374 ffff828c802d7e00 ffff83007c4bcb60
> (XEN) 00007d737fd282b7 ffff828c8014cb56 ffff83007c4bcb60
> ffff828c802d7e00 (XEN) ffff828c80168374 0000000000000001
> ffff828c802d7df0 0000000000000002 (XEN) 0f0f0f0f0f0f0f0f
> 00ff00ff00ff00ff 0000ffff0000ffff 0000000000000002 (XEN)
> 0000000000000000 0000000000000001 ffff828c802ea700 ffff828c8024ca20
> (XEN) 0000000000000008 000000c000000000 ffff828c80164e52
> 000000000000e008 (XEN) 0000000000000246 ffff828c802d7dd0
> 000000000000e010 ffff828c8024c100 (XEN) 0000000000000000
> ffff828c8016831d ffff83007c4bcb68 ffff828c802d7e20 (XEN)
> ffff828c80168372 0000000000000003 0000000000000002 00000023468c5549
> (XEN) 0000000000000000 ffff828c802d7e50 ffff828c8011dc33
> 0000000000000002 (XEN) ffff828c80306a60 00000023468bdaa9
> ffff828c8024c100 ffff828c802d7ea0 (XEN) ffff828c8011dd5d
> ffff828c802d7f28 ffff828c8024c100 ffff83007c4bcb60 (XEN)
> 0000000000000000 ffff828c802285a0 ffff828c802d7f28 ffff828c802ea700
> (XEN) ffff828c802ec700 ffff828c802d7ee0 ffff828c8011bce1
> 0000003000000000 (XEN) ffff828c802d7f28 ffff828c802285a0
> ffff828c802d7f28 ffff828c8024ca00 (XEN) ffff828c80228ab8
> ffff828c802d7f20 ffff828c80148ac5 ffff830078908000 (XEN) Xen call
> trace: (XEN) [<ffff828c801534ad>] do_IRQ+0x2c3/0x690 (XEN)
> [<ffff828c8014cb56>] common_interrupt+0x26/0x30 (XEN)
> [<ffff828c80164e52>] on_selected_cpus+0xdb/0x11f (XEN)
> [<ffff828c80168372>] time_calibration+0x55/0x57 (XEN)
> [<ffff828c8011dc33>] execute_timer+0x2e/0x4c (XEN)
> [<ffff828c8011dd5d>] timer_softirq_action+0x10c/0x331 (XEN)
> [<ffff828c8011bce1>] do_softirq+0x6f/0x8e (XEN)
> [<ffff828c80148ac5>] idle_loop+0x8f/0x94 (XEN) (XEN) (XEN)
> **************************************** (XEN) Panic on CPU 0: (XEN)
> Assertion '(sp == 0) || (peoi[sp-1].vector < vector)' failed at
> irq.c:749 (XEN) **************************************** (XEN) (XEN)
> Reboot in five seconds...
>
>
> In previous versions i have tried it, it caused the whole machine to
> get stuck, with no output, so it looks like now, it's better - i
> finally get a xen panic :)
>
> Can someone please help me with this?
>
> Tom
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home