From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pv_ops dom0 kernel failure with ata_piix / irq problems Date: Thu, 22 Jan 2009 12:23:26 -0800 Message-ID: <4978D5BE.8090601@goop.org> References: <20081230161939.GG15052@edu.joroinen.fi> <20081230162835.GH15052@edu.joroinen.fi> <1e16a9ed0812300847s5dd1c2afj4fabcd4169258e40@mail.gmail.com> <20081230165211.GI15052@edu.joroinen.fi> <20081230181845.GK15052@edu.joroinen.fi> <20081230190356.GL15052@edu.joroinen.fi> <495BE5E1.40602@goop.org> <20090102064444.GN15052@edu.joroinen.fi> <20090109174006.GR15052@edu.joroinen.fi> <20090122194645.GJ15052@edu.joroinen.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090122194645.GJ15052@edu.joroinen.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: Todd Deshane , Andrew Lyon , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen wrote: > On Fri, Jan 09, 2009 at 09:01:59PM +0000, Andrew Lyon wrote: > =20 >>> I just upgraded to newly released Xen 3.3.1 hypervisor but unfortunat= ely it >>> didn't seem to help with my problem.. I still get the exact same erro= rs with >>> ata_piix module: >>> >>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-4-= xen331.txt >>> >>> xen_allocate_pirq: returning irq 30 for gsi 18 >>> xen_set_ioapic_routing: irq 30 gsi 18 vector 160 ioapic 0 pin 18 trig= gering 0 polarity 1 >>> ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 30 >>> xen: PCI device 0000:00:1f.1 pin 1 -> irq 30 >>> xen: disable pci device 0000:00:1f.1 >>> ata_piix: probe of 0000:00:1f.1 failed with error -38 >>> =20 >> I don't think the problem is ata_piix, I've tried the pv_ops dom0 >> kernel on a Dell Optiplex 755 and unbranded system with gigabyte >> motherboard, on both systems none of the storage devices worked, >> including ahci, ata_piix, I even tried putting the root filesystem on >> a usb storage device but that too is broken, I think interrupt routing >> is not working at all perhaps? >> >> I'm going to do more testing this weekend... >> >> =20 > > Hello. > > I just did some more testing too.. > > I upgraded to the latest patches for Linux 2.6.29-rc1-tip > > log of xen+kernel from serial console: > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-5-xe= n331-linux-2.6.29-rc1.txt > > (XEN) Command line: dom0_mem=3D1024M loglvl=3Dall guest_loglvl=3Dall co= m1=3D19200,8n1 console=3Dcom1 > Kernel command line: ro root=3D/dev/vg00/lv01 console=3Dhvc0 earlyprint= k=3Dxen pci=3Dnomsi > > And the failing part of the log is here: > > xen_allocate_pirq: returning irq 30 for gsi 18 > xen_set_ioapic_routing: irq 30 gsi 18 vector 160 ioapic 0 pin 18 trigge= ring 0 polarity 1 > ata_piix 0000:00:1f.1: PCI INT A -> GSI 18 (level, low) -> IRQ 30 > xen: PCI device 0000:00:1f.1 pin 1 -> irq 30 > xen: disable pci device 0000:00:1f.1 > Pid: 1, comm: swapper Not tainted 2.6.29-rc1-tip #3 > =20 That means that the ata-piix driver decided it was unhappy for some=20 reason, and decided to fali with ENODEV. It would be very interesting=20 to know what part of the device probe failed. From the Xen perspective,=20 it looks like everything went OK. > Call Trace: > [] ? printk+0xf/0x11 > [] xen_pci_pirq_disable+0x18/0x1c > =20 (This is just a reminder to me to implement this function; it only got=20 called because ata-piix had already decided to fail and was=20 unregistering its resources.) J