home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!mojo.eng.umd.edu!mimsy!jds
- From: jds@cs.umd.edu (James da Silva)
- Newsgroups: comp.unix.bsd
- Subject: Re: NFS patch ==> 'panic: kmem-malloc: kmem-map too small'
- Summary: bump MAX_KMAPENT to 1000 in /sys/vm/vm_map.h
- Message-ID: <59265@mimsy.umd.edu>
- Date: 28 Jul 92 03:39:10 GMT
- References: <l74il5INN20p@neuro.usc.edu>
- Sender: news@mimsy.umd.edu
- Organization: University of Maryland, Department of Computer Science
- Lines: 29
-
- In article <l74il5INN20p@neuro.usc.edu> merlin@neuro.usc.edu (merlin) writes:
- >Well, for reading directories and a few small files the recently posted
- >patch to originate NFS mounts and NFS requests from a privileged port
- >worked quite well.
-
- If you are referring to Rob Fristrom's NFS reserved-port patch, I'm glad to
- hear that it works under 386BSD; we had only tried it under BSDI.
-
- >However, when I mounted a SUN disk on my 386BSD box
- >as follows:
- > [...]
- >and then pressed the system quite hard:
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
- > [...]
- >the kernel panics with 'panic: kmem-malloc: kmem-map too small' after
- >only about half a megabyte is transferred.
- >
- > [...]
- >Does anyone have any insight into or fix for this problem?
-
- I don't think this is related to the NFS patch. Bill posted about this
- problem last week. A kernel table is sized too small for active machines
- with large (12MB or more) memory. Try modifying the value of MAX_KMAPENT
- in /sys/vm/vm_map.h from 500 to 1000. It worked for me.
-
- Jaime
- ............................................................................
- : Stand on my shoulders, : jds@cs.umd.edu : James da Silva
- : not on my toes. : uunet!mimsy!jds : Systems Design & Analysis Group
-