Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Jun 2012 17:28:17 +0200
From:      Andreas Tobler <andreast-list@fgznet.ch>
To:        freebsd-current@freebsd.org, freebsd-ia64@freebsd.org, Maxime Henrion <mux@freebsd.org>
Subject:   Re: csup ends up in sigwai after "Shutting down connection to server", never exits
Message-ID:  <4FDA0311.2050300@fgznet.ch>
In-Reply-To: <20120614150417.GA1309@mech-cluster241.men.bris.ac.uk>
References:  <20120614105738.GA35741@mech-cluster241.men.bris.ac.uk> <20120614132016.GB40355@felucia.tataz.chchile.org> <20120614150417.GA1309@mech-cluster241.men.bris.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On 14.06.12 17:04, Anton Shterenlikht wrote:
> On Thu, Jun 14, 2012 at 03:20:16PM +0200, Jeremie Le Hen wrote:
>> Hi Anton,
>>
>> On Thu, Jun 14, 2012 at 11:57:38AM +0100, Anton Shterenlikht wrote:
>>> On ia64 r235474 and r235163 I get:
>>>
>>> # csup -L2 /root/ports-supfile
>>> Parsing supfile "/root/ports-supfile"
>>> Connecting to cvsup.uk.FreeBSD.org
>>> Connected to 131.111.8.41
>>> Server software version: SNAP_16_1h
>>> MD5 authentication started
>>> MD5 authentication successful
>>> Negotiating file attribute support
>>> Exchanging collection information
>>> Establishing multiplexed-mode data connection
>>> Running
>>> Updating collection ports-all/cvs
>>> Shutting down connection to server
>>>
>>> csup never exits.
>>>
>>> >From top:
>>>
>>>    PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
>>> 33822 root          2  20    0 37496K 23352K sigwai  1   0:32  0.00% csup
>>>
>>>
>>> On amd64 r236740M I don't see this problem.
>>
>> mux@ fixed many bugs in his bitbucket source tree [1], would you mind
>> giving it a spin?  I may import the latest code into the tree when I
>> have enough free time.
>>
>> [1] https://bitbucket.org/mux/csup
>
> no, this doesn't help.
> I get exactly the same behaviour.
> Perhaps the problem is not in csup.
>
> Any ideas on how to debug this further?
>

Not really debugging, but did you try to fetch a fresh ports-tree?
Had something similar yesterday (afair on ppc64) and ended with a fresh 
csup.

Gruss,
Andreas



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FDA0311.2050300>