Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757750AbXI2BGU (ORCPT ); Fri, 28 Sep 2007 21:06:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755840AbXI2BGJ (ORCPT ); Fri, 28 Sep 2007 21:06:09 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:60795 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755698AbXI2BGH (ORCPT ); Fri, 28 Sep 2007 21:06:07 -0400 Message-ID: <46FDA4F3.7050205@pobox.com> Date: Fri, 28 Sep 2007 21:05:55 -0400 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: Alan Cox CC: Mark Lord , Tejun Heo , Andrew Morton , michal.k.k.piotrowski@gmail.com, bryan@arbores.ca, linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: [PATCH] libata drain fifo on stuck DRQ HSM violation References: <46CFA08E.6090604@arbores.ca> <6bffcb0e0708261610g10d9c59ck5789fac6feca9f42@mail.gmail.com> <46DBCB6C.8080206@gmail.com> <20070905095327.6277d054.akpm@linux-foundation.org> <46DEE617.4050004@rtr.ca> <46E0A253.7060803@gmail.com> <46E154DE.2060602@rtr.ca> <46FB563A.80108@gmail.com> <20070927193701.6230d77f@the-village.bc.nu> <46FC3D7D.90009@gmail.com> <46FC3FDD.5060201@pobox.com> <46FC423C.2050206@gmail.com> <46FC7B72.2030103@rtr.ca> <20070928112735.264733ad@the-village.bc.nu> In-Reply-To: <20070928112735.264733ad@the-village.bc.nu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.1.9 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 761 Lines: 29 Alan Cox wrote: >> Drain up to 512 words from host/bridge FIFO on stuck DRQ HSM violation, >> rather than just getting stuck there forever. > > Why 512 words ? Though I have queued Mark's patch to be applied, my gut feeling would lean towards a single DRQ block, rather than 512. >> ata_altstatus(ap); >> - ata_chk_status(ap); >> + ata_drain_fifo(ap, qc); > > ap->ops->cleanup(); > > might be wiser If someone needs that, they can override the error handler with their own. No need for a new op. Jeff - 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/