From: Eric Dumazet <eric.dumazet@gmail.com>
To: Clifford Heath <clifford.heath@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Network hangs with 2.6.30.5
Date: Tue, 01 Sep 2009 12:47:46 +0200 [thread overview]
Message-ID: <4A9CFBD2.2050206@gmail.com> (raw)
In-Reply-To: <7D2F0769-2994-4BB8-B107-DEF2B1346B3A@gmail.com>
Clifford Heath a écrit :
> I sent this email last Friday, but received no response.
>
> As far as I can see, some recent work in the stable
> Linux kernel has broken the TCP stack, at least on my
> (pretty common) hardware. Can anyone confirm that
> they've seen and perhaps fixed similar symptoms, or
> at least tell me what else I need to do to help them
> identify the problem?
>
> I recently upgraded my Debian system (a Dell Optiplex GX270) from a
> 2.6.16.11 kernel to a 2.6.30.5 one (current stable). My networking is
> now misbehaving. If I could revert to an earlier kernel, I would (and
> did, it worked), but now I can't because of the glibc version change;
> the old kernel panics on startup. This leaves me with a *broken
> computer* which I cannot use for my regular work, and cannot afford to
> completely re-install.
>
> POP, IMAP, and NNTP connect ok (multiple packets each way, viewed using
> a logging proxy; no tcpdump but I can get one for you) but as soon as a
> message should start coming down, the connection hangs and then times
> out. I think it's the first large packet that causes this, and I saw
> that the net team have been working on some features to increase
> throughput through read aggregation or something... Whatever it is, it's
> clearly broken (on my hardware at least).
>
> My kernel .config file and the output of "lspci" are included below.
> Thanks for any help you can give. Let me know if you need more information.
>
You could provide a tcpdump for example, and tell us which way is broken
(your machine receiving a big packet, or sending a big packet)
You might try to change /proc/sys/net/ipv4/tcp_ecn to 0
echo 0 >/proc/sys/net/ipv4/tcp_ecn
You might try to change device settings
ethtool -K eth0 sg off
and various settings as well (tso, gso ...)
next prev parent reply other threads:[~2009-09-01 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 9:50 Network hangs with 2.6.30.5 Clifford Heath
2009-09-01 10:47 ` Eric Dumazet [this message]
2009-09-01 11:20 ` Ben Hutchings
2009-09-01 14:17 ` Holger Hoffstaette
2009-09-01 15:32 ` Holger Hoffstaette
2009-09-03 7:46 ` Jarek Poplawski
2009-09-03 19:20 ` Holger Hoffstaette
2009-09-03 19:27 ` Eric Dumazet
2009-09-03 19:55 ` Holger Hoffstaette
2009-09-07 7:21 ` Jarek Poplawski
2009-09-10 22:41 ` Clifford Heath
2009-10-01 22:49 ` David Miller
2009-10-02 8:11 ` Ilpo Järvinen
2009-10-02 12:29 ` Ilpo Järvinen
2009-10-02 12:38 ` Eric Dumazet
2009-11-19 23:40 ` David Miller
2009-11-20 12:04 ` Evgeniy Polyakov
2009-11-20 12:09 ` 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=4A9CFBD2.2050206@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=clifford.heath@gmail.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).