Rome Pierce
2011-Jan-01 15:59 UTC
[Xen-users] (XEN) physdev.c:61: dom1: map invalid irq 1251
Hello,
i''m using the latest Xen 4.0 testing from the mercurial repository and
i want to passthrough my Intel Core gpu. But somehow it has a weird IRQ of 1251.
So i cant start the vm if i set pci=[''00:02.0'']. The device is
bound to the pciback driver correctly.
The interesting part of xm dmesg (appears when i start the vm):
(XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf = 0:2.0
(XEN) [VT-D]iommu.c:1362: d1:PCI: map bdf = 0:2.0
(XEN) physdev.c:61: dom1: map invalid irq 1251
(XEN) [VT-D]io.c:300: d1: bind: m_gsi=55 g_gsi=36 device=5 intx=0
(XEN) [VT-D]iommu.c:1484: d1:PCI: unmap bdf = 0:2.0
(XEN) [VT-D]iommu.c:1362: d0:PCI: map bdf = 0:2.0
lspci -vvv:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 12) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. Device 7636
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 1251
Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at cc00 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Address: fee0800c Data: 4161
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a4] PCI Advanced Features
AFCap: TP+ FLR+
AFCtrl: FLR-
AFStatus: TP-
Kernel driver in use: pciback
--
Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Pasi Kärkkäinen
2011-Jan-05 09:54 UTC
Re: [Xen-users] (XEN) physdev.c:61: dom1: map invalid irq 1251
Adding xen-devel to CC list.. -- Pasi On Sat, Jan 01, 2011 at 04:59:39PM +0100, Rome Pierce wrote:> Hello, > > i''m using the latest Xen 4.0 testing from the mercurial repository and i want to passthrough my Intel Core gpu. But somehow it has a weird IRQ of 1251. So i cant start the vm if i set pci=[''00:02.0'']. The device is bound to the pciback driver correctly. > > The interesting part of xm dmesg (appears when i start the vm): > > (XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf = 0:2.0 > (XEN) [VT-D]iommu.c:1362: d1:PCI: map bdf = 0:2.0 > (XEN) physdev.c:61: dom1: map invalid irq 1251 > (XEN) [VT-D]io.c:300: d1: bind: m_gsi=55 g_gsi=36 device=5 intx=0 > (XEN) [VT-D]iommu.c:1484: d1:PCI: unmap bdf = 0:2.0 > (XEN) [VT-D]iommu.c:1362: d0:PCI: map bdf = 0:2.0 > > > lspci -vvv: > > 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller]) > Subsystem: Micro-Star International Co., Ltd. Device 7636 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 0 > Interrupt: pin A routed to IRQ 1251 > Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=4M] > Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M] > Region 4: I/O ports at cc00 [size=8] > Expansion ROM at <unassigned> [disabled] > Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- > Address: fee0800c Data: 4161 > Capabilities: [d0] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > Capabilities: [a4] PCI Advanced Features > AFCap: TP+ FLR+ > AFCtrl: FLR- > AFStatus: TP- > Kernel driver in use: pciback > > -- > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Konrad Rzeszutek Wilk
2011-Jan-06 16:42 UTC
Re: [Xen-devel] Re: [Xen-users] (XEN) physdev.c:61: dom1: map invalid irq 1251
On Wed, Jan 05, 2011 at 11:54:35AM +0200, Pasi Kärkkäinen wrote:> > Adding xen-devel to CC list.. > > -- Pasi > > On Sat, Jan 01, 2011 at 04:59:39PM +0100, Rome Pierce wrote: > > Hello, > > > > i''m using the latest Xen 4.0 testing from the mercurial repository and i want to passthrough my Intel Core gpu. But somehow it has a weird IRQ of 1251. So i cant start the vm if i set pci=[''00:02.0'']. The device is bound to the pciback driver correctly. > >Does this happen only with this device? What does /proc/interrupts look like? Is the Dom0 64-bit or 32-bit? What does ''xm debug-keys <x>'' where x is M, i, Q, z tell you before and after you have tried to pass in the PCI device to the guest? Oh, and what does ''xm dmesg'' show?> > The interesting part of xm dmesg (appears when i start the vm): > > > > (XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf = 0:2.0 > > (XEN) [VT-D]iommu.c:1362: d1:PCI: map bdf = 0:2.0 > > (XEN) physdev.c:61: dom1: map invalid irq 1251 > > (XEN) [VT-D]io.c:300: d1: bind: m_gsi=55 g_gsi=36 device=5 intx=0 > > (XEN) [VT-D]iommu.c:1484: d1:PCI: unmap bdf = 0:2.0 > > (XEN) [VT-D]iommu.c:1362: d0:PCI: map bdf = 0:2.0 > > > > > > lspci -vvv: > > > > 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller]) > > Subsystem: Micro-Star International Co., Ltd. Device 7636 > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ > > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > > Latency: 0 > > Interrupt: pin A routed to IRQ 1251 > > Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size=4M] > > Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M] > > Region 4: I/O ports at cc00 [size=8] > > Expansion ROM at <unassigned> [disabled] > > Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- > > Address: fee0800c Data: 4161 > > Capabilities: [d0] Power Management version 2 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > > Capabilities: [a4] PCI Advanced Features > > AFCap: TP+ FLR+ > > AFCtrl: FLR- > > AFStatus: TP- > > Kernel driver in use: pciback > > > > -- > > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Seemingly Similar Threads
- (XEN) physdev.c:61: dom1: map invalid irq 1251
- PROBLEM: new kernel 3.15.0-rc8 hangs completely with CONFIG_DRM_NOUVEAU enabled
- Suggest Hardware Raid Controller Card
- Assistance in tracking a kernel/nouveau error
- [Kernel 3.1.5] [OCFS2] After many write/delete on ocfs2 both servers in cluster kernel oops