From owner-freebsd-bugs Mon Mar 29 8:12:48 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from alms1.fw.att.com (alms1.att.com [192.128.167.146]) by hub.freebsd.org (Postfix) with ESMTP id 9393914FCC for ; Mon, 29 Mar 1999 08:12:39 -0800 (PST) (envelope-from shalunov@att.com) Received: from tuzik.lz.att.com ([135.25.200.84]) by alms1.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id LAA17022; Mon, 29 Mar 1999 11:12:18 -0500 (EST) Received: (from shalunov@localhost) by tuzik.lz.att.com (8.9.2/8.9.2) id LAA27759; Mon, 29 Mar 1999 11:14:27 -0500 (EST) (envelope-from shalunov@att.com) Date: Mon, 29 Mar 1999 11:14:27 -0500 (EST) Message-Id: <199903291614.LAA27759@tuzik.lz.att.com> X-Authentication-Warning: tuzik.lz.att.com: shalunov set sender to shalunov@att.com using -f From: stanislav shalunov To: bde@zeta.org.au Cc: freebsd-bugs@FreeBSD.ORG In-reply-to: <199903270712.SAA17025@godzilla.zeta.org.au> (message from Bruce Evans on Sat, 27 Mar 1999 18:12:17 +1100) Subject: Re: kern/10545: When a fork/exec stress test is run, the machine locks up References: <199903270712.SAA17025@godzilla.zeta.org.au> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Bruce Evans > The kernel virtual address space increase may hide the bug. You should > get the full proc table message or hit some other resource limit in a > controlled way in all configurations. Increase of kernel virtual address space in what config? (I don't follow the development too closely; Was something changed in 4.0? Or you mean my high maxusers value?) Well, I get a lock up anyway (detailed configuration posted earlier, but this is supposed to be a *release* [3.1], a *stable* OS)... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message