From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Hancock Subject: Re: libata errors Date: Mon, 13 Apr 2009 18:56:31 -0600 Message-ID: <49E3DF3F.2020502@gmail.com> References: <4b215b9d0904071340w16a65b5bs64f6161b6042b4f1@mail.gmail.com> <49DBC889.3080304@pobox.com> <18908.23783.745239.601473@pilspetsen.it.uu.se> <49E0DAC0.1030901@gmail.com> <49E22FD3.2010005@kernel.org> <49E3061C.4030006@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-fx0-f158.google.com ([209.85.220.158]:47496 "EHLO mail-fx0-f158.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752257AbZDNA4i (ORCPT ); Mon, 13 Apr 2009 20:56:38 -0400 Received: by fxm2 with SMTP id 2so2209977fxm.37 for ; Mon, 13 Apr 2009 17:56:36 -0700 (PDT) In-Reply-To: <49E3061C.4030006@pobox.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Jeff Garzik Cc: Tejun Heo , Mikael Pettersson , Matt Grice , linux-ide@vger.kernel.org Jeff Garzik wrote: > Tejun Heo wrote: >> 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? > > Hardware: SATA DVD-ROM/CD-RW devices, AHCI, ICH$foo > > Reading and writing data CDs and DVDs works fine. Ripping audio CDs > using gRip application leads to timeouts almost immediately. Well, it's a potentially unusual transfer length compared to other commands, which might be part of it. Do you have some error output? It would be useful to look at the reported failed CDB.