From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 22 19:50:09 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 BAF711065674 for ; Thu, 22 Jan 2009 19:50:09 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id A60148FC12 for ; Thu, 22 Jan 2009 19:50:09 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from OMTA06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by QMTA08.emeryville.ca.mail.comcast.net with comcast id 6cny1b00516AWCUA8jqAlX; Thu, 22 Jan 2009 19:50:10 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA06.emeryville.ca.mail.comcast.net with comcast id 6jpw1b00a4Mx3R28SjpzY0; Thu, 22 Jan 2009 19:50:08 +0000 Message-ID: <4978CDE3.4040700@comcast.net> Date: Thu, 22 Jan 2009 14:49:55 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, Mike Tancsa , scottl@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 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: Thu, 22 Jan 2009 19:50:10 -0000 We have multiple systems using LSILogic PERC4 cards (PERC4e/Si, PERC4/DC, amr driver). After recently upgrading two of them from 6.3 to 7.1, we have begun to see the following errors in our logs during heavy use in both systems: amr0: Too many retries on command 0xffffffff80a4da58. Controller is likely dead amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is likely dead amr0: Too many retries on command 0xffffffff80a497a0. Controller is likely dead amr0: Too many retries on command 0xffffffff80a4eaa8. Controller is likely dead However, the system continues working and the volumes remain accessible. This happens on the PERC4/DC controllers in both systems. Firmware version is 352D. MegaCLI reports no problems. Has anyone else seen these messages? A google search turns up nothing but results in the driver code. Is this something we should be worried about? We won't be moving any other systems to 7.1 until we can clear this up. Thanks! -Steve Polyack