From owner-freebsd-net@FreeBSD.ORG  Fri Jun 27 06:49:36 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E28F91065670
	for <net@freebsd.org>; Fri, 27 Jun 2008 06:49:36 +0000 (UTC)
	(envelope-from freebsd-net@transip.nl)
Received: from relay0.transip.nl (relay0.transip.nl [80.69.67.21])
	by mx1.freebsd.org (Postfix) with ESMTP id B50328FC20
	for <net@freebsd.org>; Fri, 27 Jun 2008 06:49:36 +0000 (UTC)
	(envelope-from freebsd-net@transip.nl)
Received: from [192.168.0.3] (ip86-50-212-87.adsl2.static.versatel.nl
	[87.212.50.86])
	by relay0.transip.nl (Postfix) with ESMTP id D0F9E102C65;
	Fri, 27 Jun 2008 08:49:33 +0200 (CEST)
Message-ID: <48648D70.50304@transip.nl>
Date: Fri, 27 Jun 2008 08:49:20 +0200
From: Ali Niknam <freebsd-net@transip.nl>
Organization: Transip BV
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
References: <486283B0.3060805@transip.nl>
	<5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc>
In-Reply-To: <5A9ZR/wNTIFIXEvIi7qXj2foxBI@/2P5JkFFETcbMzHSQ1hIkFGHokc>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
Cc: net@freebsd.org
Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state...
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Jun 2008 06:49:37 -0000

Hi Eygene,

> Just a quick "me too" message: I also used to see this on my 7.x
> machines.  This was with Apache servers in the proxy setup: one

I'm wondering: where these 32 bit, or 64 bit machines?

> I had already tried to debug this situation and Mike Silbersack
> helped me with patching the kernel.  At that days his patches (that
> went into 7.x) helped, but with higher request rate to the Apache,
> they seem to be back again.  I can try to setup the testbed and
> verify if I will still be able to reproduce them.  Will it be needed?
> 

Well, if your machine was indeed 64 bit, I for one would be very 
interested in knowing if it also appears in 32 bit.

Although perhaps a little far fetched a recent experience has made me 
aware that 64-bitness just might break things :)

Kind Regards,

Ali