Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:5208 comp.os.386bsd.bugs:1442 Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!rz.uni-karlsruhe.de!subnet.sub.net!ppcnet.ppc.sub.org!rumtifsl.ruessel.sub.org!strix.cluster.sub.org!ura From: ura@strix.cluster.sub.org (Ulf Andrick) Subject: Re: panic: kmem_map too small Organization: Nocturnal Unix System in Kaiserslautern, Germany Followup-To: comp.os.386bsd.questions,comp.os.386bsd.bugs References: <CDAMD0.5F@strix.cluster.sub.org> Message-ID: <CDJxpy.7pK@strix.cluster.sub.org> X-Newsreader: TIN [version 1.1 PL8] Date: Sat, 18 Sep 1993 13:34:44 GMT Lines: 28 In <CDAMD0.5F@strix.cluster.sub.org> Ulf Andrick (ura@strix.cluster.sub.org) writes: : Until some days ago, I had a relatively stable system. It was 386bsd 0.1 : with an older patch kit (I have become reluctant to abuse university : facilities for getting new software for my private machine nowadays). : It would run for more than 10 days until rebooted for getting rid of : some hanging process or so. : Then, I upgraded from 8 MB RAM to 16 MB. Now, the system reboots : inadvertedly several times a day. As it says `kmem_map too small' I : increased MAX_KMAPENT in /sys/vm/vm_map.h from 1000, as it was after : patch00002, to 2000, even 5000. The only difference seems to be that : there's no RAM image dumped any more. According to the responses I got, the problem was encountered before and would go away with patch kit 2.3/2.4 (I wasn't able to locate a complete patch kit 2.4). Under NetBSD or FreeBSD, the problem is unknown and it might be better to get one of those. This information is very helpful for me, as I can be confident now, that the patch kits bring a solution to this problem and that I have no reason to suspect my hardware. Thanks to Adam David, Stefan Behrens, Mike Murphy, and Dan Andersson for their responses. -- Ulf Andrick ura@strix.cluster.sub.org