From owner-freebsd-hardware@FreeBSD.ORG Fri Apr 3 07:56: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 79C1D106564A for ; Fri, 3 Apr 2009 07:56:56 +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 3721F8FC14 for ; Fri, 3 Apr 2009 07:56:56 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 22479 invoked by uid 110); 3 Apr 2009 07:30:14 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.113.73.210) by cobra.acceleratedweb.net with SMTP; 3 Apr 2009 07:30:14 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" Date: Fri, 03 Apr 2009 03:30:15 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;3) In-Reply-To: <497E252C.2010502@comcast.net> MIME-Version: 1.0 Message-Id: <20090403075656.3721F8FC14@mx1.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Fri, 03 Apr 2009 07:56:56 -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 On Mon, 26 Jan 2009 16:03:40 -0500, Steve Polyack wrote: >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. >_______________________________________________ >freebsd-stable@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org"