From owner-freebsd-current@FreeBSD.ORG  Tue Mar 16 12:19:23 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 80B4116A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 16 Mar 2004 12:19:23 -0800 (PST)
Received: from smtp-gw-cl-d.dmv.com (smtp-gw-cl-d.dmv.com [216.240.97.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2B1FB43D45
	for <freebsd-current@freebsd.org>;
	Tue, 16 Mar 2004 12:19:23 -0800 (PST)	(envelope-from sven@dmv.com)
Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46])
	i2GKJCRv018539	for <freebsd-current@freebsd.org>;
	Tue, 16 Mar 2004 15:19:12 -0500 (EST)	(envelope-from sven@dmv.com)
From: Sven Willenberger <sven@dmv.com>
To: freebsd-current@freebsd.org
In-Reply-To: <1079452815.23554.69.camel@lanshark.dmv.com>
References: <1079446098.23554.49.camel@lanshark.dmv.com>
	 <20040316152013.GA82071@walton.maths.tcd.ie>
	 <1079452815.23554.69.camel@lanshark.dmv.com>
Content-Type: text/plain
Message-Id: <1079468317.23554.98.camel@lanshark.dmv.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Tue, 16 Mar 2004 15:18:37 -0500
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.39
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 20:19:23 -0000

On Tue, 2004-03-16 at 11:00, Sven Willenberger wrote:
> 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.
> 

In comparing the vmstat -m output from a machine that has recently
rebooted and one that has been up for a few weeks (which is usually
about the max before the panic/reboot) I did notice an abnormally high
(in comparison) value of cred:

> uptime
 3:11PM  up 26 days,  2:28, 1 user, load averages: 0.00, 0.00, 0.00
> sysctl kern.malloc
kern.malloc:
        Type  InUse MemUse HighUse Requests  Size(s)
.
.
.
         cred1445117180640K 180641K  9036491  128
.
.
.

versus:
> uptime
 3:13PM  up 7 days,  1:38, 1 user, load averages: 1.49, 1.02, 0.74
> sysctl kern.malloc
kern.malloc:
        Type  InUse MemUse HighUse Requests  Size(s)
.
.
.
         cred   326    41K     49K  6666888  128
.
.
.

What exactly is "cred" and how would I go about finding out a) if that
first set of numbers is completely out of line and b) what is causing it
to go so high if it is in fact out of whack.

Sven