From owner-freebsd-current@FreeBSD.ORG  Thu Mar  4 11:51:14 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 314E316A4CE
	for <current@freebsd.org>; Thu,  4 Mar 2004 11:51:14 -0800 (PST)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E17A643D1F
	for <current@freebsd.org>; Thu,  4 Mar 2004 11:51:13 -0800 (PST)
	(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 i24JpDF6015659
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 4 Mar 2004 14:51:13 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i24Jp7Yr082329;
	Thu, 4 Mar 2004 14:51:07 -0500 (EST)
	(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: <16455.34987.700107.64116@grasshopper.cs.duke.edu>
Date: Thu, 4 Mar 2004 14:51:07 -0500 (EST)
To: Vincent Poy <vince@oahu.WURLDLINK.NET>
In-Reply-To: <20040304093201.X8264-100000@oahu.WURLDLINK.NET>
References: <16455.33748.860265.157572@grasshopper.cs.duke.edu>
	<20040304093201.X8264-100000@oahu.WURLDLINK.NET>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
cc: current@freebsd.org
Subject: Re: -CURRENT kernel panic
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, 04 Mar 2004 19:51:14 -0000


Vincent Poy writes:
 > On Thu, 4 Mar 2004, Andrew Gallatin wrote:
 > 
 > 	Interesting.  I'm still wondering what the VM_KMEM_SIZE_SCALE
 > number represents.

It tries to autoscale the kmem size, so that you don't need to hard
code it.  Hardcoding it could be bad if you change the amount of ram
in the box.


 > >  > > Even after bumping the limits, I'm seeing a repeatable panic when
 > >  > > allocating a large amount of kernel memory ("panic: pmap_enter:
 > >  > > attempted pmap_enter on 4MB page").  See yesterday's message
 > >  > > with that subject for details..
 > >  >
 > >  > 	Just checked the archives and yours seems to jhave more variables
 > >  > than mines from the panic message.
 > >
 > > Can you describe the panic you see?
 > 
 > 	Everything including buildworld doesn't cause the panic except at
 > 4AM at night when I do a dump | restore of the /usr partition which shows
 > just this:
 > 
 > panic: kmem_malloc (4096): kmem_map too small: 377487360 total allocated
 >        at line 341 in file /usr/src/sys/vm/vm_kern.c

According to this, your kmem map size is too small.  (360MB).
What does sysctl vm.kmem_size show?  377487360?

Try bumping it up  via vm.kmem_size=805306368 /boot/loader.conf

Drew