From owner-freebsd-bugs Thu Mar 25 17:20:23 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8AD9315180 for ; Thu, 25 Mar 1999 17:20:20 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.2/8.9.2) id RAA79439; Thu, 25 Mar 1999 17:20:02 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Thu, 25 Mar 1999 17:20:02 -0800 (PST) Message-Id: <199903260120.RAA79439@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/10545: When a fork/exec stress test is run, the machine locks up Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/10545; it has been noted by GNATS. From: Sheldon Hearn To: shalunov@lynxhub.lz.att.com Cc: freebsd-gnats-submit@freebsd.org Subject: Re: kern/10545: When a fork/exec stress test is run, the machine locks up Date: Fri, 26 Mar 1999 03:17:40 +0200 I've tried your stress test on my 4.0-CURRENT box (built today) and I don't get a lock-up. Instead, I get thousands of these after the first few seconds: Mar 26 03:15:15 axl /kernel: proc: table i Mar 26 03:15:15 axl /kernel: proc: table is full Mar 26 03:15:15 axl last message repeated 43 times Mar 26 03:15:15 axl /kernel: p Mar 26 03:15:15 axl /kernel: proc: table is full [...] I woulda thought this to be expected behaviour. Have you tried your test on a CURRENT box? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message