From owner-freebsd-bugs@FreeBSD.ORG  Tue Sep  2 09:11:18 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
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 A822216A4BF; Tue,  2 Sep 2003 09:11:18 -0700 (PDT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5BF4B43FE5; Tue,  2 Sep 2003 09:11:17 -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 h82GATrO083074;
	Tue, 2 Sep 2003 12:10:29 -0400 (EDT)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)h82GASdp083071;
	Tue, 2 Sep 2003 12:10:28 -0400 (EDT)
Date: Tue, 2 Sep 2003 12:10:28 -0400 (EDT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: "James F.  Hranicky" <jfh@cise.ufl.edu>
In-Reply-To: <20030902120242.19519cf9.jfh@cise.ufl.edu>
Message-ID: <Pine.NEB.3.96L.1030902120928.81810L-100000@fledge.watson.org>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2003 16:11:18 -0000


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?
  
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.  Could you include
a list of your IPFW rules also, please?  I wonder if the kernel or
userland tool contains a bug that is causing it to misbehave for some
specific ruleset.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories