From owner-cvs-src@FreeBSD.ORG  Mon Apr 25 22:11:44 2005
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 214FC16A4CE; Mon, 25 Apr 2005 22:11:44 +0000 (GMT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0A00643D55; Mon, 25 Apr 2005 22:11:44 +0000 (GMT)
	(envelope-from scottl@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.13.1/8.13.1) with ESMTP id j3PMBhjI041437;
	Mon, 25 Apr 2005 22:11:43 GMT
	(envelope-from scottl@repoman.freebsd.org)
Received: (from scottl@localhost)
	by repoman.freebsd.org (8.13.1/8.13.1/Submit) id j3PMBheb041436;
	Mon, 25 Apr 2005 22:11:43 GMT
	(envelope-from scottl)
Message-Id: <200504252211.j3PMBheb041436@repoman.freebsd.org>
From: Scott Long <scottl@FreeBSD.org>
Date: Mon, 25 Apr 2005 22:11:43 +0000 (UTC)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/sys/dev/esp ncr53c9x.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2005 22:11:44 -0000

scottl      2005-04-25 22:11:43 UTC

  FreeBSD src repository

  Modified files:
    sys/dev/esp          ncr53c9x.c 
  Log:
  Apply a torniquet to the problem of the drive unexpectedly disconnecting
  during a data phase.  Before, we would try to recover the autosense, but
  the DMA engine would still be active with interrupted transfer, and we'd
  quickly spiral out of control and cause massive data corruption.  For now,
  just reset the chip and cancel everything.  The better solution is to
  cancel the DMA operation, but there is no clear way to do that right now.
  The data corruption problem is severe enough to warrant this fix in the
  interim.  Thanks to Kris Kenneway to sacrificing countless filesystems to
  this bug.
  
  MFC After: 3 days
  
  Revision  Changes    Path
  1.11      +9 -1      src/sys/dev/esp/ncr53c9x.c