From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 21:27:23 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03113106571B for ; Thu, 22 Jan 2009 21:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9317F8FC1F for ; Thu, 22 Jan 2009 21:27:22 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35]) by QMTA04.westchester.pa.mail.comcast.net with comcast id 6bYp1b0070ldTLk54lTNtH; Thu, 22 Jan 2009 21:27:23 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA04.westchester.pa.mail.comcast.net with comcast id 6lT71b00P4Mx3R23QlTAdt; Thu, 22 Jan 2009 21:27:18 +0000 Message-ID: <4978E4AA.8050601@comcast.net> Date: Thu, 22 Jan 2009 16:27:06 -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> In-Reply-To: <4978E202.70408@samsco.org> 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-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 21:27:24 -0000 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 > We saw this one while backups wrote from an array on the PERC4/DC to a tape drive (on a separate controller). amr1: Too many retries on command 0xffffffff80a6d060. Controller is likely dead The other four which I noted came during writes to the array attached to the PERC4/DC (external Dell PowerVault). I want to say they showed up while writing a 30G junkfile (/dev/random) to the array which we were using to test the tape access; either that, or while we wrote that file out to the tape drive. If it matters, we also use ports/sysutils/linux-megacli2 to periodically check the status of our arrays. It's possible that this happened during one of these long writes/reads. I'm not having any luck reproducing at the moment, but if I come across a reproducible test, I will let you know. Thanks! Steve Polyack