From owner-freebsd-net@FreeBSD.ORG Sun Nov 26 06:43:55 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6BF1116A407 for ; Sun, 26 Nov 2006 06:43:55 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2-3.pacific.net.au [61.8.2.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 907A443D5D for ; Sun, 26 Nov 2006 06:43:02 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout2.pacific.net.au (Postfix) with ESMTP id AA0176E31A; Sun, 26 Nov 2006 17:43:52 +1100 (EST) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (Postfix) with ESMTP id 6A05B8C03; Sun, 26 Nov 2006 17:43:52 +1100 (EST) Date: Sun, 26 Nov 2006 17:43:45 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Max Laier In-Reply-To: <200611260331.28847.max@love2party.net> Message-ID: <20061126165353.Y47830@delplex.bde.org> References: <20061125015223.GA51565@cdnetworks.co.kr> <200611260331.28847.max@love2party.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Nicolae Namolovan , freebsd-net@freebsd.org Subject: Re: ping -f panic [Re: Marvell Yukon 88E8056 FreeBsd Drivers] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Nov 2006 06:43:55 -0000 On Sun, 26 Nov 2006, Max Laier wrote: > On Saturday 25 November 2006 23:20, Nicolae Namolovan wrote: >> But I need to use it on a production server and the CURRENT one is too >> unstable, without too much thinking I just run ping -f 127.0.0.1 and >> after some minutes I got kernel panic, heh. > > could you please be more specific about this? My rather recent current > box is running for over 45min doing "ping -f 127.0.0.1" with no panic or > other ill behavior so far. After about 10min I disabled the icmp > limiting which obviously didn't trigger it either. Could you provide a > back trace or at least a panic message? Thanks. I haven't seen any problems with ping, but ttcp -u causes the panic in sbdrop_internal() about half the time when the client ttcp is killed by ^C. There is apparently a race in close when packets are arriving. The stack trace on the panicing CPU is (always?): ... sigexit exit1 ... closef ... soclose ... sbflush_internal sbdrop_internal panic and on the other CPU, with net.isr.direct=1 it was: bge_rxeof ... netisr_dispatch ip_input ... sbappendaddr_locked mb_ctor_mbuf --- trap (NMI IPI for cpustop). and with net.isr.direct=0, the other CPU was just running "idle: cpuN" and the bge thread was in ithread_loop. Bruce