From owner-freebsd-stable@FreeBSD.ORG  Wed Dec 29 14:47:35 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0EFF716A4CE; Wed, 29 Dec 2004 14:47:35 +0000 (GMT)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9D7EA43D5F; Wed, 29 Dec 2004 14:47:34 +0000 (GMT)
	(envelope-from scottl@freebsd.org)
Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11])
	(authenticated bits=0)
	by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iBTEoAYn016817;
	Wed, 29 Dec 2004 07:50:11 -0700 (MST)
	(envelope-from scottl@freebsd.org)
Message-ID: <41D2C32C.7090803@freebsd.org>
Date: Wed, 29 Dec 2004 07:46:04 -0700
From: Scott Long <scottl@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tony Byrne <freebsd@byrnehq.com>
References: <187186864.20041229111855@byrnehq.com>
In-Reply-To: <187186864.20041229111855@byrnehq.com>
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org
cc: freebsd-stable@freebsd.org
cc: msmith@freebsd.org
Subject: Re: MegaRAID 'Bad Slot' Kernel message and crash.
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Dec 2004 14:47:35 -0000

Tony Byrne wrote:
> Folks,
> 
> We have a 4.10-STABLE production server which has an Intel SRCU42X
> RAID controller installed:
> 
> amr0: <LSILogic MegaRAID> mem 0xfe580000-0xfe5fffff,0xfbef0000-0xfbefffff irq 22 at device 0.0 on pci4
> amr0: <LSILogic Intel(R) RAID Controller SRCU42X> Firmware 411M, BIOS H404, 128MB RAM
> 
> The server crashed yesterday in the small hours of the morning and
> when we arrived on site to reboot it, there was a "bad slot" kernel
> message on the console, which places the RAID controller in the frame.
> 
> The amr driver man page says that this message is indicative of a firmware or
> hardware problem with the controller, but we are not convinced.  We
> experienced the same message and lockups daily during stress testing of the
> box under FreeBSD 5.3 and this ultimately forced us to 'downgrade'
> to 4.10 for production.  The box had been rock solid under 4.10 for a
> number of weeks before yesterday's crash.
> 
> Could this indicate a bug in the driver, or at least in its support
> for our re-badged RAID controller?  Has anyone else had problems with
> the amr driver with the same card?
> 
> Many thanks,
> 
> Regards,
> 
> Tony.
> 

I've been seeing this problem recently too.  I believe that there is
some sort of timing bug/race in the driver, but I haven't been able to
figure it out yet.  It also seems to be related to panic from the block
layer that point to commands being completed twice.  To be clear with
your observations, are you saying that 4.10-RELEASE is behaving the same
or differently than 4.10-STABLE?

Scott