From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 1e918876 breaks r8169 (linux-3.18+)
Date: Sat, 21 Feb 2015 10:57:33 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.02.21.10.57.33@googlemail.com> (raw)
In-Reply-To: 20150221103104.GA26574@breakpoint.cc
On Sat, 21 Feb 2015 11:31:04 +0100, Florian Westphal wrote:
> Tomas Szepe <szepe@pinerecords.com> wrote:
>> > I tried to reproduce this without success so far on my RTL8168d/8111d device.
>> > I've been running 40 parallel netperf TCP_STREAM tests (1gbit) for the
>> > last 5 hours and so far I saw no watchdog tx timeouts.
>> >
>> > I'll keep this running for a day or so to see if it just takes more time
>> > to trigger.
>>
>> So, how's this coming along? Don't you think the patch should be reverted
>> until the problem is diagnosed/understood/fixed?
>
> Sorry.
>
> David, please consider reverting
>
> 1e918876853aa85435e0f17fd8b4a92dcfff53d6
> (r8169: add support for Byte Queue Limits)
>
> and
>
> 0bec3b700d106a8b0a34227b2976d1a582f1aab7
> (r8169: add support for xmit_more)
>
> I cannot reproduce any hangs (tried for 2days with 40 parallel
> netperfs using both 100mbit and 1gbit receiver).
>
> And I don't see anything wrong with the change either.
> Seems like some revisions of the HW are just dodgy?
>
> I hate giving up, but I have no means to diagnose this any further.
> Even reporter says it doesn't affect all of his r8169 nics.
>
> So I think the change is correct per se, but might be revealing some
> HW/firmware bug.
Florian,
have you experimented with offload settings? The only times r8169 seems to
hiccup is with sg/tso enabled. I've reverted my NIC settings back to mostly
defaults (which does not enable sg/tso) and had no hangs, spurious timeouts
or other problems ever since, despite BQL, xmit_more and client/server
use for 24/7.
Tomas never said whether his setup enabled any offload settings; it's not
inconceivable that a distribution might try to automatically "optimize"
things.
-h
next prev parent reply other threads:[~2015-02-21 10:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 10:08 1e918876 breaks r8169 (linux-3.18+) Tomas Szepe
2015-02-03 10:42 ` Florian Westphal
2015-02-05 16:56 ` Tomáš Szépe
2015-02-06 14:04 ` Tomas Szepe
2015-02-08 12:18 ` Holger Hoffstätte
2015-02-10 15:45 ` Florian Westphal
2015-02-11 9:46 ` Tomáš Szépe
2015-02-21 10:15 ` Tomas Szepe
2015-02-21 10:31 ` Florian Westphal
2015-02-21 10:57 ` Holger Hoffstätte [this message]
2015-02-21 16:22 ` Eric Dumazet
2015-02-21 17:46 ` Florian Westphal
2015-02-21 18:09 ` Eric Dumazet
2015-02-21 18:32 ` Florian Westphal
2015-02-21 19:26 ` Tomas Szepe
2015-02-21 19:05 ` Tomas Szepe
2015-02-21 19:54 ` Eric Dumazet
2015-02-22 0:41 ` Tomas Szepe
2015-02-22 20:57 ` David Miller
[not found] <E1YqR6a-0007T7-Dz@feisty.vs19.net>
2015-05-07 19:22 ` Daniel Exner
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=pan.2015.02.21.10.57.33@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=linux-kernel@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 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.