DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 51HH67bw3024716
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 51HH67bw3024716
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=QBohoKXO
X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5A26C3858C51
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1739811965;
	bh=jhNe9rmi8ik/cw1M4rSfitMCu6h7gvQarmGgzCQ81IU=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=QBohoKXOTTudlMp9jIybZndIW/vqwjhl6Uz4YhDw6ru6/HW6tQzDttaCT7xoDG6xr
	 95cI6y04BMyUnaqwky75KmVdNnVkrVDNgy3OtzVfOKtwPCkM0ZX1LqKFM/C3IKrqHE
	 s3HNWEtrklogeVhgpPF+yHvCcM3L6CrrvAT3WhkI=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DB0C63858C33
Date: Mon, 17 Feb 2025 18:00:44 +0100
To: cygwin@cygwin.com
Subject: Re: [CALL FOR TESTING] Cygwin-3.6.0
Message-ID: <Z7NrPB4v62491Kfv@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <Z6-TZk74C8i5wgFD@calimero.vinschen.de>
 <c852f06e-fde6-41dc-95d9-e0081d5c995e@emrich-ebersheim.de>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <c852f06e-fde6-41dc-95d9-e0081d5c995e@emrich-ebersheim.de>
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>

Hi Rainer,

On Feb 17 12:51, Rainer Emrich via Cygwin wrote:
> Hi Corinna,
> 
> Am 14.02.2025 um 20:03 schrieb Corinna Vinschen via Cygwin-announce:
> > we're planning the next major release in the next few (hopefully
> > not more than two) weeks.
> > [...]
> > At this point, we're most interested if the test release introduces
> > regressions compared to 3.5.7!
> > [...]
> 
> I'm facing a strange major issue with scp. The issue exists in all cygwin version later than 3.5.3,
> including cygwin-3.6.0-0.374.g4dd859d01c22.
> 
> If I'm copying a large file with scp I get a "connection lost" after a random couple of seconds:
> 
> scp -v large_file foobar:
> .
> .
> debug1: Sending subsystem: sftp
> debug1: pledge: fork
> large_file                                             10%   71MB   4.3MB/s   02:21 ETA
> debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
> debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
> debug1: channel 0: free: client-session, nchannels 1
> Transferred: sent 92266460, received 35436 bytes, in 15.3 seconds
> Bytes per second: sent 6035219.0, received 2317.9
> debug1: Exit status 11
> lost connection

In fact, I can reproduce this occassionally back to 3.5.0 and back to
OpenSSH 9.7p1.  We can't easily try this with older Cygwin versions.
It's getting increasingly hard to build older Cygwin versions due to
compiler dependencies and missing symbols.

What that means in the first place, is that this is neither a regression
from 3.5.7, nor even from 3.5.1.  Obviously I can't prove if this has
been introduced into 3.5.0, but I'd like to point out that we didn't
have any noticable change in the socket code for almost 4 years, back
during 3.3 development.

Fun fact: I can NOT reproduce the problem when using the -O option,
i. e., when using the old scp protocol.  The old protocol isn't
slower either.

Maybe that's a workaround for you?

> The strange thing, if I use strace to debug this, the cpoy succeeds:
> strace -efno strace.log scp -v large_file foobar:

This often points to a timing issue, but beats me where that could be.

> I would try to debug this further, if I had an idea how to do that.

Same here ATM, sorry.


Corinna

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
