From owner-freebsd-bugs@FreeBSD.ORG Wed Sep 3 08:46:27 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 0159C16A4C0; Wed, 3 Sep 2003 08:46:27 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA00843FDF; Wed, 3 Sep 2003 08:46:25 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h83FjfrO094326; Wed, 3 Sep 2003 11:45:41 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h83Fjfuw094323; Wed, 3 Sep 2003 11:45:41 -0400 (EDT) Date: Wed, 3 Sep 2003 11:45:41 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "James F. Hranicky" In-Reply-To: <20030903062809.2ae57891.jfh@cise.ufl.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 15:46:27 -0000 On Wed, 3 Sep 2003, James F. Hranicky wrote: > 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() . In, or after? The "Running" state reported by Ctrl-T suggests it is in userspace spinning, perhaps as a result of an unexpected return from the 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. I'd step up to the ioctl in question, and then see if it really hangs in the ioctl(), or if it gets past and starts spinning. If it's the ioctl(), it would be very helpful to know which file descriptor it's on, and what the arguments are. If it's not the ioctl() call, we need to figure out which loop isn't taking something important into account. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories