From owner-freebsd-stable  Thu May  1 09:50:55 1997
Return-Path: <owner-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id JAA02222
          for stable-outgoing; Thu, 1 May 1997 09:50:55 -0700 (PDT)
Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA02217
          for <freebsd-stable@freebsd.org>; Thu, 1 May 1997 09:50:52 -0700 (PDT)
Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241])
          by dopey.pathlink.com (8.8.5/8.8.5) with SMTP
	  id JAA11640; Thu, 1 May 1997 09:59:24 -0700 (PDT)
Message-Id: <1.5.4.32.19970501095033.006e6dc8@dopey.pathlink.com>
X-Sender: kachun@dopey.pathlink.com
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 01 May 1997 09:50:33 +0000
To: dg@root.com
From: Kachun Lee <kachun@zippo.com>
Subject: Re: kmem_map full with 2.2beta to 2.2-releng-970422 
Cc: freebsd-stable@freebsd.org
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

At 11:14 PM 4/30/97 -0700, you wrote:
>> [snip]
>
>   That panic is not related to the mbuf clusters problem. The kmem_map full
>panic indicates that the kernel has run out of malloc space. The standard
>default size is 32MB. You can increase it by changing VM_KMEM_SIZE in
>i386/include/vmparam.h.
>
>-DG
>
>David Greenman
>Core-team/Principal Architect, The FreeBSD Project

Thank you! That's exactly what the patient needed.

While I got your attention, the kmem_map full was happening at our NFS
clients, and our NFS servers have quite a lot of these:

  /kernel: nfsd send error 55

They does not seem cause any ill effect. I assume 55=ENOBUFS No buffer space
available. But I thought with the unified VM/Buffer, there are no MAXBUFFER
setting any more. Do you know what parameter I should adjust?

Thank you again.