From: Jonathan Woithe <jwoithe@atrad.com.au>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 regression: UDP packets dropped intermittantly
Date: Wed, 1 Jun 2016 10:01:23 +0930 [thread overview]
Message-ID: <20160601003123.GE3384@marvin.atrad.com.au> (raw)
In-Reply-To: <20160518065137.GJ27564@marvin.atrad.com.au>
On Wed, May 18, 2016 at 04:21:37PM +0930, Jonathan Woithe wrote:
> On Thu, Apr 07, 2016 at 12:14:18PM +0930, Jonathan Woithe wrote:
> > On Mon, Feb 08, 2016 at 01:03:19PM +1030, Jonathan Woithe wrote:
> > > On Wed, Dec 02, 2015 at 12:58:52AM +0100, Francois Romieu wrote:
> > > > Jonathan Woithe <jwoithe@atrad.com.au> :
> > > > [...]
> > > > > Any thoughts or progress at this stage? Are there further tests you need me
> > > > > to do ?
> > > >
> > > > Yes but you should expect two more days without signal.
> > >
> > > FYI I am now back from annual leave and linux.conf.au. This means I am in
> > > a position to test possible solutions to this problem once you are able to
> > > make them available.
> >
> > Has there been any further progress on this problem? I still have access to
> > the hardware and systems if further tests are required.
>
> To assist in picking up this issue I thought I'd summarise where things are
> at from my perspective.
>
> The problem is that small low-speed UDP packets are being dropped by the
> r8169-based network card in our systems. Git bisect showed that the
> regression started with commit da78dbff2e05630921c551dbbc70a4b7981a8fff.
> :
FYI I have just tested the kernel.org 4.6 kernel and unsurprisingly it still
exhibits the regression.
Is there anything more I can do to move this forward? I really do not want
to limit our systems to old kernels[1] just to avoid this regression, but
that is what I have to do while the regression remains.
Regards
jonathan
[1] We are currently on 2.6.35.11 with some additional device driver patches
we need for our hardware (which have subsequently been merged into
mainline). The regression is present in all kernels starting with 3.3
which means the latest kernel we can use at present is 3.2.x.
next prev parent reply other threads:[~2016-06-01 0:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 6:46 r8169 regression: UDP packets dropped intermittantly Jonathan Woithe
2013-03-11 0:02 ` Francois Romieu
2013-03-11 0:17 ` Jonathan Woithe
2013-03-11 22:18 ` Jonathan Woithe
2013-04-05 0:15 ` Jonathan Woithe
2015-11-17 1:56 ` Jonathan Woithe
2015-11-17 23:21 ` Francois Romieu
2015-11-18 5:09 ` Jonathan Woithe
2015-11-19 0:56 ` Francois Romieu
2015-11-19 6:57 ` Jonathan Woithe
2015-11-19 12:22 ` Eric Dumazet
2015-11-19 21:44 ` Francois Romieu
2015-11-19 21:58 ` Eric Dumazet
2015-11-20 2:46 ` Jonathan Woithe
2015-11-20 22:45 ` Francois Romieu
2015-11-21 22:36 ` Francois Romieu
2015-11-22 22:50 ` Jonathan Woithe
2015-11-22 23:02 ` Francois Romieu
2015-11-23 0:07 ` Jonathan Woithe
2015-11-30 6:42 ` Jonathan Woithe
2015-12-01 23:58 ` Francois Romieu
2016-02-08 2:33 ` Jonathan Woithe
2016-04-07 2:44 ` Jonathan Woithe
2016-05-17 6:52 ` Jonathan Woithe
2016-05-18 6:51 ` Jonathan Woithe
2016-06-01 0:31 ` Jonathan Woithe [this message]
2016-06-21 3:21 ` Jonathan Woithe
2016-06-21 23:09 ` Francois Romieu
2016-06-21 23:59 ` Jonathan Woithe
2016-06-22 23:22 ` Francois Romieu
2016-06-23 8:26 ` Jonathan Woithe
2017-03-24 5:05 ` Jonathan Woithe
2017-11-14 5:39 ` Jonathan Woithe
2015-11-23 0:16 ` Jonathan Woithe
-- strict thread matches above, loose matches on Subject: below --
2017-12-18 5:49 Jonathan Woithe
2017-12-18 13:38 ` Holger Hoffstätte
2017-12-18 22:32 ` Jonathan Woithe
2017-12-19 5:45 ` Jonathan Woithe
2017-12-19 12:25 ` Michal Kubecek
2017-12-20 5:20 ` Jonathan Woithe
2018-01-15 6:56 ` Jonathan Woithe
2018-10-22 0:01 ` Jonathan Woithe
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=20160601003123.GE3384@marvin.atrad.com.au \
--to=jwoithe@atrad.com.au \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 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).