From owner-freebsd-bugs@FreeBSD.ORG Wed Sep 3 03:28:13 2003 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 D125516A4BF; Wed, 3 Sep 2003 03:28:13 -0700 (PDT) Received: from mail.cise.ufl.edu (redoak.cise.ufl.edu [128.227.205.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7F0943FB1; Wed, 3 Sep 2003 03:28:11 -0700 (PDT) (envelope-from jfh@cise.ufl.edu) Received: from waterspout.cise.ufl.edu (waterspout.cise.ufl.edu [128.227.205.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cise.ufl.edu (Postfix) with ESMTP id F08D1FE41; Wed, 3 Sep 2003 06:28:10 -0400 (EDT) Date: Wed, 3 Sep 2003 06:28:09 -0400 From: "James F. Hranicky" To: Robert Watson Message-Id: <20030903062809.2ae57891.jfh@cise.ufl.edu> In-Reply-To: References: <20030902120242.19519cf9.jfh@cise.ufl.edu> Organization: University of Florida CISE Department X-Mailer: Sylpheed version 0.9.4 (GTK+ 1.2.8; sparc-sun-solaris2.8) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: admin@cise.ufl.edu cc: FreeBSD-gnats-submit@FreeBSD.org cc: freebsd-bugs@FreeBSD.org Subject: Re: conf/56031: ipfw hangs on every invocation 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: Wed, 03 Sep 2003 10:28:14 -0000 On Tue, 2 Sep 2003 12:10:28 -0400 (EDT) Robert Watson wrote: > > On Tue, 2 Sep 2003, James F. Hranicky wrote: > > > Let me know if I can provide any more info. > > This seems to suggest it's really just the userland application spinning, > not a hang in the kernel. Could you try using truss to see if, once it > starts spinning, it's making system calls, or just stuck entirely in > userspace? As far as I can tell it's hanging in the last ioctl() . > Assuming it's purely a userspace problem (perhaps triggered by > syntactically poor output from the kernel), the next thing to do is > probably to instrument your ipfw binary with either printfs or debugging > symbols and see where in its execution it is spinning. I can compile it with debugging symbols and trace through the execution, but it seems like the ioctl() is where it's hanging, again some kind of odd terminal thing. > Could you include a list of your IPFW rules also, please? I don't have any set at this time, just the default pass any any. I'll trace through it with gdb if you think it will help. Jim