From owner-freebsd-current@FreeBSD.ORG Mon Jul 20 20:13:34 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 C6E07106564A for ; Mon, 20 Jul 2009 20:13:34 +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 8AB6A8FC14 for ; Mon, 20 Jul 2009 20:13:34 +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 85A9423C4FD for ; Mon, 20 Jul 2009 22:13:33 +0200 (CEST) Date: Mon, 20 Jul 2009 22:13:32 +0200 From: Peter Schuller To: freebsd-current@freebsd.org Message-ID: <20090720201332.GA95896@hyperion.scode.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV" Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: 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:13:35 -0000 --HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, Short version: Is there a list of reasons why crashdumps might not work? I have dumpdev on a plain (non-gmirror/non-gstripe/etc) device that is equal to RAM size, but I am not getting a dump for unknown reasons. Long version: so a few months ago I started seeing page faults and/or VM page related panics while bulk-building ports. I was updating CURRENT every month or so a the time and using the bulk building as a test case for ZFS stability issues. While I have stopped seeing deadlocks and such, which is presumably due to the fixes taht have gone in, I instead started seeing these crashes. I never got crash dumps and didn't know why, and was hoping to wait it out a bit. With the advent of 8.0 BETA1 I wanted to give it another shot. I finally realized that having the dumpdev on gstripes/gmirrors was not supported, so I reconfigured my system with a dumpdev on a plain device. I also manually ran the dumpdev command. After I finally made the box crash again (of course the *one* time I had hoped to have proper dumpdev configuration it took several days), I still don't have a dump, and I really don't know why. Is there a checklist of things that need to be correct in order for the kernel to do a dump? Are there certain forms of panic where a dump won't be attempted (such as in this case where it was some a VM page insert or similar)? The problem is that I cannot get a stacktrace interactively since the USB keyboard won't work after a panic, so I really want a crashdump. But since it takes at least a day often, possibly several days, to trigger the crash I'm running out of time if I am to produce some kind of report before 8.0... --=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 --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpkz+sACgkQDNor2+l1i33+bwCeLbD4Ih2cR/vTaUD+6YBzOUoD xJUAoLEKBJXiFrlMmx28FMSEooMMaFCu =YQcc -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--