netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Subject: Re: TCP connection hang problem with 2.6.16.16, e1000.
Date: Wed, 31 May 2006 10:26:03 -0700	[thread overview]
Message-ID: <447DD1AB.3030909@candelatech.com> (raw)
In-Reply-To: <447DC830.4080201@candelatech.com>

Ben Greear wrote:
> Kernel is 2.6.16.16 with my patches, including a patch to the
> e1000.  I also rebuilt a fresh kernel with only the attached
> send-to-self patch.  I see the hang, but there was no OOM messages,
> probably because the machine was freshly rebooted and had plenty
> of buffers available.  I will try to reproduce this with some other
> NICs next...

The same problem happens with a single TCP connection between two
copper 10/100/1000 intel ports on the FC2 dual-xeon 32-bit machine.


I tried a dual-core AMD system running 64-bit kernel and FC5.  This kernel
is running my complete set of patches (against 2.6.16.16).

I can reproduce with Intel pro/1000 on this dual-core system when I up the rate to 400Mbps
and do 50,000 byte writes (can only get 125Mbps with 5000 byte writes on
this system, and it ran at that speed for several minutes w/out problem.)

I can also reproduce when using the tg3 adapters, but the tg3 can only run at about
220Mbps, even with the larger write size.  This slower speed could be because of bus
issues or the VLAN I used for one end of the connection.  I could not see this problem with tg3 untill
I yanked the cable a few times and then ran the connection through my network
emulator (which will cause a bit of latency and some dropped packets).  The tethereal
output looks slightly different, but I think this is just because it is a different
version from the older FC2 system from my previous email.

   0.399107  192.168.1.3 -> 192.168.1.2  TCP 33020 > 33019 [ACK] Seq=4294967248 Ack=48 Win=11998 Len=0 TSV=943608 TSER=842823
   0.400565  192.168.1.2 -> 192.168.1.3  TCP 33019 > 33020 [ACK] Seq=0 Ack=0 Win=11998 Len=0 TSV=943608 TSER=842824
   0.400764  192.168.1.3 -> 192.168.1.2  TCP 33020 > 33019 [ACK] Seq=4294967248 Ack=48 Win=11998 Len=0 TSV=943608 TSER=842823
   0.400948  192.168.1.2 -> 192.168.1.3  TCP 33019 > 33020 [ACK] Seq=0 Ack=0 Win=11998 Len=0 TSV=943608 TSER=842824
   0.408851  192.168.1.3 -> 192.168.1.2  TCP 33020 > 33019 [ACK] Seq=4294967248 Ack=48 Win=11998 Len=0 TSV=943608 TSER=842823
   0.410005  192.168.1.2 -> 192.168.1.3  TCP 33019 > 33020 [ACK] Seq=0 Ack=0 Win=11998 Len=0 TSV=943608 TSER=842824
   0.411524  192.168.1.3 -> 192.168.1.2  TCP 33020 > 33019 [ACK] Seq=4294967248 Ack=48 Win=11998 Len=0 TSV=943608 TSER=842823
   0.450702  192.168.1.2 -> 192.168.1.3  TCP 33019 > 33020 [ACK] Seq=0 Ack=0 Win=11998 Len=0 TSV=943608 TSER=842824


Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2006-05-31 17:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-31 16:45 TCP connection hang problem with 2.6.16.16, e1000 Ben Greear
2006-05-31 17:26 ` Ben Greear [this message]
2006-05-31 17:54 ` Auke Kok
2006-05-31 18:00   ` Ben Greear
2006-05-31 19:37     ` Ben Greear
2006-05-31 21:45       ` TCP connection hang problem with 2.6.16.16, e1000 (found work-around) Ben Greear
2006-05-31 22:10         ` Stephen Hemminger
2006-05-31 22:38           ` Ben Greear
2006-06-01  2:56 ` TCP connection hang problem with 2.6.16.16, e1000 Herbert Xu

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=447DD1AB.3030909@candelatech.com \
    --to=greearb@candelatech.com \
    --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).