From owner-freebsd-stable@FreeBSD.ORG Thu Jan 22 20:28:20 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 4F4BC106567C; Thu, 22 Jan 2009 20:28:20 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id C0C938FC19; Thu, 22 Jan 2009 20:28:19 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from [10.92.110.42] (mobile-032-158-094-188.mycingular.net [32.158.94.188] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id n0MJqP11053693; Thu, 22 Jan 2009 12:52:35 -0700 (MST) (envelope-from scottl@samsco.org) References: <4978CDE3.4040700@comcast.net> Message-Id: <55889FEE-0F42-4D40-8E90-447A2AFF70A6@samsco.org> From: Scott Long To: Steve Polyack In-Reply-To: <4978CDE3.4040700@comcast.net> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (5G77) Mime-Version: 1.0 (iPhone Mail 5G77) Date: Thu, 22 Jan 2009 12:52:15 -0700 X-Spam-Status: No, score=-2.6 required=3.8 tests=BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "scottl@freebsd.org" , 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 20:28:21 -0000 I might have a fix for this, let me check and get back to you. Scott Sent from my iPhone On Jan 22, 2009, at 12:49 PM, Steve Polyack wrote: > 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