Date: Thu, 24 Jun 2004 07:58:25 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: =?iso-8859-1?q?Claus=20Guttesen?= <cguttesen@yahoo.dk> Cc: current@freebsd.org Subject: Re: unable to make a crashdump Message-ID: <16602.49633.178084.134850@grasshopper.cs.duke.edu> In-Reply-To: <20040624072910.53703.qmail@web14101.mail.yahoo.com> References: <20040624072910.53703.qmail@web14101.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Claus Guttesen writes: > Hi. > > I'm trying to get a crashdump from my kernel when it > panics. I have the following in my kernel: > > makeoptions DEBUG=-g > options DDB, DDB_UNATTENDED You may also want to add DDB_TRACE. This gets a stack trace on console regardless of a crashdump's success. You may have to jot it down by hand, but in many cases its enough to characterize the panic enough for a meaningful problem report. <...> > syncing bugger 3795 > > And then it hangs. Swap is 2 GB, RAM is 1 GB. > Sync'ing on panic nearly always locks my machines up too. When I turn this off (sysctl kern.sync_on_panic=0), then I reliably get dumps. Is anybody able to reliably get dumps with kern.sync_on_panic enabled? Maybe it works on SCSI boxes (all of my crashboxes are IDE)... Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16602.49633.178084.134850>