LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Florian Westphal <fw@strlen.de>,
	Francois Romieu <romieu@fr.zoreil.com>,
	Hayes Wang <hayeswang@realtek.com>,
	Eric Dumazet <edumazet@google.com>,
	Tom Herbert <therbert@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	Marco Berizzi <pupilla@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: 1e918876 breaks r8169 (linux-3.18+)
Date: Tue, 3 Feb 2015 11:08:16 +0100	[thread overview]
Message-ID: <20150203100816.GA5807@louise.pinerecords.com> (raw)

Hi,

Since linux-3.18.0, r8169 is having problems driving one of my add-on
PCIe NICs.  The interface is losing link for several seconds at a time,
the frequency being about once a minute when the traffic is high.

The first loss of link is accompanied by the message "NETDEV WATCHDOG:
eth1 (r8169): transmit queue 0 timed out" and a call trace, while
subsequent occurrences only report "r8169 0000:01:00.0 eth1: link up"
(w/o the complementary "link down" message).

I've traced the culprit down to commit 1e918876, "r8169: add support
for Byte Queue Limits" by Florian Westphal <fw@strlen.de>.  Reverting
the patch appears to fix the problem on linux-3.18.5.

The same issue might already have been reported by Marco Berizzi here:
http://lkml.org/lkml/2014/12/11/65

The NIC is:
01:00.0 0200: 10ec:8168 (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller) (rev 01)
	Subsystem: 10ec:8168 (Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller)
	Flags: bus master, fast devsel, latency 0, IRQ 27
	I/O ports at e000 [size=256]
	Memory at f7d00000 (64-bit, non-prefetchable) [size=4K]
	Expansion ROM at f7d20000 [disabled] [size=128K]
	Capabilities: [40] Power Management version 2
	Capabilities: [48] Vital Product Data
	Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+
	Capabilities: [60] Express Endpoint, MSI 00
	Capabilities: [84] Vendor Specific Information: Len=4c <?>
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [12c] Virtual Channel
	Capabilities: [148] Device Serial Number 98-2d-00-00-10-ec-81-68
	Capabilities: [154] Power Budgeting <?>

Best regards,
-- 
Tomas Szepe <szepe@pinerecords.com>

             reply	other threads:[~2015-02-03 10:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 10:08 Tomas Szepe [this message]
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
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=20150203100816.GA5807@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=hayeswang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pupilla@hotmail.com \
    --cc=romieu@fr.zoreil.com \
    --cc=therbert@google.com \
    --subject='Re: 1e918876 breaks r8169 (linux-3.18+)' \
    /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

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).