Date: Thu, 9 Dec 2004 12:41:10 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: crashdumps not working Message-ID: <20041209021109.GH92212@wantadilla.lemis.com> In-Reply-To: <Pine.NEB.3.96L.1041208111915.98791C-100000@fledge.watson.org> References: <200412072154.42853.michaelnottebrock@gmx.net> <Pine.NEB.3.96L.1041208111915.98791C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--HUY/6dRnBRT+g9H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wednesday, 8 December 2004 at 11:20:34 +0000, Robert Watson wrote: > > On Tue, 7 Dec 2004, Michael Nottebrock wrote: > >> I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers >> a panic, no crashdump is taken although dumps are enabled. What could be >> causing this? > > If you drop to the debugger by using the debug.kdb.enter sysctl, and > do "call doadump", followed by a reset, does a dump get generated > successfully? I.e., are they completely broken on your system, or > is this somehow a property of the particular hang you're seeing. > (Do the above with caution and in a situation where you don't mind > fscking, needless to say). FWIW, I've found that the only way to dump a -CURRENT system in the last six months or so has been to 'call doadump'. There are a number of other problems, including getting gdb over firewire to work at all, but I won't find time to look at them for the next few weeks. Greg -- See complete headers for address and phone numbers. --HUY/6dRnBRT+g9H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBt7Q9IubykFB6QiMRAqq8AJ9FN7BjMZOxTVn4VKDgZYgFV/YeOACfaks+ Ufv6MRVPo4tmaVAwcLb0A90= =EycB -----END PGP SIGNATURE----- --HUY/6dRnBRT+g9H1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041209021109.GH92212>