From: Frederic Leroy <fredo@starox.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Netdev <netdev@vger.kernel.org>, Asdo <asdo@shiftmail.org>
Subject: Re: scp stalls mysteriously
Date: Mon, 30 Nov 2009 21:37:27 +0100 [thread overview]
Message-ID: <20091130213727.2f4047d2@houba> (raw)
In-Reply-To: <alpine.DEB.2.00.0911302113390.9826@melkinpaasi.cs.helsinki.fi>
Le Mon, 30 Nov 2009 22:18:22 +0200 (EET),
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> a écrit :
> On Mon, 30 Nov 2009, Frederic Leroy wrote:
>
> Thanks, at least ....3.... shows that cwnd (congestion window, the
> 2nd to last field in /proc/net/tcp) goes to zero which it never ever
> should. ...I'll start reading some code to figure out the cause for
> that.
>
> How much is your RTT btw?
The RTT is ~ 1.4ms.
The following trace has a rtt as big as 5ms but most of the time, it's
under 1.4ms and periodically grow to 3ms.
-------------------------------------------
64 bytes from sg (192.168.1.19): icmp_seq=681 ttl=64 time=1.26 ms
64 bytes from sg (192.168.1.19): icmp_seq=682 ttl=64 time=1.26 ms
64 bytes from sg (192.168.1.19): icmp_seq=683 ttl=64 time=1.34 ms
64 bytes from sg (192.168.1.19): icmp_seq=684 ttl=64 time=2.01 ms
64 bytes from sg (192.168.1.19): icmp_seq=686 ttl=64 time=2.15 ms
64 bytes from sg (192.168.1.19): icmp_seq=687 ttl=64 time=5.07 ms
64 bytes from sg (192.168.1.19): icmp_seq=688 ttl=64 time=1.19 ms
64 bytes from sg (192.168.1.19): icmp_seq=689 ttl=64 time=1.30 ms
64 bytes from sg (192.168.1.19): icmp_seq=690 ttl=64 time=1.19 ms
64 bytes from sg (192.168.1.19): icmp_seq=691 ttl=64 time=1.14 ms
-------------------------------------------
> The RTO timeout easily goes up to 120
> secods similar to what I found myself already. Thus I'm not sure if
> this stall would be "infinite" after all.
I notice that grep '":0016" /proc/net/tcp' stop to report something when
it stalls. Is the connection closed ?
> I've some problem in .3. case in matching timing of the proc/net/tcp
> dump and the tcpdump ... did you perhaps cut it somewhere?
No, I didn't cut it.
> This might
> point out to yet another problem, however, I'm not sure what I can
> atm trust in the logs. ...Timestamps would probably help me a bit
> (I've changed also sleep to do 0.01 granularity):
>
> while [ : ]; do date "+%s.%N"; grep ":0016" /proc/net/tcp; sleep
> 0.01; done | tee scp_stall-houba.x.proc_net_tcp
> (Please run start while loop before starting the transfer and all the
> way until the connection is already killed and only then stop the
> loop).
I took care to timings this time. I did as you said.
> What happened in .2. case I've very little idea, proc/net/tcp does
> claim retransmission would have happened on TCP layer but that never
> went into tcpdump log (the kind of thing might have happened in
> the .3. case too which is why I asked for the timestamps for matching
> captures more exactly but there were some retransmissions earlier in
> the log so I cannot be sure). Can you also check that tcpdump doesn't
> lose any packets, it should show: "0 packets dropped by kernel" when
> you ctrl-c it.
I still have the logs, O packet dropped :
-------------------------------------------
houba tmp # tcpdump -i wlan1 -s 1500 -w /tmp/ssh_stall-houba.1.pcap -vv
ether host 00:40:45:09:3f:3f tcpdump: listening on wlan1, link-type
EN10MB (Ethernet), capture size 1500 bytes ^C8923 packets captured
8923 packets received by filter
0 packets dropped by kernel
houba tmp # tcpdump -i wlan1 -s 1500 -w /tmp/scp_stall-houba.3.pcap
-vv ether host 00:40:45:09:3f:3f tcpdump: listening on wlan1, link-type
EN10MB (Ethernet), capture size 1500 bytes ^C17045 packets captured
17045 packets received by filter
0 packets dropped by kernel
houba tmp #
-------------------------------------------
--
Frédéric Leroy
next prev parent reply other threads:[~2009-11-30 20:37 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 21:35 scp stalls mysteriously Frederic Leroy
2009-11-27 22:12 ` Ilpo Järvinen
[not found] ` <20091128010156.1219012a@houba>
2009-11-28 11:31 ` Ilpo Järvinen
2009-11-29 22:13 ` Ilpo Järvinen
2009-11-30 18:50 ` Frederic Leroy
2009-11-30 19:10 ` Ilpo Järvinen
2009-11-30 20:18 ` Ilpo Järvinen
2009-11-30 20:37 ` Frederic Leroy [this message]
2009-11-30 21:37 ` Ilpo Järvinen
2009-11-30 22:19 ` Frederic Leroy
2009-12-01 20:19 ` Frederic Leroy
2009-12-01 20:27 ` Ilpo Järvinen
2009-12-02 7:59 ` Frederic Leroy
2009-12-02 12:59 ` Ilpo Järvinen
2009-12-02 15:44 ` Frederic Leroy
2009-12-02 16:05 ` Ilpo Järvinen
2009-12-02 17:34 ` Frederic Leroy
2009-12-02 19:17 ` Damian Lukowski
2009-12-03 8:59 ` Frederic Leroy
2009-12-03 10:29 ` Ilpo Järvinen
2009-12-03 10:34 ` David Miller
2009-12-03 10:48 ` Ilpo Järvinen
2009-12-03 12:19 ` Asdo
2009-12-03 11:57 ` Damian Lukowski
2009-12-03 12:19 ` Damian Lukowski
2009-12-03 12:49 ` Ilpo Järvinen
2009-12-03 14:10 ` Damian Lukowski
2009-12-03 19:23 ` Frederic Leroy
2009-12-03 20:34 ` Damian Lukowski
2009-12-03 22:03 ` Frederic Leroy
2009-12-04 10:41 ` Ilpo Järvinen
2009-12-04 9:36 ` Frederic Leroy
2009-12-04 11:14 ` Ilpo Järvinen
2009-12-04 13:58 ` Frederic Leroy
2009-12-04 15:09 ` Ilpo Järvinen
2009-12-03 20:36 ` Ilpo Järvinen
2009-12-03 21:37 ` Frederic Leroy
2009-12-05 22:32 ` Damian Lukowski
2009-12-06 10:29 ` Ilpo Järvinen
2009-12-06 17:48 ` Ilpo Järvinen
2009-12-06 22:44 ` Damian Lukowski
2009-12-06 23:09 ` Ilpo Järvinen
2009-12-06 20:32 ` Frederic Leroy
2009-12-07 14:01 ` Ilpo Järvinen
2009-12-07 22:18 ` Frederic Leroy
2009-12-07 22:38 ` Ilpo Järvinen
2009-12-09 4:54 ` David Miller
2009-12-03 12:11 ` Frederic Leroy
2009-12-03 12:44 ` Ilpo Järvinen
2009-12-03 13:37 ` Arnd Hannemann
2009-12-03 14:27 ` Arnd Hannemann
2009-12-03 14:36 ` Ilpo Järvinen
2009-12-03 15:34 ` Arnd Hannemann
2009-12-03 15:48 ` Ilpo Järvinen
2009-12-03 18:32 ` Greg KH
2009-12-03 21:37 ` David Miller
2009-12-03 8:56 ` Frederic Leroy
2009-11-30 21:24 ` Frederic Leroy
2009-11-30 21:26 ` Ilpo Järvinen
2009-11-30 21:54 ` Frederic Leroy
2009-11-27 22:22 ` Frederic Leroy
2009-11-27 22:28 ` Ilpo Järvinen
2009-11-27 22:30 ` Ilpo Järvinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091130213727.2f4047d2@houba \
--to=fredo@starox.org \
--cc=asdo@shiftmail.org \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).