From owner-freebsd-hardware@FreeBSD.ORG Fri Apr 3 12:34:18 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 DC8401065678 for ; Fri, 3 Apr 2009 12:34:18 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 6C9FC8FC28 for ; Fri, 3 Apr 2009 12:34:18 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 67945 invoked by uid 110); 3 Apr 2009 12:34:17 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.113.73.210) by cobra.acceleratedweb.net with SMTP; 3 Apr 2009 12:34:17 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" Date: Fri, 03 Apr 2009 08:34:18 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;3) In-Reply-To: <49D5FFA7.3090408@collaborativefusion.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20090403123418.6C9FC8FC28@mx1.freebsd.org> Subject: Re: [Fwd: 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: Fri, 03 Apr 2009 12:34:19 -0000 >> It appears this has not been fixed in 7.1-p4 I've been waiting to upgrade due >> to this but was forced after latest root exploit was found recently. Upon MySQL >> upgrade, running mysql_upgrade which upgrades and checks all the tables, >> I got 2 of these messages while a large ,1.4G, mysql table was being dumped >> to array so it could be repaired. I don't know what to make of this error and >> are not sure if it could be safely ignored. >> >> amr0: Too many retries on command 0xc71ceaa8. Controller is likely dead >> amr0: Too many retries on command 0xc71cdce8. Controller is likely dead >> >> Thank you in advance! >> >> -Simon >> >> >We still see these as well. I've also been ensured that these are >harmless messages. As far as I can tell from my own investigation, the >behavior has not changed other than the addition of tracking of how many >retries there have been when submitting commands to the controller. >When the controller mailbox is "busy", the driver must wait before >submitting a command. If the driver has to retry 1000 times twice >within one second, it logs the messages you are seeing. This logging >was simply not present before 7.1. >As I've said and been told, the message is harmless if your machine is >still responding. Well, I have several machines with same megaraid controller and I'm only seeing this on one of them thus far. The load on this one is not grossly different from that of others, so now I wonder why I only get it on this machine. Thanks for your input! -Simon