From owner-freebsd-current@FreeBSD.ORG Mon Jul 20 20:43:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADF031065723; Mon, 20 Jul 2009 20:43:25 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from hyperion.scode.org (cl-1361.ams-04.nl.sixxs.net [IPv6:2001:960:2:550::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6E3368FC0A; Mon, 20 Jul 2009 20:43:25 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from hyperion.scode.org (hyperion.scode.org [85.17.42.115]) by hyperion.scode.org (Postfix) with ESMTPS id 766BF23C4FD; Mon, 20 Jul 2009 22:43:24 +0200 (CEST) Date: Mon, 20 Jul 2009 22:43:23 +0200 From: Peter Schuller To: Doug Barton Message-ID: <20090720204323.GA96793@hyperion.scode.org> References: <20090720201332.GA95896@hyperion.scode.org> <4A64D203.1030908@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <4A64D203.1030908@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@freebsd.org Subject: Re: Getting crashdumps to work (trying to submit crash report) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2009 20:43:26 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > First question, why do you think that you do not have a dump? Second Nothing in /var/crash after reboot. I checked with 'savecore' manually but of course I realize now that this was pretty useless since by that time swap would have been re-enabled. So really, savecore may have given some kind of message on boot - I'm not entirely sure to what extent I checked the messages on boot after the panic. So I'm not sure what might have been printed during boot this time around. Hmm. Is there a good way to simulate a panic so that I can quicky iterate tweaks until I can be sure I get a dump? > question, do you have anything in the console log when you boot that > indicates a problem with savecore? What happens if you run Possibly but I would probably have missed it this time; previously I had the "no suitable dump device" on setup, presumably because swap was a gmirror. > '/etc/rc.d/savecore start' ? Finally, I'm assuming throughout that > your /var/crash directory is on a disk/partition with enough space for > a dump? Plenty of space (> 100 gig), though it's on ZFS in case that matters (but since this is done by savecore rather than special kernel stuff I was sort of assuming that would not be a problem). --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpk1usACgkQDNor2+l1i339tgCgn/Nk0YdGReYw0WhRW+XxbU1u av4AoJbiFHcyALWdjZEXrpRxcNXqqpPj =ONXe -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0--