From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: sata_nv times out for BD-ROM iHOS104-08 Date: Tue, 09 Mar 2010 10:21:02 +0900 Message-ID: <4B95A27E.9010302@kernel.org> References: <4B67A149.10406@kernel.org> <4B7C9CEE.4080902@kernel.org> <4B8085E7.5000501@kernel.org> <4B833FA1.8030207@kernel.org> <4B8CFAF4.7030303@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: =?UTF-8?B?Q2VuZ2l6IEfDvG5heQ==?= Cc: Robert Hancock , "linux-kernel@vger.kernel.org" , "linux-ide@vger.kernel.org" List-Id: linux-ide@vger.kernel.org On 03/09/2010 04:17 AM, Cengiz G=C3=BCnay wrote: > Hello, >=20 > Sorry for the delay, I was confused about managing so many patches, > but I realized that you're sending me cumulative patches that I can > apply to the original. I just want to remind you that I still have th= e > patches to the other two files: libata-eh.c libata-sff.c >=20 > On Tue, Mar 2, 2010 at 6:48 AM, Tejun Heo wrote: >> Hmmm... the drive is timing out even on 4k READ10's. This shouldn't >> really be happening. Can you please try this one? >=20 > Applied. It did not change anything visibly (dmesg attached). I have > also been getting other SCSI errors since we started communicating > with the device (search for sr0 in dmesg). I wonder if they give any > hints? Here's one: >=20 > sr 4:0:0:0: [sr0] Result: hostbyte=3DDID_OK driverbyte=3DDRIVER_SENSE > sr 4:0:0:0: [sr0] Sense Key : Aborted Command [current] [descriptor] > Descriptor sense data with sense descriptors (in hex): > 72 0b 00 00 00 00 00 0e 09 0c 00 00 00 02 00 00 > 00 20 00 00 a0 40 > sr 4:0:0:0: [sr0] Add. Sense: No additional sense information > sr 4:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 40 00 > end_request: I/O error, dev sr0, sector 0 Hmmm... can you please post full dmesg? --=20 tejun