From owner-freebsd-current@FreeBSD.ORG  Sat Nov 15 22:45:08 2003
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 65EA016A4CE
	for <current@freebsd.org>; Sat, 15 Nov 2003 22:45:08 -0800 (PST)
Received: from smtp.mho.com (smtp.mho.net [64.58.4.6])
	by mx1.FreeBSD.org (Postfix) with SMTP id 65D5D43F85
	for <current@freebsd.org>; Sat, 15 Nov 2003 22:45:07 -0800 (PST)
	(envelope-from scottl@freebsd.org)
Received: (qmail 93685 invoked by uid 1002); 16 Nov 2003 06:45:06 -0000
Received: from unknown (HELO freebsd.org) (64.58.1.252)
  by smtp.mho.net with SMTP; 16 Nov 2003 06:45:06 -0000
Message-ID: <3FB71CC3.9060408@freebsd.org>
Date: Sat, 15 Nov 2003 23:44:19 -0700
From: Scott Long <scottl@freebsd.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031103
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Claus Guttesen <cguttesen@yahoo.dk>
References: <20031115233048.83366.qmail@web14104.mail.yahoo.com>
In-Reply-To: <20031115233048.83366.qmail@web14104.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: FreeBSD current, apache and php4 woes
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: Sun, 16 Nov 2003 06:45:08 -0000

Claus Guttesen wrote:
> Hi.
> 
> 
>>>panic: kmem_malloc(4096): kmem_map too small:
>>>275251200 total allocated cpuid = 0; lapic.id =
>>>00000000
>>
>>man tuning
>>
>>You probably need to reset maxusers to 128 or so
>>manually since the
>>auto-tuning is doing the wrong thing. Although this
>>is usually a problem
>>on 4GB systems.
>>
> 
> 
> I'll try to adjust it manually.
> 
> 
>>You aren't running any wierd nmbclusters/nmbufs
>>values, are you?
>>
> 
> 
> Just a straight install and custom-kernel reg. NIC and
> SCSI.
> 
> Claus
> 

You'll either want to raise the size of the kmem_map pool
(this is where kernel malloc and UMA get their allocations),
or decrease the maximum number of vnodes allowed (vnodes get
allocated out of the kmem_map and are likely depleating it
in your case).  I run into this constantly; we worked on
fixing it last spring by making the maxvnodes auto-tune itself
better, but that seems to no longer be enough.  Add one of
the two lines to /boot/loader.conf:

kern.vn.kmem.size=350000000

or

kern.maxvnodes=150000

The first one is probably the better choice for you since
the very nature of what you are doing demands that you touch
a lot of vnodes.

Scott