WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] pv_ops dom0 kernel failure with ata_piix

To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Subject: Re: [Xen-devel] pv_ops dom0 kernel failure with ata_piix
From: "Andrew Lyon" <andrew.lyon@xxxxxxxxx>
Date: Fri, 9 Jan 2009 21:01:59 +0000
Cc: Todd Deshane <deshantm@xxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 09 Jan 2009 13:02:32 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=E0y8ClbhNdv1LxZNrM37gCJsMOp4QfsbzYGYqEetJEY=; b=K15duJKnhWPVqwRSyAHXgNJhMYWIfN/1UEq0MmVYNfpAjDTAFZkIpvK4D4Nv39R/HS lVcLeSuvdy43nWaJIzf+7WJRv0RLQoMUdHcP149sG1GQjVyfMHOGG5sSWWlh15nZvnQv nDYVjeTt0mXyhL+oBC1mtJM0xO0LSetPpWuYE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=NjzyI9E4FqUtcfVtTDljZD93NASTpD3CJKQK9r0qBOetFibVIjEHkp/uNtE/ysumw1 E7dywDFNsv+B0deYj5yZUiKyjDMTpQg3bX0hKFjiGuzynAu9upQvXwNhjl74wKkg7Xcs eHgSh1g0uI4qNaOfEkxuStXNipMr8zH5Ll4Mw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090109174006.GR15052@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20081230144422.GD15052@xxxxxxxxxxxxxxx> <20081230161939.GG15052@xxxxxxxxxxxxxxx> <20081230162835.GH15052@xxxxxxxxxxxxxxx> <1e16a9ed0812300847s5dd1c2afj4fabcd4169258e40@xxxxxxxxxxxxxx> <20081230165211.GI15052@xxxxxxxxxxxxxxx> <20081230181845.GK15052@xxxxxxxxxxxxxxx> <20081230190356.GL15052@xxxxxxxxxxxxxxx> <495BE5E1.40602@xxxxxxxx> <20090102064444.GN15052@xxxxxxxxxxxxxxx> <20090109174006.GR15052@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Jan 9, 2009 at 5:40 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> On Fri, Jan 02, 2009 at 08:44:44AM +0200, Pasi Kärkkäinen wrote:
>> On Thu, Jan 01, 2009 at 08:36:33AM +1100, Jeremy Fitzhardinge wrote:
>> > Pasi Kärkkäinen wrote:
>> > >On Tue, Dec 30, 2008 at 08:18:45PM +0200, Pasi Kärkkäinen wrote:
>> > >
>> > >>On Tue, Dec 30, 2008 at 06:52:11PM +0200, Pasi Kärkkäinen wrote:
>> > >>
>> > >>>On Tue, Dec 30, 2008 at 11:47:40AM -0500, Todd Deshane wrote:
>> > >>>
>> > >>>>On Tue, Dec 30, 2008 at 11:28 AM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>> > >>>>
>> > >>>>>>>Try changing the SATA mode of the disk in the BIOS to either legacy
>> > >>>>>>>or
>> > >>>>>>>ATA, depending
>> > >>>>>>>on what you bios supports.
>> > >>>>>>>
>> > >>>>>>>There is still a known issue with some of the AHCI stuff.
>> > >>>>>>>
>> > >>>>>>>
>> > >>>>>>I'm not using AHCI at all.. AHCI (SATA) controller does not have any
>> > >>>>>>disks
>> > >>>>>>plugged in.
>> > >>>>>>
>> > >>>>>>My (only) disk is attached to IDE/PATA ICH6 controller..
>> > >>>>>>
>> > >>>>>>
>> > >>>>>I tried disabling AHCI anyway (even when I'm not using the AHCI SATA
>> > >>>>>controller), but it didn't help.
>> > >>>>>
>> > >>>>>Booting the pv_ops dom0 kernel still fails.. because the IDE/PATA
>> > >>>>>controller
>> > >>>>>still gets disabled (just like in the logs above) for some unknown
>> > >>>>>reason.
>> > >>>>>
>> > >>>>>-- Pasi
>> > >>>>>
>> > >>>>So from the log it looks like you are getting a hard crash?
>> > >>>>
>> > >>>>
>> > >>>No, it's not a hard crash.. I'm able to reboot the box with
>> > >>>ctrl-alt-del.
>> > >>>
>> > >>>>Did you try adding noreboot to the xen command line and then trying
>> > >>>>to get any more information with sysreq stuff?
>> > >>>>
>> > >>>>Another thing that I noticed in the log is:
>> > >>>>
>> > >>>>irq 12: nobody cared (try booting with the "irqpoll" option)
>> > >>>>
>> > >>>>Is it an smp kernel? I had some weird problems when passing nosmp at
>> > >>>>one point.
>> > >>>>
>> > >>>>
>> > >>>Yep, it is SMP kernel..
>> > >>>
>> > >>>
>> > >>>>I don't recognize this crash, those module traces, at least for me were
>> > >>>>non-fatal and didn't cause a crash. I was normally just dropped to a
>> > >>>>initramfs prompt in the case when the disk was not detected properly.
>> > >>>>
>> > >>>>I was then able to at least look around and check that modules were
>> > >>>>loaded correctly etc.
>> > >>>>
>> > >>>>
>> > >>>The problem seems to be the IDE controller/disk is not detected at all..
>> > >>>because the device gets disabled for some reason during ata_piix
>> > >>>loading/probing..
>> > >>>
>> > >>>That is the only disk I have, so the root partition is on it.
>> > >>>
>> > >>>Same kernel works just fine on baremetal without Xen.
>> > >>>
>> > >>>
>> > >>So I guess the subject should be 'failure with ata_piix' instead of
>> > >>'crash'..
>> > >>Anyway, there seems to be problems with ata_piix too.. in addition to
>> > >>AHCI.
>> > >>
>> > >>Jeremy: Can you think of anything to try?
>> > >>
>> > >>
>> > >
>> > >I tried booting with "nosmp" dom0 kernel parameter:
>> > >
>> >
>> > Yes, nosmp is known to make things worse.  It has the side-effect of
>> > disabling io_apic support, so all the interrupt stuff fails in the way
>> > you've noticed.
>> >
>>
>> Yep. "nosmp" was just something I tried to see if it makes any difference.
>> It didn't help.
>>
>> Anyway, have you seen/heard of this problem with ata_piix earlier?
>>
>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-1.txt
>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-2.txt
>>
>> Same kernel on baremetal without Xen:
>> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/baremetal-dmesg.txt
>>
>
> I just upgraded to newly released Xen 3.3.1 hypervisor but unfortunately it
> didn't seem to help with my problem.. I still get the exact same errors 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 triggering 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

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...

Andy

>
> -- Pasi
>
> _______________________________________________
> 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