From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
Jeff Garzik <jgarzik@pobox.com>, Matt Grice <mcjgrice@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: libata errors
Date: Sun, 12 Apr 2009 11:15:47 -0700 [thread overview]
Message-ID: <49E22FD3.2010005@kernel.org> (raw)
In-Reply-To: <49E0DAC0.1030901@gmail.com>
Hello,
Robert Hancock wrote:
> I tend to doubt that the driver is doing the wrong thing.
I've tested everything including recording and cd ripping and most of
my devices seem happy but you never know.
> I suspect it's more that ATAPI devices on SATA are about as
> standards-compliant in general as ATAPI devices on PATA (which is to
> say not very good) and some of them break if the controller does
> something slightly differently or with different timing, which is
> quite possible in AHCI mode.
>
> Tejun was looking at some SATA analyzer traces of a few drives that were
> apparently failing consistently on AHCI. Tejun, did you get anywhere
> with this?
I need to take a deeper look at that but in general I couldn't find
anything standing out. After a series of ATAPI changes (IIRC, the DMA
padding change was the last thing), most ATAPI bug reports got
resolved and I'm not getting many ATAPI failure bug reports other than
recent ahci ones anymore. I'm not sure whethre it indicates that we
finally got it right or something else tho.
Jeff, what kind of failure are you seeing?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-04-13 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 20:40 libata errors Matt Grice
2009-04-07 21:41 ` Jeff Garzik
2009-04-08 8:14 ` Mikael Pettersson
2009-04-08 13:25 ` Jeff Garzik
2009-04-08 17:52 ` Matt Grice
2009-04-11 18:00 ` Robert Hancock
2009-04-12 18:15 ` Tejun Heo [this message]
2009-04-13 9:30 ` Jeff Garzik
2009-04-14 0:56 ` Robert Hancock
2009-04-08 2:06 ` Robert Hancock
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=49E22FD3.2010005@kernel.org \
--to=tj@kernel.org \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mcjgrice@gmail.com \
--cc=mikpe@it.uu.se \
/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).