From owner-freebsd-current  Wed Jan  7 14:04:31 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA16543
          for current-outgoing; Wed, 7 Jan 1998 14:04:31 -0800 (PST)
          (envelope-from owner-freebsd-current)
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 OAA16521
          for <freebsd-current@FreeBSD.ORG>; Wed, 7 Jan 1998 14:04:17 -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 OAA16705;
	Wed, 7 Jan 1998 14:03:19 -0800 (PST)
Message-Id: <199801072203.OAA16705@implode.root.com>
To: shimon@simon-shapiro.org
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Panic: kmem_malloc: kmem_map too small 
In-reply-to: Your message of "Wed, 07 Jan 1998 09:36:53 PST."
             <XFMail.980107093653.shimon@simon-shapiro.org> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 07 Jan 1998 14:03:19 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I receive that mainly under SMP, but looking at vm/vm_kern.c I do not see

   Sounds like you need to increase the kmem_map size - you're running out
of malloc space. This can be done by changing VM_KMEM_SIZE in
/sys/i386/include/vmparam.h. The problem might indicate that you have a
very large system, a mistuned system, or perhaps could even indicate a
kernel memory leak. I suggest that you carefully analyze the output of
"vmstat -m" to determine where it's all going.

-DG

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