From owner-freebsd-hackers Tue Dec 2 19:28:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA01679 for hackers-outgoing; Tue, 2 Dec 1997 19:28:48 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA01657 for ; Tue, 2 Dec 1997 19:28:44 -0800 (PST) (envelope-from mrcpu@cdsnet.net) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.6/8.8.6) with SMTP id TAA09819 for ; Tue, 2 Dec 1997 19:28:42 -0800 (PST) Date: Tue, 2 Dec 1997 19:28:41 -0800 (PST) From: Jaye Mathisen To: hackers@freebsd.org Subject: panic, kmem_malloc: kmem_map too small Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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.