From owner-freebsd-hackers Thu Oct 10 21:48:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0C3A37B401 for ; Thu, 10 Oct 2002 21:48:17 -0700 (PDT) Received: from mail1.informationwave.net (dipole.informationwave.net [199.74.235.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8532443E77 for ; Thu, 10 Oct 2002 21:48:17 -0700 (PDT) (envelope-from abe@informationwave.net) Received: by mail1.informationwave.net (Postfix, from userid 1007) id 767B64F921; Fri, 11 Oct 2002 00:46:36 -0400 (EDT) Date: Fri, 11 Oct 2002 00:46:36 -0400 From: abe To: hackers@freebsd.org Subject: Re: fatal trap 12 kernel panic Message-ID: <20021011044636.GA84506@dipole.informationwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello folks, Recently I have been corresponding with several from this list and questions@ with regard to an odd issue with ipfw and my machine panicing after any network communication was attempted after loading some IPFW rules. Some evidence of the panics can be found at: http://dipole.informationwave.net/~abe/fbsd.jpg http://dipole.informationwave.net/~abe/crash.mpg http://dipole.informationwave.net/~abe/trace.txt Unfortunately, feedback sent while in good intentions did not help. However, in further tinkering with this issue I believe I've come to a conclusion. I run a rather high-traffic server so I had initially increased net.inet.ip.fw.dyn_buckets to 500, from the default 256 as people were complaining that they were getting connection refusals. At the time of the complaints, it seemed the max dyn_buckets limit had been reached. In attempt to remedy this as I said above I increased it. After this week of going through many hardware tests and so forth trying multiple machines with the same rules and numerous fresh installations, tonight I set the default net.inet.ip.fw.dyn_buckets back to 256 and no issues. So then on a chance, I increased the value to 512. After this, I attempted to reproduce the panic with the same procedure I had taken before making this change. No panics post-change. I'm going to be keeping a close eye on this server and hoping that it was as simple an issue as that, and if not of course pursue the answer until it is found. If anyone has any comments or thoughts on this, please feel free to contact me on or off the list. Regards, Abe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message