From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 3 15:36:54 2005 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 609D916A4CE for ; Thu, 3 Feb 2005 15:36:54 +0000 (GMT) Received: from server2.troikatek.com (server2.troikatek.com [66.135.32.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD3B243D39 for ; Thu, 3 Feb 2005 15:36:51 +0000 (GMT) (envelope-from aheyn@jmsent.com) Received: (qmail 27367 invoked from network); 3 Feb 2005 16:31:11 -0000 Received: from ns.jmsent.com (HELO AREILLPC) (66.9.27.146) by server2.troikatek.com with SMTP; 3 Feb 2005 16:31:10 -0000 From: "Andrew Heyn" To: Date: Thu, 3 Feb 2005 10:37:17 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <20050202214303.P76517@sasami.jurai.net> Subject: RE: Compaq Smart Array 4200 controller question X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Feb 2005 15:36:54 -0000 Hi, Now that its confirmed that it's a firmware crash... What can I do about this? Could it be the driver? or the drives giving an unexpected response? Can HP/Compaq help me? Am I SOL? I hope it's not the last thing, but I guess it is. Thanks, Andrew -----Original Message----- From: Matthew N. Dodd [mailto:mdodd@FreeBSD.ORG] Sent: Wednesday, February 02, 2005 6:45 PM To: Andrew Heyn Cc: freebsd-hardware@FreeBSD.ORG Subject: RE: Compaq Smart Array 4200 controller question On Wed, 2 Feb 2005, Andrew Heyn wrote: > I got a 6-CURRENT kernel so I could show you the messages it creates > when it times out. Unfortunately, it doesn't seem very useful, but here > it is: > > ida0: ida_timeout() qactive 1 > ida0: IDA_INTERRUPTS > ida0: R_CMD_FIFO: 00000000 > R_DONE_FIFO:00000000 > R_INT_MASK: 00000000 > R_STATUS: 00000000 > R_INT_PENDING Yep, thats what a firmware lockup looks like. You can confirm this by looking at the pretty lights on the card and comparing the pre and post crash state. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00