Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758909AbXI3Rno (ORCPT ); Sun, 30 Sep 2007 13:43:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757932AbXI3Rnh (ORCPT ); Sun, 30 Sep 2007 13:43:37 -0400 Received: from rtr.ca ([76.10.145.34]:1032 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757862AbXI3Rng (ORCPT ); Sun, 30 Sep 2007 13:43:36 -0400 Message-ID: <46FFE047.7030102@rtr.ca> Date: Sun, 30 Sep 2007 13:43:35 -0400 From: Mark Lord User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Tejun Heo Cc: Mark Lord , Jeff Garzik , Paolo Ornati , Alan Cox , Linux Kernel Mailing List , linux-ide@vger.kernel.org Subject: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS References: <20070930160548.235be972@localhost> <20070930152908.1f58d39d@the-village.bc.nu> <20070930164610.20818867@localhost> <46FFBB2D.6060004@garzik.org> <46FFDC5A.7070509@rtr.ca> <46FFDCE5.4060900@gmail.com> In-Reply-To: <46FFDCE5.4060900@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1243 Lines: 32 Tejun Heo wrote: > Mark Lord wrote: >> Jeff Garzik wrote: >>> Paolo Ornati wrote: >>>> I have this problem only with XFS, and even with XFS it goes away >>>> mounting with "nobarrier"... >>> This last is an interesting datapoint. >>> >>> I wonder if libata has a generic problem with NCQ + FLUSH CACHE. >> Yeah, that's pretty suspicious. Prior to issuing a FLUSH_CACHE op, >> one must first drain all outstanding NCQ commands (and not issue new ones). >> >> I'm sure the code must *try* to do that, but perhaps there's a bug in >> there? >> Or just another drive bug? > > If there was such a bug, the aborted commands list should contain both > FPDMA commands and FLUSH commands. I don't think command filtering > itself is broken. Possibly another quirky firmware but it's strange > that this is the only Seagate drive showing this problem. Yeah, that's the strange bit. Surely someone at SuSE must have a drive like that, which they could set up with XFS and reproduce the same results? ?? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/