From owner-freebsd-hackers Wed Dec 3 11:30:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA05710 for hackers-outgoing; Wed, 3 Dec 1997 11:30:03 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from bob.scl.ameslab.gov (bob.scl.ameslab.gov [147.155.137.254]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA05658 for ; Wed, 3 Dec 1997 11:29:58 -0800 (PST) (envelope-from ccsanady@bob.scl.ameslab.gov) Received: from bob.scl.ameslab.gov (localhost [127.0.0.1]) by bob.scl.ameslab.gov (8.8.8/8.8.5) with ESMTP id NAA04658; Wed, 3 Dec 1997 13:29:21 -0600 (CST) Message-Id: <199712031929.NAA04658@bob.scl.ameslab.gov> X-Mailer: exmh version 2.0zeta 7/24/97 To: dg@root.com cc: Jaye Mathisen , hackers@freebsd.org Subject: Re: panic, kmem_malloc: kmem_map too small In-reply-to: Your message of "Tue, 02 Dec 1997 20:03:58 PST." <199712030403.UAA05314@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Dec 1997 13:29:21 -0600 From: Chris Csanady Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>I have a server running a moderately current 2.2.5 (about 3000-4000 >>processes), that is dying with the above listed panic semi-regularly. >> >>The server has 512MB of RAM in it, and does lots of NFS traffic. (keeps a >>100MB half-duplex ethernet running about 40% of capacity. >> >>I have maxusers set to 256 in config, but not sure what other parameters >>may need to be bumped, or more importantly, how they relate to maxusers. >> >>Any tip appreciated. > > In the file /sys/i386/include/vmparam.h, change the parameter VM_KMEM_SIZE >to 64MB. Perhaps this should be made a config option for now? Chris > >-DG > >David Greenman >Core-team/Principal Architect, The FreeBSD Project >