From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 1 22:59:32 2004 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 A204B16A4F0 for ; Thu, 1 Jul 2004 22:59:32 +0000 (GMT) Received: from smtp.internal.alivewww.com (gp1.alivewww.com [217.158.94.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7257943D58 for ; Thu, 1 Jul 2004 22:59:32 +0000 (GMT) (envelope-from enquiries@alivewww.com) Received: from host-83-146-2-180.bulldogdsl.com ([83.146.2.180]) by smtp.internal.alivewww.com with asmtp (Exim 4.34) id 1BgAVT-0003yK-II; Thu, 01 Jul 2004 23:58:15 +0100 From: Alasdair Lumsden To: Paul Saab In-Reply-To: <20040701215131.GA83112@elvis.mu.org> References: <1088701228.2638.86.camel@host-83-146-2-180.bulldogdsl.com> <20040701215131.GA83112@elvis.mu.org> Content-Type: text/plain Message-Id: <1088722694.2554.48.camel@host-83-146-2-180.bulldogdsl.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6-1mdk Date: Thu, 01 Jul 2004 23:58:15 +0100 Content-Transfer-Encoding: 7bit cc: freebsd-hardware@freebsd.org Subject: Re: 3Ware 8506 Series, 3DM, Upgrading to 9000 Series 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, 01 Jul 2004 22:59:32 -0000 On Thu, 2004-07-01 at 22:51, Paul Saab wrote: > Have you gotten a crashdump after one of these lockups? I've got debugging symbols enabled in the kernel, and dumpdev set in rc.conf - if the box panics then the crash dump information gets written to /var/crash on next boot. However with this particular problem there is no panic. The Raid array simply stops responding. FreeBSD is still running, as timeout messages appear on the console, but it doesn't respond to user input. The only thing you can do is to reboot the box. Since it's a production box we have to simply have it rebooted ASAP, so kernel debugging over serial isn't really an option. If it does it again hopefully I'll be able to extract more useful information from the console history.