| To: | Stephen Rothwell <sfr@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: TCP hang with 2.2.14 <-> 2.2.15pre5 |
| From: | Andi Kleen <ak@xxxxxx> |
| Date: | Fri, 24 Mar 2000 10:35:23 +0100 |
| Cc: | netdev@xxxxxxxxxxx, rusty@xxxxxxxxxxxxx, tridge@xxxxxxxxxxxxx |
| In-reply-to: | <200003240710.SAA02284@xxxxxxxxxxxxxxxxxxxx>; from Stephen Rothwell on Fri, Mar 24, 2000 at 08:12:08AM +0100 |
| References: | <200003240710.SAA02284@xxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Fri, Mar 24, 2000 at 08:12:08AM +0100, Stephen Rothwell wrote: > 16:37:07.987900 owl.rsync > elm.1216: . ack 31383222 win 31856 > <nop,nop,timestamp 528848505 2055387> (DF) > 16:37:07.987946 elm.1216 > owl.rsync: R 2680405324:2680405324(0) win 0 > 16:37:07.989904 elm.1216 > owl.rsync: R 31436798:31436798(0) ack 79735 win > 31856 <nop,nop,timestamp 2147827 528836519> (DF) The second reset is not generated by the Linux TCP/IP stack (we never send RSTs with options and windows). It looks like a normal ACK with a few bits flipped (?). The first one is bogus too because it has wrong sequence numbers, but at least the rest of the header looks normal. I would check the ethernet driver/card. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TCP hang with 2.2.14 <-> 2.2.15pre5, Stephen Rothwell |
|---|---|
| Next by Date: | 3c59x.c, Andrew Morton |
| Previous by Thread: | TCP hang with 2.2.14 <-> 2.2.15pre5, Stephen Rothwell |
| Next by Thread: | Re: TCP hang with 2.2.14 <-> 2.2.15pre5, Stephen Rothwell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |