From: Ben Hutchings <ben@decadent.org.uk>
To: for.poige+bugzilla.kernel.org@gmail.com
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
Jan Beulich <jbeulich@novell.com>,
Neil Horman <nhorman@tuxdriver.com>,
Steffen Klassert <klassert@mathematik.tu-chemnitz.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 28542] New: 3c59x.c: Regression since 2.6.36 (incl.), for e. g., TCP stalls on receive
Date: Tue, 08 Feb 2011 00:39:10 +0000 [thread overview]
Message-ID: <1297125550.2876.21.camel@localhost> (raw)
In-Reply-To: <20110207150919.cd253b97.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On Mon, 2011-02-07 at 15:09 -0800, Andrew Morton wrote:
> On Mon, 7 Feb 2011 18:55:29 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
[...]
> > Dump of kernel source bz2 download being stalled:
> > http://poige.livejournal.com/475372.html#cutid1 (see the bunch of ACKs
> > #5555523).
That's not a stall, that's selective-ACKing (see the ranges listed on
the right of each ACK line).
> > As a workaround I've just replaced drivers/net/3c59x.c with its former
> > (2.6.35.11) version, the connectivity problems are gone now.
This could just be a coincidence. But it could be that packet loss is
now more likely for some reason. Does the rx_fifo_errors statistic
increase quickly with the later version of the driver? (This seems to
be the only receive error type reported.)
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2011-02-08 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-28542-10286@https.bugzilla.kernel.org/>
2011-02-07 23:09 ` [Bugme-new] [Bug 28542] New: 3c59x.c: Regression since 2.6.36 (incl.), for e. g., TCP stalls on receive Andrew Morton
2011-02-08 0:39 ` Ben Hutchings [this message]
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=1297125550.2876.21.camel@localhost \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=for.poige+bugzilla.kernel.org@gmail.com \
--cc=jbeulich@novell.com \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
/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.