From owner-freebsd-current@FreeBSD.ORG  Sat Jan 31 01:08:57 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 11D431065670
	for <freebsd-current@FreeBSD.ORG>; Sat, 31 Jan 2009 01:08:57 +0000 (UTC)
	(envelope-from dylan@dylex.net)
Received: from datura.dylex.net (datura.dylex.net [216.27.141.80])
	by mx1.freebsd.org (Postfix) with ESMTP id D74128FC19
	for <freebsd-current@FreeBSD.ORG>; Sat, 31 Jan 2009 01:08:56 +0000 (UTC)
	(envelope-from dylan@dylex.net)
Received: from dylan by datura.dylex.net with local (Exim 4.69)
	(envelope-from <dylan@dylex.net>) id 1LT4Lv-00025b-Pi
	for freebsd-current@FreeBSD.ORG; Fri, 30 Jan 2009 20:08:55 -0500
Date: Fri, 30 Jan 2009 20:08:55 -0500
From: Dylan Alex Simon <dylan@dylex.net>
To: freebsd-current@FreeBSD.ORG
Message-ID: <20090131010855.GA7991@datura.dylex.net>
References: <8cb6106e0901200641x4b0bda9ag31e6f059f13035a7@mail.gmail.com>
	<200901201829.n0KITE8V072323@lurza.secnetix.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200901201829.n0KITE8V072323@lurza.secnetix.de>
Jabber-ID: dylan@dylex.net
Cc: 
Subject: Re: SATA DMA errors on second ICH10 bus
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 31 Jan 2009 01:08:57 -0000

> That advice seems to be particularly valuable given the
> current firmware problems that particular Seagate disks
> are exhibiting.

I've confirmed with Seagate and others that the firmware these disks already
have (CC1F) is not affected by the firmware problems.  The instability (as
described in kern/130726) continues with a kernel from today.  I've traced it
down to exclusively and reliably being caused by access to disks on multiple
channels simultaneously (access to any pair of disks on the same channel works
fine).  If anyone has any suggestions or any other data I should collect let
me know as I will have to put these machines into production shortly (without
freebsd unfortunately).

:-Dylan