From owner-freebsd-current@FreeBSD.ORG  Thu Jun 24 11:58:50 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9F1FB16A4CE
	for <current@freebsd.org>; Thu, 24 Jun 2004 11:58:50 +0000 (GMT)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3FC1843D39
	for <current@freebsd.org>; Thu, 24 Jun 2004 11:58:50 +0000 (GMT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu
	[152.3.145.30])
	by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i5OBwUqM024543
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 24 Jun 2004 07:58:30 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i5OBwPMU093896;
	Thu, 24 Jun 2004 07:58:25 -0400 (EDT)
	(envelope-from gallatin)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16602.49633.178084.134850@grasshopper.cs.duke.edu>
Date: Thu, 24 Jun 2004 07:58:25 -0400 (EDT)
To: =?iso-8859-1?q?Claus=20Guttesen?= <cguttesen@yahoo.dk>
In-Reply-To: <20040624072910.53703.qmail@web14101.mail.yahoo.com>
References: <20040624072910.53703.qmail@web14101.mail.yahoo.com>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
cc: current@freebsd.org
Subject: Re: unable to make a crashdump
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2004 11:58:50 -0000


Claus Guttesen writes:
 > Hi.
 > 
 > I'm trying to get a crashdump from my kernel when it
 > panics. I have the following in my kernel:
 > 
 > makeoptions     DEBUG=-g
 > options         DDB, DDB_UNATTENDED

You may also want to add  DDB_TRACE.  This gets a stack
trace on console regardless of a crashdump's success.
You may have to jot it down by hand, but in many cases its enough
to characterize the panic enough for a meaningful problem report.

<...>

 > syncing bugger 3795
 > 
 > And then it hangs. Swap is 2 GB, RAM is 1 GB.
 > 


Sync'ing on panic nearly always locks my machines up too.
When I turn this off (sysctl kern.sync_on_panic=0), then
I reliably get dumps.

Is anybody able to reliably get dumps with kern.sync_on_panic enabled?
Maybe it works on SCSI boxes (all of my crashboxes are IDE)...

Drew