misc/75510: panic: kmem_malloc(4096): kmem_map too small

[Kris Kennaway]

The following reply was made to PR misc/75510; it has been noted by GNATS.

From: Kris Kennaway <kris at obsecurity.org>
To: Rob Swindell <rob at synchro.net>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: misc/75510: panic: kmem_malloc(4096): kmem_map too small
Date: Mon, 27 Dec 2004 11:17:44 -0800

 On Sun, Dec 26, 2004 at 11:11:03AM +0000, Rob Swindell wrote:
 > 
 > >Number:         75510
 > >Category:       misc
 > >Synopsis:       panic: kmem_malloc(4096): kmem_map too small
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       high
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sun Dec 26 11:20:17 GMT 2004
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Rob Swindell
 > >Release:        5.3-RELEASE
 > >Organization:
 > Synchronet
 > >Environment:
 > FreeBSD devil.synchro.net 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Sat Dec 25 02:42:54 PST 2004     root at devil.synchro.net:/usr/src/sys/i386/compile/MYKERNEL  i386
 >   
 > >Description:
 > When running a multi-threaded server application (http://www.synchro.net), accessing configuration and data files on an smbfs-mounted volume, after 4-8 hours, I get the following panic (routinely):
 > 
 > panic:  kmem_malloc(4096): kmem_map too small: 40898560 total allocated
 > 
 > I've seen another PR related to a panic like this one, but it was in
 > relation to a system with 4GB+ of RAM. This particular system only
 > has 128MB of RAM. Here is a current "top" output at the time of one
 > of the panics:
 
 The same explanation applies; your application is causing your kernel
 to run out of KVM.  Since you only have 128MB you don't have much room
 to increase the defaults as described in other PRs and emails about
 this topic, so the best solution is to add more RAM.
 
 Kris