From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 17:43:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47BFC16A4CE for ; Wed, 21 Jul 2004 17:43:25 +0000 (GMT) Received: from apathy.neglect.us (rapture.nine.org [69.17.66.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6978943D55 for ; Wed, 21 Jul 2004 17:43:24 +0000 (GMT) (envelope-from matt+list.sw.freebsd.current@publicly.neglect.us) Received: from [192.168.20.34] (ipffw01-dmz1.ipfabrics.com [4.18.226.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apathy.neglect.us (Postfix) with ESMTP id 36A44CEE for ; Wed, 21 Jul 2004 13:43:23 -0400 (EDT) Date: Wed, 21 Jul 2004 10:43:20 -0700 From: Matt White To: freebsd-current@freebsd.org Message-ID: <3270557515.1090406600@[192.168.20.34]> In-Reply-To: <000001c46f11$1f53a880$132a15ac@spud> References: <000001c46f11$1f53a880$132a15ac@spud> X-Mailer: Mulberry/3.1.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: RE: fetch hangs, part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 21 Jul 2004 17:43:25 -0000 In my case, I tracked this down to either my netscreen5 or the cable into it going south. It's a bit strange because other software wasn't having an issue, so I'll probably look at this more in the next few days. But for now, removing that box from my network has made fetch happy again, which in turn has made me happy again. -Matt --On Wednesday, July 21, 2004 3:54 AM -0700 Darren Pilgrim wrote: >> From: Robert Watson [mailto:rwatson@freebsd.org] >> >> >> On Tue, 20 Jul 2004, Darren Pilgrim wrote: >> >> > I've been having the same (or a similar problem). Fetching the >> > distfile for a port will hang. I poked some more at this and found >> > that all the sites fetch is hanging on successfully negotiate the TCP >> > connection then go dead without closing the connection. My workaround >> > has been to edit the Makefile and remove the offending site from >> > MASTER_SITES or manually fetch from ftp.freebsd.org. >> >> Could you try disabling TCP SACK > > Set net.inet.tcp.delayed_ack=0? > >> and see if things "get better"? It's one >> of the things that has changed in the TCP code recently. This could well >> be a user space fetch issue, but it would be worth trying it to see, if >> only to rule it out. > > It didn't change. The connections still hung. > >