From owner-freebsd-stable Mon Feb 1 11:37:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05028 for freebsd-stable-outgoing; Mon, 1 Feb 1999 11:37:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dfw-ix5.ix.netcom.com (dfw-ix5.ix.netcom.com [206.214.98.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05021 for ; Mon, 1 Feb 1999 11:37:28 -0800 (PST) (envelope-from phate1@ix.netcom.com) Received: (from smap@localhost) by dfw-ix5.ix.netcom.com (8.8.4/8.8.4) id NAA05392 for ; Mon, 1 Feb 1999 13:37:20 -0600 (CST) Received: from unknown(209.67.1.10) by dfw-ix5.ix.netcom.com via smap (V1.3) id rma005286; Mon Feb 1 13:36:54 1999 Message-ID: <36B60321.AA21E91@ix.netcom.com> Date: Mon, 01 Feb 1999 14:40:17 -0500 From: Mike Organization: Integration Soft. X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Can't set maxusers to 512. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, FreeBSD 3.0 stable Pentium 400 Xeon x2 (SMP) 512MB Ram Recently moved from 3.0R to 3.0S, had trouble at first, but finally got it working. The problem is, I can't set maxusers to 512, this is going to be a very a heavy serving box, and I would need the extra open files, file descriptors, etc.. The problem is, after the box boots up, when i login via the console (and httpd, ftp starts, etc) kernel panics: panic: pmap_new_proc: u_map allocation failed I can set it to 256, 384 without any problems I remember I couldnt set this to 512 as well on my earlier box which had only 384MB Ram, (kmem_alloc() panicked right after detecting the memory) This panic is after the boot process is finished.. Can someone elucidate me if me not be able to set maxusers to 512 is a memory issue, or do I have add another option to kernel config?? Thanks in advance! Yev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message