From owner-freebsd-net@FreeBSD.ORG Thu May 8 09:17:09 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB4881065689; Thu, 8 May 2008 09:17:09 +0000 (UTC) (envelope-from mark@pogo.org.uk) Received: from metheny.ijneb.com (unknown [IPv6:2001:ba8:0:1ba:214:22ff:feb1:2693]) by mx1.freebsd.org (Postfix) with ESMTP id 7AF938FC26; Thu, 8 May 2008 09:17:09 +0000 (UTC) (envelope-from mark@pogo.org.uk) Received: from localhost ([127.0.0.1] ident=mark) by metheny.ijneb.com with esmtp (Exim 4.69) (envelope-from ) id 1Ju2FR-0006Uf-7u; Thu, 08 May 2008 10:17:09 +0100 Date: Thu, 8 May 2008 10:17:09 +0100 (BST) From: Mark Hills To: Andre Oppermann In-Reply-To: <4822BABB.4020407@freebsd.org> Message-ID: References: <20080506133208.C2EC.B627C632@gmail.com> <48223324.6070203@freebsd.org> <20080508120410.70E4.B627C632@gmail.com> <4822BABB.4020407@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: mark@pogo.org.uk Cc: freebsd-net@freebsd.org, Deng XueFeng Subject: Re: read() returns ETIMEDOUT on steady TCP connection X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2008 09:17:09 -0000 On Thu, 8 May 2008, Andre Oppermann wrote: > Deng XueFeng wrote: >> hi, >> the patch can not apply to 6.2, cound do a new patch for 6.2 or 6.3 ? > > The logging function is not (yet) present in RELENG_6. I'll post the > patch when I've backported the functionality. > > However it's an important information that it happens on 6.2 too. That > means the source of the trouble wasn't introduced with 7.0. I did earlier tests with the same software on FreeBSD 6.3 and never saw ETIMEDOUT -- only on FreeBSD 7.0. But I did have a different issue with 6.3 (lockups under very heavy conditions), although didn't do any specific tuning to try and stop this. Instead I made the jump to 7.0 which stopped this problem but introduced the ETIMEDOUT one. Mark