From: Tejun Heo <htejun@gmail.com>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Robert Hancock <hancockr@shaw.ca>, Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: Help interpreting AHCI failure messages
Date: Mon, 22 Dec 2008 18:54:57 +0900 [thread overview]
Message-ID: <494F63F1.3020207@gmail.com> (raw)
In-Reply-To: <f4527be0812220117v6fcc72c6v8012247ec443f636@mail.gmail.com>
Hello,
Andrew Lyon wrote:
>>>>> Furthermore, ata2 - which is sharing the same interrupt - seems to have
>>>>> managed to read the DVD drive's information, so something must be
>>>>> working. But why is it failing for the disk?
>>>> Can you try irqpoll on it?
>>> Here's a log of a run where everything works initially, but then it
>>> starts to fail (about half way into the log). ATA_DEBUG is enabled, so
>>> its pretty verbose.
>>>
>>> http://kraxel.fedorapeople.org/for-jeremy/xeni.log
>>>
>>> Does anything stand out?
>> Can you please exclude pata_acpi from the initrd and see whether
>> anything changes?
>
> I have already tried using a kernel with pata_acpi disabled, it does not help.
There's a BUG messages in the log and several IRQ enable/disable
messages && once timeout happens on one of the ata port, the other one
begins to time out too. I'm out of ideas and think this really needs
a look from someone who knows xen. It doesn't seem to be a libata
problem at this point.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-12-22 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 21:23 Help interpreting AHCI failure messages Jeremy Fitzhardinge
2008-12-13 3:52 ` Robert Hancock
[not found] ` <49434EC9.4070408@goop.org>
[not found] ` <49446DD0.3030600@gmail.com>
2008-12-19 16:30 ` Jeremy Fitzhardinge
2008-12-22 4:05 ` Tejun Heo
2008-12-22 9:17 ` Andrew Lyon
2008-12-22 9:54 ` Tejun Heo [this message]
2008-12-22 18:52 ` Andrew Lyon
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=494F63F1.3020207@gmail.com \
--to=htejun@gmail.com \
--cc=andrew.lyon@gmail.com \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=jeremy@goop.org \
--cc=kraxel@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).