Date: Thu, 1 Jul 2004 16:38:11 -0700 From: Paul Saab <ps@mu.org> To: Alasdair Lumsden <enquiries@alivewww.com> Cc: freebsd-hardware@freebsd.org Subject: Re: 3Ware 8506 Series, 3DM, Upgrading to 9000 Series Message-ID: <20040701233811.GA89536@elvis.mu.org> In-Reply-To: <1088724938.2879.17.camel@host-83-146-2-180.bulldogdsl.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040701233811.GA89536>