From owner-freebsd-bugs@FreeBSD.ORG Sat Oct 8 17:50:19 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org 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 DBB2016A41F for ; Sat, 8 Oct 2005 17:50:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8F6A43D45 for ; Sat, 8 Oct 2005 17:50:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j98HoJQR087761 for ; Sat, 8 Oct 2005 17:50:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j98HoJxe087760; Sat, 8 Oct 2005 17:50:19 GMT (envelope-from gnats) Date: Sat, 8 Oct 2005 17:50:19 GMT Message-Id: <200510081750.j98HoJxe087760@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Robert Watson Cc: Subject: Re: kern/87094: 5.4 system with SMP and IPFW crashes under load (mbuf underrun) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Watson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Oct 2005 17:50:20 -0000 The following reply was made to PR kern/87094; it has been noted by GNATS. From: Robert Watson To: Chris Ulrich Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/87094: 5.4 system with SMP and IPFW crashes under load (mbuf underrun) Date: Sat, 8 Oct 2005 18:47:42 +0100 (BST) On Fri, 7 Oct 2005, Chris Ulrich wrote: > Run SMP and IPFW and natd on a 5.4 i386 system and run iperf between one > interface and the other (server outside the nat interface). > > After a minute or so, netstat -m will show something like: > 4294266316 mbufs in use > 4294737989/25600 mbuf clusters in use (current/max) > 3560445 KBytes allocated to network > 201 calls to protocol drain routines > > After another period of time, the system will eventually reboot. The > behavior is not related to load or firewall rule changes. FYI, statistics errors in the mbuf allocator in 5.x are probably unrelated to the reboot, and occurs due to races in statistics gathering. 6.x corrects this problem, and I'm considering a merge of the changes to the 5.x branch following 6.0-RELEASE and some additional in-field testing. The reboot is, however, concerning. Do you get a panic and reboot, or just a reboot? In particular, if you compile in the kernel debugger, does it drop to the debugger at some point, or reboot? Could you try a 5-STABLE kernel and see if that works better? There have been a number of synchronization fixes that have not yet been released as errata, which might affect this. Thanks, Robert N M Watson