From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 1 23:39:55 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 1D92F16A4CE for ; Thu, 1 Jul 2004 23:39:55 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id F392B43D1D for ; Thu, 1 Jul 2004 23:39:54 +0000 (GMT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id C2A4A5C825; Thu, 1 Jul 2004 16:38:11 -0700 (PDT) Date: Thu, 1 Jul 2004 16:38:11 -0700 From: Paul Saab To: Alasdair Lumsden Message-ID: <20040701233811.GA89536@elvis.mu.org> References: <1088701228.2638.86.camel@host-83-146-2-180.bulldogdsl.com> <20040701215131.GA83112@elvis.mu.org> <1088722694.2554.48.camel@host-83-146-2-180.bulldogdsl.com> <20040701230015.GA87635@elvis.mu.org> <1088724938.2879.17.camel@host-83-146-2-180.bulldogdsl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1088724938.2879.17.camel@host-83-146-2-180.bulldogdsl.com> User-Agent: Mutt/1.4.2.1i 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 23:39:55 -0000 Alasdair Lumsden (enquiries@alivewww.com) wrote: > On Fri, 2004-07-02 at 00:00, Paul Saab wrote: > > There is a debugger where you can force a panic on a hang. That's what > > DDB/BREAK_TO_DEBUGGER/ALT_BREAK_TO_DEBUGGER are for. > > Thank you - unfortunately, I'm unsure as to what use a DDB prompt would > be to me. > > I'm not a driver/kernel developer, nor do I know C, nor can the box > spare the downtime in the event of this situation occurring again. > > Further more, since the box continues to run, and isn't a true "hang" in > the sense of the word, thousands of instructions will have run after the > true cause of the problem, making debugging even harder (presumably - as > I say I'm no developer!) No.. it will tell us where it is hung in the driver. Please read http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html This will tell you how to get into DDB and when you get the ddb prompt, type trace and tell us where it is hung at.