From owner-freebsd-current@FreeBSD.ORG  Thu Apr 29 22:18:41 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id B1960106564A
	for <freebsd-current@freebsd.org>; Thu, 29 Apr 2010 22:18:41 +0000 (UTC)
	(envelope-from james-freebsd-current@jrv.org)
Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106])
	by mx1.freebsd.org (Postfix) with ESMTP id 5D42D8FC18
	for <freebsd-current@freebsd.org>; Thu, 29 Apr 2010 22:18:41 +0000 (UTC)
Received: from kremvax.housenet.jrv (kremvax.housenet.jrv [192.168.3.124])
	by mail.jrv.org (8.14.3/8.14.3) with ESMTP id o3TMIcfO063911;
	Thu, 29 Apr 2010 17:18:38 -0500 (CDT)
	(envelope-from james-freebsd-current@jrv.org)
Authentication-Results: mail.jrv.org; domainkeys=pass (testing)
	header.from=james-freebsd-current@jrv.org
DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject:
	references:in-reply-to:content-type:content-transfer-encoding;
	b=JeH51lHKELin1IvTWWrsG36ZXFXyaTylglvNfiTKG2UFAmg2hV5e6oX2cKMvgm6WC
	hnC2GX+XQZAoIW2YoiuQ4Z6/bvb+8WC/ljBm5gJPLaADfsFqBvZhRbijKct3rn6TIpL
	tPSuLE5OZvEq7t1/7djxnvsh5qknR+MEK2PJIkY=
Message-ID: <4BDA05BE.8090807@jrv.org>
Date: Thu, 29 Apr 2010 17:18:38 -0500
From: "James R. Van Artsdalen" <james-freebsd-current@jrv.org>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Scott Long <scottl@samsco.org>
References: <4BD8F7FA.2080103@jrv.org>	<20100429145334.GB62822@roberto-al.eurocontrol.fr>	<n2m2e027be01004290844k51dd6060q77375e894ff4efc4@mail.gmail.com>
	<E79134A9-2174-4905-85A6-ADAEC0EA7D66@samsco.org>
In-Reply-To: <E79134A9-2174-4905-85A6-ADAEC0EA7D66@samsco.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Tom Evans <tevans.uk@googlemail.com>,
	Ollivier Robert <roberto@keltia.freenix.fr>, freebsd-current@freebsd.org
Subject: Re: kmem_map too small: 3832475648 total allocated
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 29 Apr 2010 22:18:41 -0000

Scott Long wrote:
>
> I'm sorry, but I find it absolutely absurd that any filesystem has to wire down 2GB of RAM, and that the solution to panics is buy more

The only thing buying more RAM is likely to do is make the memory leak
behind this harder to reproduce.  Likewise increasing kernel tunables.

It may only be a short-term leak, i.e. something that would be recovered
normally.

Does FreeBSD have a kernel debug facility for this?  Is there a way to
look at a kernel dump file and identify by caller who allocated space?