Date: Wed, 10 Aug 2011 18:24:28 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Steven Hartland <killing@multiplay.co.uk> Cc: freebsd-stable@FreeBSD.org Subject: Re: debugging frequent kernel panics on 8.2-RELEASE Message-ID: <4E42A2AC.3030604@FreeBSD.org> In-Reply-To: <47F0D04ADF034695BC8B0AC166553371@multiplay.co.uk> References: <47F0D04ADF034695BC8B0AC166553371@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
on 10/08/2011 17:22 Steven Hartland said the following: > The kernel is compiled with:- > options KDB # Kernel debugger related code > options KDB_TRACE # Print a stack trace for a panic You also have to provide an actual debugger backend like built-in DDB or a stub for remote GDB to get online debugging. No guarantees that that would help you to get the debugging information, but without that the chances are even slimmer. You may also try this patch and see if it provides any improvements for post-panic environment (dumping etc): http://people.freebsd.org/~avg/stop_scheduler_on_panic.8.x.diff It might also be a good idea to at least capture a screenshot of whatever information you get on console when the panic happens. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E42A2AC.3030604>