Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Jan 2009 12:52:15 -0700
From:      Scott Long <scottl@samsco.org>
To:        Steve Polyack <korvus@comcast.net>
Cc:        "scottl@freebsd.org" <scottl@freebsd.org>, Mike Tancsa <freebsd-stable@freebsd.org>, "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org>
Subject:   Re: amr driver issues in 7.1-RELEASE
Message-ID:  <55889FEE-0F42-4D40-8E90-447A2AFF70A6@samsco.org>
In-Reply-To: <4978CDE3.4040700@comcast.net>
References:  <4978CDE3.4040700@comcast.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <korvus@comcast.net> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55889FEE-0F42-4D40-8E90-447A2AFF70A6>