From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Suggestions for debugging ata_piix and ahci driver failures on Xen pv_ops dom0 kernel (2.6.29-rcX)
Date: Fri, 6 Feb 2009 14:32:07 +0200 [thread overview]
Message-ID: <20090206123207.GP15052@edu.joroinen.fi> (raw)
In-Reply-To: <498B880E.6070001@gmail.com>
On Thu, Feb 05, 2009 at 06:45:02PM -0600, Robert Hancock wrote:
> Pasi Kärkkäinen wrote:
> >Hello!
> >
> >I'm trying to figure out what's wrong with the pv_ops dom0 kernel/patches
> >[1]
> >causing at least ata_piix and ahci drivers to fail to work.
> >
> >There was legacy IRQ enabling problem earlier with the pv_ops dom0
> >patches, which pretty much prevented the disks from being detected.. but
> >that got fixed. It could still be something related to Xen/dom0 irq
> >handling..
> >I'd be glad if someone could take a look at this 2.6.29-rc3-tip pv_ops
> >dom0 kernel boot log
> >and comment about _possible_ causes for such behaviour of ata_piix and
> >ahci:
> >
> >http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-11-xen331-linux-2.6.29-rc3-atadebug3.txt
> >
> >In that testing box I have just one IDE hdd attached to ata_piix
> >controller, the AHCI controller doesn't
> >have any disks attached.
> >
> >The exact same kernel works OK without problems on baremetal without Xen
> >hypervisor.
>
> Seems like me like ata_piix is not receiving any interrupts.. the
> polling-based IDENTIFY and SET FEATURES work, but the READ NATIVE MAX
> ADDRESS times out and so does the READ DMA that gets tried next.
>
OK. Thanks for pointing this out.
> Note that the ata_piix controller is in legacy mode, not native mode, so
> it's using IRQ 14 and 15, not whatever the hardware may otherwise
> indicate. Could be the problem is related to that.
>
Yep. With earlier version of pv_ops dom0 patches devm_request_irq() call failed
for IRQ 14 and 15 in ata_piix driver, but that has been fixed now..
Calling devm_request_irq() returns success now, but maybe it doesn't actually
work and do what it should?
Thanks for your reply!
-- Pasi
prev parent reply other threads:[~2009-02-06 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 8:28 Pasi Kärkkäinen
2009-02-06 0:45 ` Robert Hancock
2009-02-06 12:32 ` Pasi Kärkkäinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090206123207.GP15052@edu.joroinen.fi \
--to=pasik@iki.fi \
--cc=hancockrwd@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®