From owner-freebsd-hackers  Tue Dec  2 20:00:45 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA04200
          for hackers-outgoing; Tue, 2 Dec 1997 20:00:45 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA04190
          for <hackers@FreeBSD.ORG>; Tue, 2 Dec 1997 20:00:41 -0800 (PST)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id UAA05314;
	Tue, 2 Dec 1997 20:03:58 -0800 (PST)
Message-Id: <199712030403.UAA05314@implode.root.com>
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: hackers@FreeBSD.ORG
Subject: Re: panic, kmem_malloc: kmem_map too small 
In-reply-to: Your message of "Tue, 02 Dec 1997 19:28:41 PST."
             <Pine.NEB.3.95.971202192616.4251r-100000@mail.cdsnet.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 02 Dec 1997 20:03:58 -0800
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I have a server running a moderately current 2.2.5 (about 3000-4000
>processes), that is dying with the above listed panic semi-regularly.
>
>The server has 512MB of RAM in it, and does lots of NFS traffic. (keeps a
>100MB half-duplex ethernet running about 40% of capacity.
>
>I have maxusers set to 256 in config, but not sure what other parameters
>may need to be bumped, or more importantly, how they relate to maxusers.
>
>Any tip appreciated.

   In the file /sys/i386/include/vmparam.h, change the parameter VM_KMEM_SIZE
to 64MB.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project