Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!news.ksu.ksu.edu!news.physics.uiowa.edu!math.ohio-state.edu!howland.reston.ans.net!ix.netcom.com!news3.noc.netcom.net!zdc!usenet
From: kachun@pathlink.com
Subject: kmem_map full
X-Newsreader: NetRunner News Reader
Sender: usenet@snews.zippo.com (Http Group)
Nntp-Posting-Host: dvl-1.pathlink.com
Organization: Zippo
Message-ID: <DLCLL6.K7J@snews.zippo.com>
Date: Wed, 17 Jan 1996 23:07:54 GMT
Lines: 18
We are running a P100/128M/FreeBSD 2.1/News Server, which has a very
heavy load - 300+ connections constantly. About once a week, it panics with
kmem_map full. For another reason, back in the 2.0 day, I have tried to change
the:
VM_KMEM_SIZE in /sys/i386/include/vmparam.h to 64*1024*1024
already, and the 2.0 kernel did not even start. I believe the boot process panic right after
displaying the size of the main memory. My questions are:
1. With FreeBSD 2.1, can I just change VM_KMEM_SIZE to a large value?
2. Will that help the kmem_map full panic?
3. If not, can the size of kmem_map be increased to solve the above panic
problem? Or why should I do?
Thank you