From owner-freebsd-current@FreeBSD.ORG Mon Apr 2 09:58:04 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 489B916A405 for ; Mon, 2 Apr 2007 09:58:04 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id B047E13C483 for ; Mon, 2 Apr 2007 09:58:03 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 8424 invoked from network); 2 Apr 2007 08:58:10 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Apr 2007 08:58:10 -0000 Message-ID: <4610CD68.2060706@freebsd.org> Date: Mon, 02 Apr 2007 11:31:20 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Barrett Lyon References: <20070401005604.051A473039@freebsd-current.sentex.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: TCP sessions hanging in FIN_WAIT_1? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2007 09:58:04 -0000 Barrett Lyon wrote: > I've been testing CURRENT for a bit and with a thousands of short lived > HTTP sessions, CURRENT hangs most of the sessions in FIN_WAIT_1 status > until the machine runs out of resources and causes the network stack to > stop performing. The HTTP daemon I am playing with is lighttpd-1.4.13, > and I don't see this happening on any of the 6.2 test machines I run. > > There's nothing unusual about the build other than the interface card > running the mxge driver. Has anyone else seen reports of this? I have > seen this behavior on all source up to today's tree. Are you running a pure GENERIC kernel or do you have any other modifications? What about firewall packages (ipfw, pf, ipfilter)? -- Andre