From owner-freebsd-bugs@FreeBSD.ORG Fri Oct 15 03:30:31 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 510ED16A4CE for ; Fri, 15 Oct 2004 03:30:31 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4037643D1D for ; Fri, 15 Oct 2004 03:30:31 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i9F3UV3C010353 for ; Fri, 15 Oct 2004 03:30:31 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9F3UVHV010352; Fri, 15 Oct 2004 03:30:31 GMT (envelope-from gnats) Date: Fri, 15 Oct 2004 03:30:31 GMT Message-Id: <200410150330.i9F3UVHV010352@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Nikolas Britton 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 Reply-To: Nikolas Britton List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Oct 2004 03:30:31 -0000 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): 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 ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA=xxxxxx Also I take back what I said about freebsd 5.3 being unstable, you guys really know how to build'em, at one time I had the system load (top) for the 1min avg. pegged in the 90s and the 15min. avg. in the 50s - 60s. At the end of my testing I did finally get the system into an unrecoverable state and was forced to reboot it, I was running it with X up and when I try to switch to the console the screen went dead. I blame this one on X. It wasn't a total waste though as I did get to thoroughly burn-in and stress test my new (Used Armada 1750) laptop. So guess this PR is closed unless someone else can crash beastie.