From: Jonathan Woithe <jwoithe@atrad.com.au>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: r8169 regression: UDP packets dropped intermittantly
Date: Wed, 20 Dec 2017 15:50:11 +1030 [thread overview]
Message-ID: <20171220052011.GN8641@marvin.atrad.com.au> (raw)
In-Reply-To: <20171219122523.lhavmoxo3ippftyn@unicorn.suse.cz>
On Tue, Dec 19, 2017 at 01:25:23PM +0100, Michal Kubecek wrote:
> On Tue, Dec 19, 2017 at 04:15:32PM +1030, Jonathan Woithe wrote:
> > This clearly indicates that not every card using the r8169 driver is
> > vulnerable to the problem. It also explains why Holger was unable to
> > reproduce the result on his system: the PCIe cards do not appear to suffer
> > from the problem. Most likely the PCI RTL-8169 chip is affected, but newer
> > PCIe variations do not. However, obviously more testing will be required
> > with a wider variety of cards if this inference is to hold up.
>
> The r8169 driver supports many slightly different variants of the chip.
> To identify your variant more precisely, look for a line like
>
> r8169 0000:02:00.0 eth0: RTL8168evl/8111evl at 0xffffc90003135000, d4:3d:7e:2a:30:08, XID 0c900800 IRQ 38
>
> in kernel log.
The PCIe card (the one which works correctly with the current driver) shows
this:
r8169 0000:02:00.0 eth0: RTL8168e/8111e at 0xf862e000, 80:1f:02:45:25:a4,
XID 0c200000 IRQ 30
r8169 0000:02:00.0 eth0: jumbo features [frames: 9200 bytes,
tx checksumming: ko]
The PCI card (Netgear GA311) which is affected by the problem shows this:
r8169 0000:05:01.0 eth1: RTL8110s at 0xf8706800, e0:91:f5:1b:5f:c6,
XID 04000000 IRQ 22
r8169 0000:05:01.0 eth1: jumbo features [frames: 7152 bytes,
tx checksumming: ok]
The system which has shown the regressed behaviour is running a 32-bit
kernel; for various reasons we can't move to a 64-bit kernel at present.
However, I was able to boot this system using Slackware 14.2 install discs,
and therefore test using both 32-bit and 64-bit 4.4.14 kernels. In both
cases the fault was observed within 30 minutes of starting the tests when
the GA311 card was in use. The fault is therefore not specific to 32-bit
environments.
Regards
jonathan
next prev parent reply other threads:[~2017-12-20 5:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 5:49 r8169 regression: UDP packets dropped intermittantly 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 [this message]
2018-01-15 6:56 ` Jonathan Woithe
2018-10-22 0:01 ` Jonathan Woithe
-- strict thread matches above, loose matches on Subject: below --
2013-03-09 6:46 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
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
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=20171220052011.GN8641@marvin.atrad.com.au \
--to=jwoithe@atrad.com.au \
--cc=holger@applied-asynchrony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkubecek@suse.cz \
--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).