kern/75755: kmem_malloc(45056): kmem_map too small: 335540224 total allocated

[Michael Haro]

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

From: Michael Haro <mharo at FreeBSD.org>
To: Kris Kennaway <kris at obsecurity.org>
Cc: FreeBSD-gnats-submit at FreeBSD.org
Subject: Re: kern/75755: kmem_malloc(45056): kmem_map too small: 335540224 total allocated
Date: Tue, 4 Jan 2005 22:09:52 -0800

 How would I figure out what this value should be set to without just
 increasing it and waiting for it to run out of KMEM space and panicing
 again?
 
 I'm not following the system workload thing you stated.  This server
 mostly just nfs client, sendmail, clamav, mimedefang and seti and only
 receives about 300 messages per day.
 
 top currently says:
 Mem: 311M Active, 1532M Inact, 118M Wired, 67M Cache, 112M Buf, 1735M Free
 Swap: 4096M Total, 4096M Free
 
 How do I find out the amount of kmem being used?
 
 Michael
 
 On Tue, Jan 04, 2005 at 04:46:22PM -0800, Kris Kennaway wrote:
 > On Mon, Jan 03, 2005 at 10:03:48AM -0800, Michael Haro wrote:
 > 
 > > Not sure. This is the first occurance.  System was up for over 40 days.
 > > 
 > > I did see a few other PRs with similar issues, but none of them had a
 > > solution that all the PRs agreed on.
 > 
 > As you noted, this is a duplicate of other PRs and should be closed.
 > The problem is that your system workload caused the system to run out
 > of KVM (kernel memory).  The solution is to increase the amount of KVM:
 > 
 > > Unknown.  One PR said
 > > options VM_KMEM_SIZE_MAX=419430400
 > > decreased KMEM space.  Another comment said that it increased it and thus
 > > was incorrect.
 > 
 > I'm confused about what you're claiming here.  This option allocates
 > 400M of KVM (default is 320, so this is an increase and will provide
 > your kernel with a bit more memory with which to work).  If 400 is
 > still too low, try a larger value.
 > 
 > Kris