From: Asdo <asdo@shiftmail.org>
To: Frederic Leroy <fredo@starox.org>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Subject: Re: TCP sockets stalling - help! (long)
Date: Fri, 27 Nov 2009 13:56:13 +0100 [thread overview]
Message-ID: <4B0FCC6D.3050003@shiftmail.org> (raw)
In-Reply-To: <20091126233302.42be8780@houba>
[-- Attachment #1.1: Type: text/plain, Size: 1423 bytes --]
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
> ssh unless I limit the rate ( ssh -l 8000 ... )
> After reading your mail, I make some quick tests ( see below).
>
> Results in short :
> - netcat always work.
> - ssh stalls, nearly immediately.
>
Good God it's true then!
I think I have an idea for why Netcat works while scp doesn't:
probably SCP pushing data requires replies from the application layer
(the 60 bytes I was telling about for SFTP) while netcat doesnt, it just
needs the Acks to keep pushing data.
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.
I think I just reproduced the bug on another machine, different hardware
(Supermicro mainboard), same Ubuntu, same kernel, same integrated Intel
network card. It just takes 5 hours or so for me to trigger.
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...
Would you paste here your lspci and lsmod?
Thank you
[-- Attachment #2: Type: text/plain, Size: 354 bytes --]
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
next prev parent reply other threads:[~2009-11-27 12:56 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 [this message]
2009-11-27 20:53 ` Frederic Leroy
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=4B0FCC6D.3050003@shiftmail.org \
--to=asdo@shiftmail.org \
--cc=e1000-devel@lists.sourceforge.net \
--cc=fredo@starox.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.