From: Krzysztof Halasa <khc@pm.waw.pl>
To: <netdev@oss.sgi.com>
Subject: TCP stalls, 2.6.12pre6
Date: Fri, 10 Jun 2005 00:58:55 +0200 [thread overview]
Message-ID: <m3mzpz87dc.fsf@defiant.localdomain> (raw)
Hi,
I got this three times recently, with 2.6.12 pre6 and possibly pre5 (4?)
kernels on both sides:
intrepid is X11-server with ssh connection to defiant (X11-forwarding,
EPIC100 PCI NIC). defiant is an older notebook machine and it was running
XEmacs and Firefox with ssh/X11 (cardbus DEC 21143).
Both on the same Ethernet subnet. Both standard MTU etc.
intrepid# netstat -to
tcp 0 0 intrepid:3457 defiant:ssh ESTABLISHED keepalive (5615.71/0/0)
defiant# netstat -to (not 100% sure about this data)
Send-Q
tcp 0 32800 defiant:ssh intrepid:3457 ESTABLISHED keepalive (20.5/0/0)
Partial dump:
intrepid# tcpdump -r qwe -vve port not 4840
00:08:32.603003 len 1514: IP (tos 0x10, ttl 64, id 17467, offset 0,
flags [DF], proto 6, length: 1500) defiant.ssh > intrepid.3457: .
[bad tcp cksum 2fa (->8fbe)!] 2999401769:2999403217(1448)
ack 1597770543 win 16022 <nop,nop,timestamp 131339306 29183805>
00:08:55.750326 len 158: IP (tos 0x10, ttl 64, id 13187, offset 0,
flags [DF], proto 6, length: 144) intrepid.3457 > defiant.ssh: P
[tcp sum ok] 1:81(80) ack 0 win 18856 <nop,nop,timestamp 29224727
131133680,nop,nop,sack sack 1 {1448:16816} >
00:08:55.750603 len 66: IP (tos 0x10, ttl 64, id 17469, offset 0,
flags [DF], proto 6, length: 52) defiant.ssh > intrepid.3457: .
[tcp sum ok] 16816:16816(0) ack 81 win 16022 <nop,nop,timestamp
131362456 29224727>
Send-Q is stuck at the fixed value. Other TCP connections (including
similar ones between the two hosts) are not affected.
Ideas?
--
Krzysztof Halasa
next reply other threads:[~2005-06-09 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 22:58 Krzysztof Halasa [this message]
2005-06-11 17:44 ` TCP stalls - sack?, 2.6.12pre6 Krzysztof Halasa
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=m3mzpz87dc.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=netdev@oss.sgi.com \
/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