From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15046 invoked by alias); 26 Jan 2009 16:29:38 -0000 Received: (qmail 15036 invoked by uid 22791); 26 Jan 2009 16:29:37 -0000 X-Spam-Check-By: sourceware.org Received: from pool-71-126-240-83.bstnma.fios.verizon.net (HELO cgf.cx) (71.126.240.83) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Jan 2009 16:29:34 +0000 Received: from ednor.cgf.cx (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id EF52413C028 for ; Mon, 26 Jan 2009 11:29:23 -0500 (EST) Received: by ednor.cgf.cx (Postfix, from userid 201) id E82E52B385; Mon, 26 Jan 2009 11:29:23 -0500 (EST) Date: Mon, 26 Jan 2009 17:17:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [1.7] regression wrt scp? Message-ID: <20090126162923.GA1074@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <49644339.8000508@cwilson.fastmail.fm> <20090108103349.GB14304@calimero.vinschen.de> <20090108161513.GA10914@trixie.casa.cgf.cx> <20090126074307.GA32214@ednor.casa.cgf.cx> <20090126142815.GD16129@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090126142815.GD16129@calimero.vinschen.de> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2009-01/txt/msg00763.txt.bz2 On Mon, Jan 26, 2009 at 03:28:15PM +0100, Corinna Vinschen wrote: >On Jan 26 02:43, Christopher Faylor wrote: >> I finally managed to duplicate this. >> [...] >> >It's already on my list to investigate. When I saw "broken pipe" I >> >thought it could be something in the new pipe code. >> >> But, if it is, I can't see it yet. >> >> The strace snippet below seems to show that the ssh process which scp >> forks is expecting for the socket to become writable but that never happens. >> >> At time 10048910 you can see 16384 bytes received. Then select() is >> called to inspect the socket handler for readability/writability. But >> select claims that the socket handle is never ready. > >It's probably right about that. The peek_socket function is called in a >loop by the thread_socket function (via select) with a non INFINITE >timeout. The "Broken pipe" message already occured at the time the >peek_socket function is repeated ad infinitum. This message in the >strace does not mean that SSH hangs for that reason, it just doesn't get >any data from the remote side. SSH maintains a select loop over all >open descriptors and every poll from the thread_socket function >generates this debug message. SSH seems to be waiting for data from the >local pipe to the local scp actually. Ok. I was pretty sure that I hadn't seen a broken pipe message at this point but I could be mistaken. Btw, in an unrelated problem, the reason that I didn't look into this earlier was because my normal system for debugging this problem can no longer connect to sourceware.org. I am not running a firewall or any BLODA but it seems to hang in the initial connect and never recover. 1.5.25 works fine. It is just sourceware.org which seems to have this problem, which is weird. I assume that if 1.7 goes live I won't be the only one with this problem. I guess I should start a new thread to discuss it. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/