From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 26 21:03:56 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29C2110656C6 for ; Mon, 26 Jan 2009 21:03:56 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id C0BE98FC1E for ; Mon, 26 Jan 2009 21:03:55 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA09.westchester.pa.mail.comcast.net with comcast id 8BRg1b0030ldTLk59M3wZw; Mon, 26 Jan 2009 21:03:56 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA04.westchester.pa.mail.comcast.net with comcast id 8M3h1b00a4Mx3R23QM3knJ; Mon, 26 Jan 2009 21:03:54 +0000 Message-ID: <497E252C.2010502@comcast.net> Date: Mon, 26 Jan 2009 16:03:40 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Scott Long References: <4978CDE3.4040700@comcast.net> <4978E202.70408@samsco.org> <4978E4AA.8050601@comcast.net> In-Reply-To: <4978E4AA.8050601@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Tancsa , freebsd-hardware@freebsd.org Subject: Re: amr driver issues in 7.1-RELEASE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2009 21:03:57 -0000 Steve Polyack wrote: > Scott Long wrote: >> The fix for this that I was thinking of is already in 7.1. There >> might still be a driver bug, but I'm leaning more towards the >> controller simply being busy. Do you have a reproducible test case >> that I could >> try? >> >> Scott >> So far, I have not been able to reliably reproduce this. It pops up every now and then during our backups, which at the moment aren't that disk intensive. I'll let you know if I come across anything else.