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, 18 Nov 2015 15:39:19 +1030 [thread overview]
Message-ID: <20151118050919.GR25216@marvin.atrad.com.au> (raw)
In-Reply-To: <20151117232108.GC3362@electric-eye.fr.zoreil.com>
On Wed, Nov 18, 2015 at 12:21:08AM +0100, Francois Romieu wrote:
> Jonathan Woithe <jwoithe@atrad.com.au> :
> [...]
> > It would be advantageous if we could upgrade this Linux system to a kernel
> > more recent than 2.6.35.11, but that will require a resolution to this
> > problem. Since 2.6.35.11 works while current kernels do not, the only other
> > option is to stick with 2.6.35.11. Is there anything we can do to try to
> > track down the problem? I'm willing and able to run further tests on the
> > system as required.
>
> If you were tracking the hardware stats (ethtool -S), would you be able to
> tell if the hardware sees the relevant UDP packets long before the driver
> does ?
Possibly. The packet flow at the time of fault is quite low so it might be
doable. What would be the best way to approach this? Query "ethtool -S"
regularly around the point of failure?
> Would you be able to ascertain that the interrupt mask register (ethtool -d)
> is not set for an excessive amount of time ?
I could try. What's the most reliable way to determine this? Use regular
ethtool queries about the time of the failures?
Regards
jonathan
next prev parent reply other threads:[~2015-11-18 5:09 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 [this message]
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
-- 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=20151118050919.GR25216@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).