From owner-freebsd-bugs@FreeBSD.ORG Fri Oct 15 05:39:14 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EB0816A4CE for ; Fri, 15 Oct 2004 05:39:14 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id B444943D2F for ; Fri, 15 Oct 2004 05:39:13 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.12.10) with ESMTP id i9F5dHQ2067165; Fri, 15 Oct 2004 01:39:17 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.12.10/Submit) id i9F5dHgY067164; Fri, 15 Oct 2004 01:39:17 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Fri, 15 Oct 2004 01:39:17 -0400 From: David Schultz To: Nikolas Britton Message-ID: <20041015053917.GA67052@VARK.MIT.EDU> Mail-Followup-To: Nikolas Britton , freebsd-bugs@FreeBSD.ORG References: <200410150330.i9F3UVHV010352@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410150330.i9F3UVHV010352@freefall.freebsd.org> cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/72680: (Kernel Panic) FreeBSD 5.3 Does not survive fork bombing X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 05:39:14 -0000 On Fri, Oct 15, 2004, Nikolas Britton wrote: > The following reply was made to PR kern/72680; it has been noted by GNATS. > > From: Nikolas Britton > To: freebsd-gnats-submit@FreeBSD.org, freebsd@nbritton.org > Cc: > Subject: Re: kern/72680: (Kernel Panic) FreeBSD 5.3 Does not survive fork > bombing > Date: Thu, 14 Oct 2004 22:26:18 -0500 > > Sorry to have wasted your time but after 3 hours of fork bombing and > trying everthing else under the sun, I could not get FreeBSD to panic > with the new debug kernel. I guess it was just a fluke or I was doing > the wrong thing at the right time (when it paniced the first time it was > in the middle of a portupgrade -arR, X session, etc.). here is a list of > the many error messages I receviced (if it helps any): No worries. In the future, though, it would help if you could provide more information in problem reports. The best thing to do (short of submitting a patch to fix the bug) is to provide the panic message, backtrace, anything noteworthy about your kernel config, and steps to reproduce the problem. If the problem is hard to reproduce, we minimally need a panic message or something that will tell us *where* something went wrong. > maxproc limit exceeded > kern.ipc.maxpipekva exceeded > swap_pager: out of swap space > swap_pager_getswapspace > Pipe call failed: bad file descriptor > kern.maxfiles limit exceeded > Can't open /dev/null: Too meny open files in the system > Connot fork: Resource temporarily unavailable Given that you've hit just about every *other* resource limit in the system, my guess is that you also ran out of KVA or reached the limit on the kmem_map size. If this is a real problem, you should set administrative limits to ensure that you do not run out of swap space and then, if needed, adjust some of the other limits as well.