Path: utzoo!yunexus!torsqnt!dptcdc!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: jbm@eos.arc.nasa.gov (Jeffrey Mulligan)
Newsgroups: comp.sys.sun
Subject: HELP:  panic: out of kernelmap for devices
Keywords: SunOS
Message-ID: <2762@eos.UUCP>
Date: 8 Mar 89 17:46:18 GMT
Article-I.D.: eos.2762
Sender: usenet@rice.edu
Organization: NASA Ames Research Center, California
Lines: 20
Approved: Sun-Spots@rice.edu
Original-Date: 1 Mar 89 01:58:23 GMT
X-Sun-Spots-Digest: Volume 7, Issue 187, message 13 of 15

System:  4Mb 3/160, os 4.0.1 (in a 2/160 enclosure)

This system already has a number of extra devices on it; today I tried to
add another.  During the probe section of the boot, the system panic'ed.
We ran into this problem before and were able to work around it by
reducing the number of devices in the config file, and by reducing
MAXUSERS (this surprised me; I expected that we would need to *increase*
MAXUSERS, but apparently memory given to process tables, etc., is memory
that is unavailable for kernelmap??).

Has anyone seen this before?  Is there an easy way to tweak param.c?  Is
there a not-so-easy way to tweak vmunix (a la adb)?

Any insight imparted will be greatly appreciated.

jeff

	Jeff Mulligan (jbm@aurora.arc.nasa.gov)
	NASA/Ames Research Ctr., Mail Stop 239-3, Moffet Field CA, 94035
	(415) 694-6290