From owner-freebsd-current@FreeBSD.ORG  Tue Sep  2 21:09:29 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B72FD16A4BF; Tue,  2 Sep 2003 21:09:29 -0700 (PDT)
Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com
	[12.233.57.131])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0611243FF5; Tue,  2 Sep 2003 21:09:29 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Received: from HAL9000.homeunix.com (localhost [127.0.0.1])
	by HAL9000.homeunix.com (8.12.9/8.12.9) with ESMTP id h8349RG7003011;
	Tue, 2 Sep 2003 21:09:27 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Received: (from das@localhost)
	by HAL9000.homeunix.com (8.12.9/8.12.9/Submit) id h8349RST003010;
	Tue, 2 Sep 2003 21:09:27 -0700 (PDT)
	(envelope-from das@FreeBSD.ORG)
Date: Tue, 2 Sep 2003 21:09:27 -0700
From: David Schultz <das@FreeBSD.ORG>
To: sos@FreeBSD.ORG
Message-ID: <20030903040927.GA2960@HAL9000.homeunix.com>
Mail-Followup-To: sos@FreeBSD.ORG, current@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
cc: current@FreeBSD.ORG
Subject: ATAng panic: ata_dmasetup: transfer active on this device!
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2003 04:09:29 -0000

I have a machine that panics reliably within ten minutes of
operation with ATAng.  It subsequently locks up, so I can't obtain
a dump, and I get a small amount of random filesystem corruption
upon rebooting.  Everything was fine with ATAog.

I don't have a serial cable handy at the moment, but the DDB
traceback looks like this:

	panic: ata_dmasetup: transfer active on this device!
	cpuid = 0
	[...]
	panic [...]
	ata_dmastart(d3075000,4000,0,101) [...]
	ata_pci_dmastart(d3075000,4000,0,20) [...]
	ata_transaction [...]
	ata_start [...]
	ata_completed [...]
	taskq_run [...]
	[...]

I can attach a serial cable and get some more information if
necessary.  The dual-processor machine in question has one 200GB
UATA 100 drive attached to ad0 and two 36GB SATA drives on ad4 and
ad6, mirrored through ccd(4).