From owner-freebsd-current Mon May 15 14:58:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 73B2D37B8CF for ; Mon, 15 May 2000 14:58:45 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 7D8581CD7; Mon, 15 May 2000 14:58:44 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvsup on recent -CURRENT In-Reply-To: Message from naddy@mips.inka.de (Christian Weisgerber) of "15 May 2000 22:52:46 +0200." <8fpo2u$2viq$1@bigeye.rhein-neckar.de> Date: Mon, 15 May 2000 14:58:44 -0700 From: Peter Wemm Message-Id: <20000515215844.7D8581CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Weisgerber wrote: > (My original question should have gone out last Thursday but had > been stuck in a mail queue since.) > > Nick Hibma wrote: > > > > TreeList failed: Network write failure: Connection closed > > > > Which host are you pilling from? I am slurping things out of > > cvsup.uk.freebsd.org and see the same messages. > > The problem was most apparent with cvsup.uk.openbsd.org, which is > probably the same machine. It was less severe with cvsup.pasta.cs.uit.no, > and didn't occur at all with cvsup3.de.freebsd.org and for localhost > connections. > > Disabling newreno > > sysctl -w net.inet.tcp.newreno=0 > > immediately fixed the problem, so I guess we have the culprit there. Yes, there is a known bug in the newreno code. It was committed prematurely (before Jayanth was ready). Jayanth has fixed the problem and is doing some serious testing before committing a fix and reactivating it. The newreno sysctl defaults to off for the time being and has for a few days. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message