From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 11:19:05 2004 Return-Path: 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 98CBB16A4CE; Wed, 29 Dec 2004 11:19:05 +0000 (GMT) Received: from schubert.byrnehq.com (dsl-33-12.dsl.netsource.ie [213.79.33.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2BD643D49; Wed, 29 Dec 2004 11:19:04 +0000 (GMT) (envelope-from freebsd@byrnehq.com) Received: from localhost (mauer.directski.com. [212.147.140.194]) by schubert.byrnehq.com (8.13.1/8.13.1) with ESMTP id iBTBJ6jo015952; Wed, 29 Dec 2004 11:19:07 GMT (envelope-from freebsd@byrnehq.com) Date: Wed, 29 Dec 2004 11:18:55 +0000 From: Tony Byrne Organization: ByrneHQ X-Priority: 3 (Normal) Message-ID: <187186864.20041229111855@byrnehq.com> To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ByrneHQ-SA-Hits: 1.455 X-Scanned-By: MIMEDefang 2.49 on 192.168.10.254 cc: msmith@freebsd.org Subject: MegaRAID 'Bad Slot' Kernel message and crash. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Tony Byrne List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 11:19:05 -0000 Folks, We have a 4.10-STABLE production server which has an Intel SRCU42X RAID controller installed: amr0: mem 0xfe580000-0xfe5fffff,0xfbef0000-0xfbefffff irq 22 at device 0.0 on pci4 amr0: 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. -- Tony Byrne