From owner-freebsd-stable@FreeBSD.ORG  Wed Dec  8 11:23:01 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 40BEB16A4CE
	for <freebsd-stable@freebsd.org>;
	Wed,  8 Dec 2004 11:23:01 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CF4C443D1F
	for <freebsd-stable@freebsd.org>;
	Wed,  8 Dec 2004 11:23:00 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB8BKYJV099087;
	Wed, 8 Dec 2004 06:20:34 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)iB8BKYiF099084;
	Wed, 8 Dec 2004 11:20:34 GMT	(envelope-from robert@fledge.watson.org)
Date: Wed, 8 Dec 2004 11:20:34 +0000 (GMT)
From: Robert Watson <rwatson@freebsd.org>
X-Sender: robert@fledge.watson.org
To: Michael Nottebrock <michaelnottebrock@gmx.net>
In-Reply-To: <200412072154.42853.michaelnottebrock@gmx.net>
Message-ID: <Pine.NEB.3.96L.1041208111915.98791C-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-stable@freebsd.org
Subject: Re: crashdumps not working
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2004 11:23:01 -0000


On Tue, 7 Dec 2004, Michael Nottebrock wrote:

> I recently enabled SW_WATCHDOG in my kernel, but when watchdog triggers
> a panic, no crashdump is taken although dumps are enabled. What could be
> causing this? 

If you drop to the debugger by using the debug.kdb.enter sysctl, and do
"call doadump", followed by a reset, does a dump get generated
successfully?  I.e., are they completely broken on your system, or is this
somehow a property of the particular hang you're seeing.  (Do the above
with caution and in a situation where you don't mind fscking, needless to
say).

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Principal Research Scientist, McAfee Research