Date: Fri, 17 Dec 1999 03:18:11 -0500 From: scott <scott@chronis.pobox.com> To: David Scheidt <dscheidt@enteract.com> Subject: Re: system freeze: how to debug? Message-ID: <19991217031811.A15782@chronis.pobox.com> In-Reply-To: <Pine.NEB.3.96.991216230745.11417A-100000@shell-1.enteract.com> References: <19991216235723.A9224@chronis.pobox.com> <Pine.NEB.3.96.991216230745.11417A-100000@shell-1.enteract.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 16, 1999 at 11:15:27PM -0600, David Scheidt wrote: > On Thu, 16 Dec 1999, scott wrote: > > > I have a 3.3 release system that keeps freezing when stressed. It is > > running postfix, and that's all. When it freezes, there is no kernel > > dump, no console message, no log messages. It simply will not respond > > to anything, console or otherwise, except to recycle the power. > > > > How do I get this system to be more informative about what is causing > > this problem? > > Put > options DDB > in your kernel config, config -g your kernel, make and install it, and wait > for it to hang. When it does, use CTRL-ALT-ESC to break into the debugger. > Type trace <return>, copy down the output, then do panic <return> continue > <return>. > > Save the crashdump, and post the stack trace. There are instructions on > this in section 22 of the handbook < > http://www.freebsd.org/handbook/kerneldebug.html > or your local copy. You > probably should read that first. Read that, didn't fully understand the saving of the crash dump, I keep getting magic number mismatch errors. anyway, 2 different things happened: first go, it paniced by itself, and here's the trace from that: db> trace Debugger(e01e9787) at Debugger+0x37 panic (c01f8b56, cb2cff58, c019ddf5, 1c0f000, 7a0f000) at panic+0x74 pmap_copy_page (1c0f000, 7a0f000, cb2af620) at pmap_copy_page+0x21 vm_fault (cb2c0e80, 28141000, 3, 8, cb2af620) at vm_fault+0x721 trap_pfault (cb2cffbc, 1, 281416f0) at trap_pfault+0xaa trap (8120027, bfbf0027, 0, 8129000, bfbfd5ec) at trap+0x1aa calltrap() at calltrap+0x1c --- trap 0xc, eip=0x80662ac esp=0xbfbfd5e0 ebp=0xbfbfd5ec --- The second time I got it to crash, it wouldn't even respond to CTRL-ALT-ESC, it just hung :( Any clues deciphering the trace? scott > > Regards, > > David Scheidt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991217031811.A15782>