From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: netdev@vger.kernel.org
Subject: Network hangs on current git kernel
Date: Sat, 2 Jun 2012 10:25:03 +0200 [thread overview]
Message-ID: <20120602082503.GC329@x4> (raw)
I'm running the latest git kernel 3.4.0-09820-g86c47b7 and see periodic
network "hangs" on my machine.
These hangs mostly occur when I read nntp news articles. Every once in a
while the nntp client seems to take forever to fetch an article. During
these hangs I see packet losses:
% ping heise.de
PING heise.de (193.99.144.80) 56(84) bytes of data.
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=2 ttl=246 time=22.2 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=4 ttl=246 time=22.3 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=8 ttl=246 time=21.9 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=12 ttl=246 time=23.4 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=15 ttl=246 time=22.5 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=19 ttl=246 time=22.9 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=21 ttl=246 time=21.6 ms <== Hang stops here
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=22 ttl=246 time=23.2 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=23 ttl=246 time=23.4 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=24 ttl=246 time=22.9 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=25 ttl=246 time=22.9 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=26 ttl=246 time=22.5 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=27 ttl=246 time=22.4 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=28 ttl=246 time=22.4 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=29 ttl=246 time=22.0 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=30 ttl=246 time=22.4 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=31 ttl=246 time=22.0 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=32 ttl=246 time=22.0 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=33 ttl=246 time=22.0 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=34 ttl=246 time=21.8 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=35 ttl=246 time=23.1 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=36 ttl=246 time=22.4 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=37 ttl=246 time=23.2 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=38 ttl=246 time=22.3 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=39 ttl=246 time=32.2 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=40 ttl=246 time=22.5 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=41 ttl=246 time=22.6 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=42 ttl=246 time=23.7 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=43 ttl=246 time=22.7 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=44 ttl=246 time=27.4 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=45 ttl=246 time=22.2 ms
64 bytes from redirector.heise.de (193.99.144.80): icmp_req=46 ttl=246 time=22.5 ms
^C
--- heise.de ping statistics ---
46 packets transmitted, 32 received, 30% packet loss, time 45101ms
rtt min/avg/max/mdev = 21.613/23.021/32.210/1.924 ms
Sorry, if this all sounds somewhat vague. I will try to record a sysrq-w dump
in the future.
--
Markus
next reply other threads:[~2012-06-02 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 8:25 Markus Trippelsdorf [this message]
2012-06-02 9:50 ` Network hangs on current git kernel Eric Dumazet
2012-06-02 10:57 ` Francois Romieu
2012-06-02 11:15 ` Eric Dumazet
2012-06-02 11:23 ` Markus Trippelsdorf
2012-06-02 11:27 ` Markus Trippelsdorf
2012-06-02 15:48 ` Eric Dumazet
2012-06-02 16:34 ` Markus Trippelsdorf
2012-06-02 17:16 ` Markus Trippelsdorf
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=20120602082503.GC329@x4 \
--to=markus@trippelsdorf.de \
--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).