From: Frederic Leroy <fredo@starox.org>
To: Asdo <asdo@shiftmail.org>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Subject: Re: TCP sockets stalling - help! (long)
Date: Fri, 27 Nov 2009 21:53:24 +0100 [thread overview]
Message-ID: <20091127215324.5f494a86@houba> (raw)
In-Reply-To: <4B0FCC6D.3050003@shiftmail.org>
Le Fri, 27 Nov 2009 13:56:13 +0100,
Asdo <asdo@shiftmail.org> a écrit :
> Frederic Leroy wrote:
> > Le Wed, 25 Nov 2009 05:25:28 +0100,
> > Asdo <asdo@shiftmail.org> a écrit :
> >
> >
> >> Hi netdev and e1000 people,
> >>
> >> I have a weird problem here.
> >> [...]
> > I have the same kind of problem at home. I can't copy big files over
> > [...]
> Good God it's true then!
Yes :)
> Still if I am right, with Netcat you might end up with a corrupted
> file on the other side (shorter). Or maybe not, depending on how
> exactly the bug is made. Could you check this? Filesize and md5sum.
md5sum are ok.
I can't reproduce the problem on wire with a switch ( using both
10 and 100Mbp FD )
> Do you have Intel network card, with e1000e driver on SG? (see lsmod)
> (sorry I was wrong before, it's e1000e in my case not e1000)
> Otherwise it's probably the TCP layer...
Sorry, I forgot to precise the network hardware.
I forgot a noname 100Mbp switch between the isv box and sg host.
SG:
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
using module 8139cp
Devel:
02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
using b43 driver.
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB)
Ethernet Controller (rev 81)
using e100 in kernel ( no module )
My isv box is broadcom based, but I don't know which chipset for
wireless.
Since our hardware are different, I don't think it's coming from
hardware driver. I'm preparing traces for Ilpo
--
Frédéric Leroy
next prev parent reply other threads:[~2009-11-27 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 4:25 TCP sockets stalling - help! (long) Asdo
2009-11-25 11:48 ` Ilpo Järvinen
2009-11-25 13:07 ` Asdo
2009-11-25 15:36 ` Asdo
2009-11-25 16:38 ` Asdo
2009-11-25 22:29 ` [E1000-devel] " Ilpo Järvinen
2009-11-26 22:33 ` Frederic Leroy
2009-11-27 9:10 ` Ilpo Järvinen
2009-11-27 12:56 ` Asdo
2009-11-27 20:53 ` Frederic Leroy [this message]
2009-11-27 21:00 ` Ilpo Järvinen
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=20091127215324.5f494a86@houba \
--to=fredo@starox.org \
--cc=asdo@shiftmail.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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).