From owner-freebsd-bugs@FreeBSD.ORG Wed Sep 3 03:30:20 2003 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 BD75216A4BF for ; Wed, 3 Sep 2003 03:30:20 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A04A43FFD for ; Wed, 3 Sep 2003 03:30:20 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h83AUKUp027903 for ; Wed, 3 Sep 2003 03:30:20 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h83AUKcO027901; Wed, 3 Sep 2003 03:30:20 -0700 (PDT) Date: Wed, 3 Sep 2003 03:30:20 -0700 (PDT) Message-Id: <200309031030.h83AUKcO027901@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "James F. Hranicky" Subject: Re: conf/56031: ipfw hangs on every invocation X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "James F. Hranicky" List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2003 10:30:20 -0000 The following reply was made to PR conf/56031; it has been noted by GNATS. From: "James F. Hranicky" To: Robert Watson Cc: FreeBSD-gnats-submit@FreeBSD.org, admin@cise.ufl.edu, freebsd-bugs@FreeBSD.org Subject: Re: conf/56031: ipfw hangs on every invocation Date: Wed, 3 Sep 2003 06:28:09 -0400 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