From owner-freebsd-current@FreeBSD.ORG Tue Jan 17 23:00:23 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C63331065696; Tue, 17 Jan 2012 23:00:23 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 8D75B8FC1E; Tue, 17 Jan 2012 23:00:23 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.5/8.14.5) with ESMTP id q0HN0Nr5081024; Tue, 17 Jan 2012 15:00:23 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.5/8.14.5/Submit) id q0HN0NIJ081023; Tue, 17 Jan 2012 15:00:23 -0800 (PST) (envelope-from sgk) Date: Tue, 17 Jan 2012 15:00:23 -0800 From: Steve Kargl To: Dimitry Andric Message-ID: <20120117230023.GA80996@troutmask.apl.washington.edu> References: <20120116204208.GA74223@troutmask.apl.washington.edu> <4F1498BC.3020608@FreeBSD.org> <20120116235402.GA75198@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120116235402.GA75198@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: svn stuck in read() 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: Tue, 17 Jan 2012 23:00:24 -0000 On Mon, Jan 16, 2012 at 03:54:02PM -0800, Steve Kargl wrote: > On Mon, Jan 16, 2012 at 10:38:04PM +0100, Dimitry Andric wrote: > > On 2012-01-16 21:42, Steve Kargl wrote: > > >Is anyone else seeing svn getting stuck while > > >updating /usr/src on an update-to-date freebsd-current? > > > > I saw this when I tried out serf instead of the default neon. For me, > > it hung in about 20% of remote operations. Reverting to neon fixed the > > problem, but I never delved any deeper. > > I'm not using serf. neon was fairly new, but I'll re-install > it to see if the problem presists. Thanks for the feedback. > After rebuilding apr-nothr-ipv6-devrandom-gdbm-db42 to not use threads, subversion works as expected. There appears to be some race condition with apr-* and libthr. -- Steve