From owner-freebsd-current@FreeBSD.ORG Fri Apr 27 01:43:20 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 389EE16A40E for ; Fri, 27 Apr 2007 01:43:20 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 22E2C13C45E for ; Fri, 27 Apr 2007 01:43:20 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C444C1A4DA5; Thu, 26 Apr 2007 18:43:46 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6AACF513F4; Thu, 26 Apr 2007 21:43:17 -0400 (EDT) Date: Thu, 26 Apr 2007 21:43:17 -0400 From: Kris Kennaway To: Steve Kargl Message-ID: <20070427014317.GA17436@xor.obsecurity.org> References: <20070426204602.GA81382@keltia.freenix.fr> <20070427012401.GZ2445@obelix.dsto.defence.gov.au> <20070427013742.GA51877@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <20070427013742.GA51877@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org Subject: Re: Panic on boot. How do I get a kernel dump. 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: Fri, 27 Apr 2007 01:43:20 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 26, 2007 at 06:37:42PM -0700, Steve Kargl wrote: > On Fri, Apr 27, 2007 at 09:24:02AM +0800, Wilkinson, Alex wrote: > > 0n Thu, Apr 26, 2007 at 03:35:15PM -0700, Tom Cumming wrote:=20 > >=20 > >>The problem is not getting it to panic, the problem is getting it to sa= ve > >>core after the panic. I can find no way to configure the dump device be= fore > >>I boot, only after the OS is up. This means a panic during boot will not > >>dump core because the dump device is not configured. > >=20 > > Boot off of a good kernel and: > >=20 > > # boot -s > > # fsck -p > > # mount /var > > # savecore /kernel.broken /var/crash > >=20 > > -aW > >=20 >=20 > Re-read the text that you quoted. Tom doesn't have=20 > dumpdev set, so there is no core for savecore to > retrieve. ISTR, that one could set dumpdev in the > loader. At the loader prompt, do=20 >=20 > set dumpdev=3D"/dev/ad0s2b" =20 I don't think this has existed for many years (it was removed during GEOM development). Kris --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGMVU1Wry0BWjoQKURAgmrAJ4yYw4JEGed4g5PfBJOyMgxnd/olACg6qIT ciCTvwqLlAayMRjDxvLt9cQ= =rVXV -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c--