Date: Wed, 16 Jul 2008 10:58:53 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: freebsd-usb@freebsd.org Subject: Re: Crash when booting with umass device connected Message-ID: <3a142e750807160158x150f521fv696845d77d6e3c58@mail.gmail.com> In-Reply-To: <91DD32EA4C3672A46D423E44@utd65257.utdallas.edu> References: <3632806C83D31F1A23DE0F0A@utd65257.utdallas.edu> <3a142e750807150219j5a619135x19edba16e6590c21@mail.gmail.com> <3a142e750807150223w6f264048wd9e13ae8846b593c@mail.gmail.com> <91DD32EA4C3672A46D423E44@utd65257.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/15/08, Paul Schmehl <pschmehl_lists@tx.rr.com> wrote: > --On Tuesday, July 15, 2008 11:23:09 +0200 "Paul B. Mahol" > <onemda@gmail.com> > wrote: >> >> Look in Developers handbook for more info >> /usr/share/doc/en/books/developers-handbook/index.html >> >> I think that textdumps are MFCed to STABLE. >> Textdumps provide easy way for gathering backtraces. > > The problem is, I'm not getting dump files. (And dumpdev is set to AUTO - > the > default.) Savecore runs, but there's nothing to put in /var/crash. > First, do you see kdb prompt when system panics? If not then you will need to recompile kernel with various debug stuff: KDB, DDB, GDB, DEBUG=-g ... Second do you have line with sw in /etc/fstab. If not, it is possible to set dump device manually. You should have following lines in /etc/rc.conf: ddb_enable="YES" ddb_config="/etc/ddb.conf" But this one is required only if you want that textdumps are taken automaticaly after system crash. Exploring ddb(4) is also usefull.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750807160158x150f521fv696845d77d6e3c58>