From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Re: [Xen-users] (XEN) physdev.c:61: dom1: map invalid irq 1251 Date: Thu, 6 Jan 2011 11:42:33 -0500 Message-ID: <20110106164233.GA18774@dumpdata.com> References: <20110101155939.14640@gmx.net> <20110105095435.GT2754@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20110105095435.GT2754@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: Rome Pierce , xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, Jan 05, 2011 at 11:54:35AM +0200, Pasi K=E4rkk=E4inen wrote: >=20 > Adding xen-devel to CC list.. >=20 > -- Pasi >=20 > On Sat, Jan 01, 2011 at 04:59:39PM +0100, Rome Pierce wrote: > > Hello, > >=20 > > i'm using the latest Xen 4.0 testing from the mercurial repository an= d 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=3D['00:02.0']. The device i= s bound to the pciback driver correctly. > >=20 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 ' 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): > >=20 > > (XEN) [VT-D]iommu.c:1484: d0:PCI: unmap bdf =3D 0:2.0 > > (XEN) [VT-D]iommu.c:1362: d1:PCI: map bdf =3D 0:2.0 > > (XEN) physdev.c:61: dom1: map invalid irq 1251 > > (XEN) [VT-D]io.c:300: d1: bind: m_gsi=3D55 g_gsi=3D36 device=3D5 intx= =3D0 > > (XEN) [VT-D]iommu.c:1484: d1:PCI: unmap bdf =3D 0:2.0 > > (XEN) [VT-D]iommu.c:1362: d0:PCI: map bdf =3D 0:2.0 > >=20 > >=20 > > lspci -vvv: > >=20 > > 00:02.0 VGA compatible controller: Intel Corporation Core Processor I= ntegrated 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- P= arErr- Stepping- SERR- FastB2B- DisINTx+ > > Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbo= rt- SERR- > Latency: 0 > > Interrupt: pin A routed to IRQ 1251 > > Region 0: Memory at fb800000 (64-bit, non-prefetchable) [size= =3D4M] > > Region 2: Memory at d0000000 (64-bit, prefetchable) [size=3D2= 56M] > > Region 4: I/O ports at cc00 [size=3D8] > > Expansion ROM at [disabled] > > Capabilities: [90] MSI: Enable- Count=3D1/1 Maskable- 64bit- > > Address: fee0800c Data: 4161 > > Capabilities: [d0] Power Management version 2 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=3D0mA PME(D0-,= D1-,D2-,D3hot-,D3cold-) > > Status: D0 NoSoftRst- PME-Enable- DSel=3D0 DScale=3D0= PME- > > Capabilities: [a4] PCI Advanced Features > > AFCap: TP+ FLR+ > > AFCtrl: FLR- > > AFStatus: TP- > > Kernel driver in use: pciback > >=20 > > --=20 > > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! =20 > > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail >=20 >=20 >=20 > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel