From owner-freebsd-isp  Mon Sep 23 08:54:08 1996
Return-Path: owner-isp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA17751
          for isp-outgoing; Mon, 23 Sep 1996 08:54:08 -0700 (PDT)
Received: from saguaro.flyingfox.com (saguaro.flyingfox.com [204.188.109.253])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA17727
          for <freebsd-isp@FreeBSD.ORG>; Mon, 23 Sep 1996 08:53:58 -0700 (PDT)
Received: (from jas@localhost) by saguaro.flyingfox.com (8.6.12/8.6.10) id IAA12960; Mon, 23 Sep 1996 08:52:19 -0700
Date: Mon, 23 Sep 1996 08:52:19 -0700
From: Jim Shankland <jas@flyingfox.COM>
Message-Id: <199609231552.IAA12960@saguaro.flyingfox.com>
To: freebsd-isp@FreeBSD.ORG, robseco@wizard.teksupport.net.au
Subject: Re:  mb_map full
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Every 'once in a blue moon' ( 3-6 months) one of our servers
> crashes with the following error:
> 
> Sep 23 02:24:26 wizard kernel: mb_map full
> 
> Before anyone says anything, I know I need to upgrade this
> machine to 2.1.5.  However, aside from this problem it runs
> flawlessly and the upgrade is planned for next month. It is
> currently running FreeBSD 2.0-RELEASE GENERIC kernel.

Also `panic("kmem_malloc: kmem_map too small")' caused by, e.g.,
a fork() when running with high network activity (mbufs come
out of the kmem_map) and little physical memory.  Granted, when
you're out of memory, you're out of memory, but returning
EAGAIN instead of panicking would seem to be more in the spirit
of graceful degradation :-).

This was 2.1.0-RELEASE; haven't seen this yet under 2.1.5, and
haven't yet taken a close look to see if it's been fixed; but
the kmem_malloc code, at least, looks about the same as under
2.1.0.

Jim Shankland
Flying Fox Computer Systems, Inc.