From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: [PATCH Linux 2.6.12 00/09] NCQ: generic NCQ completion/error-handling Date: Thu, 30 Jun 2005 09:36:34 +0200 Message-ID: <20050630073633.GF2243@suse.de> References: <20050626152105.D86561FB@htj.dyndns.org> <20050627143344.GI11633@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from ns.virtualhost.dk ([195.184.98.160]:9168 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S262600AbVF3Hhh (ORCPT ); Thu, 30 Jun 2005 03:37:37 -0400 Content-Disposition: inline In-Reply-To: <20050627143344.GI11633@suse.de> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tejun Heo Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org On Mon, Jun 27 2005, Jens Axboe wrote: > On Mon, Jun 27 2005, Tejun Heo wrote: > > Hello, Jeff. > > Hello, Jens. > > > > This patchset implements generic completion and error-handling for > > NCQ commands. This patchset assumes that the previous six misc > > patches to NCQ are applied. > > Excellent, much needed work in that area. I will give it a test spin > here as well, I have one drive that likes to barf with ncq occasionally. Ok, I've run with this for a few days and finally hit the drive-stops-responding condition yesterday afternoon. Error recovery worked a lot better than before, but eventually went down anyways. But now I got a better look at the error, and it's the drive throwing an ICRC (error 0x80). Very odd. I've never seen this happen with non-NCQ operations, however I've seen it now a few times using NCQ. Any ideas? -- Jens Axboe