| To: | gandalf@xxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: Dump of TCP hang in established state |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 29 May 2003 14:54:33 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <1054238230.709.1.camel@xxxxxxxxxxxxxx> |
| References: | <20030529.024114.78714066.davem@xxxxxxxxxx> <1054217010.757.39.camel@xxxxxxxxxxxxxx> <1054238230.709.1.camel@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Martin Josefsson <gandalf@xxxxxxxxxxxxxx> Date: 29 May 2003 21:57:11 +0200 I've just tested 2.5-bk and I can still reproduce it. Can you get a tcpdump trace at the sender side for the complete life of the connection for which the hang occurs? There isn't much we can do about this without a trace. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Dump of TCP hang in established state, David S. Miller |
|---|---|
| Next by Date: | Re: 2.5.70 kernel BUG at net/xfrm/xfrm_policy.c:185!, David S. Miller |
| Previous by Thread: | Re: Dump of TCP hang in established state, David S. Miller |
| Next by Thread: | Re: Dump of TCP hang in established state, Martin Josefsson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |