From owner-freebsd-questions@FreeBSD.ORG Wed Jun 1 07:26:11 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDE6D16A41C for ; Wed, 1 Jun 2005 07:26:11 +0000 (GMT) (envelope-from dennyboy@cableone.net) Received: from S1.cableone.net (smtp1.cableone.net [24.116.0.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A8D943D53 for ; Wed, 1 Jun 2005 07:26:11 +0000 (GMT) (envelope-from dennyboy@cableone.net) Received: from dualman.cableone.net (unverified [24.119.190.179]) by S1.cableone.net (CableOne SMTP Service S1) with ESMTP id 21618546 for ; Wed, 01 Jun 2005 00:26:31 -0700 Date: Wed, 1 Jun 2005 02:25:56 -0500 (CDT) From: Denny White To: freebsd-questions@freebsd.org Message-ID: <20050531215354.F613@dualman.cableone.net> X-GPG-PUBLIC_KEY: http://wwwkeys.nl.pgp.net X-GPG-FINGERPRINT: D0A9 AD44 1F10 E09E OE67 EC25 CB44 F2E5 1644 E79A MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-IP-stats: Incoming Last 3, First 27, in=36, out=0, spam=0 X-External-IP: 24.119.190.179 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Subject: System Panics and Core Dump help X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jun 2005 07:26:11 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just trying to get a heads up if I'm going about this in the right way, if I've understood what I've read and applied, outlined below. I read an article at Onlamp on how to prepare for system panics and core dumps. Article here: http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html?page=2 After rebuilding my kernel with the options KDB options DDB makeoptions DEBUG=-g I copied kernel.debug to /var/crash/kernel.debug.date for future use. I added the following below to /etc/rc.conf, leaving the dump directory at its default /var/crash in /etc/defaults/rc.conf: dumpdev="/dev/amrd0s1b" (this is my swap partition) savecore_flags="-z" (added flag for compression) Now, in /var/log/messages, I get: savecore: unable to open bounds file, using 0 savecore: no dumps found Am I right in assuming that the system's doing exactly what it's supposed to do? That is, checking for a dump when booting, not finding any, reporting as much, and proceeding booting as usual? I assumed that, even though the message is a bit misleading to a relative newbie like myself, after reading the following at another web site: - -------------------------------------------- PROBLEMS AND REMEDIES No Dump Was Saved Cause: The system may have shut down successfully. Remedy: No dump is expected. Core dumps are only created for abnormal shutdowns. - ------------------------------------------- Thanks for any help, advice and clarification. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCnWMRy0Ty5RZE55oRAoIdAKDLBzHivK8U0f+sagqNMcmPG3YF4wCdETzG noqTYEnxXHRrfcNtRzA4oYA= =VBh0 -----END PGP SIGNATURE-----