From owner-freebsd-current@FreeBSD.ORG  Sat Feb  7 02:37:51 2004
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 63C6216A4CE
	for <current@freebsd.org>; Sat,  7 Feb 2004 02:37:51 -0800 (PST)
Received: from paladin.fortunaty.net (fortunaty.net [217.160.129.175])
	by mx1.FreeBSD.org (Postfix) with SMTP id 9BC5A43D2F
	for <current@freebsd.org>; Sat,  7 Feb 2004 02:37:50 -0800 (PST)
	(envelope-from ah@paladin.fortunaty.net)
Received: (qmail 2500 invoked by uid 501); 7 Feb 2004 10:37:49 -0000
Date: 7 Feb 2004 10:37:49 -0000
Message-ID: <20040207103749.2499.qmail@paladin.fortunaty.net>
User-Agent: Emai/0.0.2p1
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
References: <20040109085601.20479.qmail@paladin.fortunaty.net>
	(andy-freebsd@splashground.de's message of "9 Jan 2004 08:56:01 -0000")
	<xzp65fl1oow.fsf@dwp.des.no>
In-Reply-To: <xzp65fl1oow.fsf@dwp.des.no>
From: Andreas Hauser <andy-freebsd@splashground.de>
To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no>
X-License: BSD
X-Addicted: yeah
cc: current@freebsd.org
Subject: Re: Problems with Promise FastTrak
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: Sat, 07 Feb 2004 10:37:51 -0000

des wrote @ Fri, 09 Jan 2004 10:00:47 +0100:
> andy-freebsd@splashground.de writes:
> > [...]
> > ad4: WARNING - WRITE_DMA recovered from missing interrupt
> > ad4: WARNING - READ_DMA recovered from missing interrupt
> 
> You should have included this in your original post...

FWIW, a 2nd Feb -CURRENT still exposed this.
Though mounting /dev/ad4 instead of /dev/ar0 got me
back performance and those messages disappeared.

Andy