From owner-freebsd-current@FreeBSD.ORG  Tue Mar 16 08:01:16 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 A673916A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 16 Mar 2004 08:01:16 -0800 (PST)
Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 65E8443D2F
	for <freebsd-current@freebsd.org>;
	Tue, 16 Mar 2004 08:01:16 -0800 (PST)	(envelope-from sven@dmv.com)
Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46])
	i2GG1EW1030468;	Tue, 16 Mar 2004 11:01:14 -0500 (EST)
	(envelope-from sven@dmv.com)
From: Sven Willenberger <sven@dmv.com>
To: David Malone <dwmalone@maths.tcd.ie>
In-Reply-To: <20040316152013.GA82071@walton.maths.tcd.ie>
References: <1079446098.23554.49.camel@lanshark.dmv.com>
	 <20040316152013.GA82071@walton.maths.tcd.ie>
Content-Type: text/plain
Message-Id: <1079452815.23554.69.camel@lanshark.dmv.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Tue, 16 Mar 2004 11:00:30 -0500
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.39
cc: freebsd-current@freebsd.org
Subject: Re: kmem_map too small, revisited
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: Tue, 16 Mar 2004 16:01:16 -0000

On Tue, 2004-03-16 at 10:20, David Malone wrote:
> On Tue, Mar 16, 2004 at 09:08:18AM -0500, Sven Willenberger wrote:
> > Where should I begin to better diagnose what exactly is going on here? 
> 
> I can suggest two ways. The first is to record the output of "vmstat
> -m" every 5 minutes from when the machine boots until it dies. If
> something is consuming all your kernel memory, this may tell us
> what subsystem it is.

I will get that started on one of the boxes ASAP.

> Another possibility is to add the DDB and DDB_UNATTENDED options
> to your kernel and record the backtraces when the machine reboots.
> 
Do I need to define dumpdev in rc.conf as well? Also, after the machine
reboots after the crash, I can access the kernel dump with DDB by
dropping to debug mode? (via the sysctl or keyboard per the handbook and
assuming the DDB_UNATTENDED preserves the information upon reboot into
multi-user)

Sven