On Mon, Sep 24, 2007 at 06:36:53PM +0200, P.U.Kruppa wrote:
That's the DDB prompt: from there you need to either get a backtrace or,
more usefully, generate a crash dump.
See
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html
for details.
To generate a crash dump that you can later use with kgdb, type "panic"
at the db> prompt. Then, read
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html
to find out how to obtain a backtrace that can help diagnose the fault.
If using the "panic" command doesn't generate a crash dump, you could
also do some diagnostics at the db> prompt by using commands such as
"trace" to get a stack trace, but unless you're connected over serial
you won't be able to get a copy of the output so it's better to see if
you can generate a crash dump first.
--
Bruce
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"