From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Fluhr Subject: Re: READ SCSI cmd seems to fail on SATA optical devices... Date: Wed, 15 Nov 2006 16:19:18 +0100 Message-ID: <1163603958.3029.3.camel@de-c-l-110.nero-de.internal> References: <1163434776.2984.21.camel@de-c-l-110.nero-de.internal> <4558BE57.4020700@cfl.rr.com> <1163444160.27291.2.camel@de-c-l-110.nero-de.internal> <1163446372.15249.190.camel@laptopd505.fenrus.org> <1163519125.2998.8.camel@de-c-l-110.nero-de.internal> <4559FBCF.9050203@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4559FBCF.9050203@gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Tejun Heo Cc: Arjan van de Ven , Phillip Susi , jgarzik@pobox.com, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: linux-ide@vger.kernel.org On Wed, 2006-11-15 at 02:24 +0900, Tejun Heo wrote: > > ... and the problem is not in accessing the device itself (this is > > working like a charm) but understanding why a SCSI READ(10) cmd > > sometimes fails as a ATA-padded READ(10) cmd - as discribed in the > Annex > > A of the MMC-5 spec - ALWAYS works. > > -> I would suspect somehow a synchronisation problem somehow in the > > translation of SCSI to ATA command... > > Can you try the attached patch and see if anything changes? > The patch _seems_ to solve my problem. I am just really astonished when I read the diff file :D. Can I expect that it will be merged to the official kernel sources ? Thanks a lot for your answers!