From: VDR User <user.vdr@gmail.com>
To: netdev@vger.kernel.org
Subject: r8169 driver from kernel 5.0 crashing
Date: Sun, 10 Mar 2019 12:02:10 -0700 [thread overview]
Message-ID: <CAA7C2qju6tYKNiLuL96801EvWp6YODONd7a0d5JCu5rWdwXf=g@mail.gmail.com> (raw)
Hi, after updating to kernel 5.0, the nic driver (r8169) has been
crashing whenever I start using heavy traffic on it (for example,
xferring large files to the box across my lan). The destination
harddrive may be sleeping and need to spin-up, or not, but the box
itself does not suspend/hibernate. The nic becomes completely
unresponsive and all connections to the box drop. After what I think
is several minutes, the connection comes back to life. The problem
happens consistently but seemingly not consistently at the same point.
For example, I can xfer a few 4gb files and it will crash at around
2-3gb on the first file. The next time it might not crash until 2-3gb
on the second file.Prior to kernel 5.0 I was using 4.19.12 and this
problem didn't occur. I have since downgraded back to 4.19.12 pending
what response this post gets.
Thanks for any help or assistance on how to proceed!
-Derek
NOTE: I'm not subscribed to this mailing list so please CC me on any replies!
The nic is on-board ECS A75F-A:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Subsystem: Elitegroup Computer Systems RTL8111/8168/8411 PCI
Express Gigabit Ethernet Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at c000 [size=256]
Region 2: Memory at d0004000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at d0000000 (64-bit, prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: r8169
I see the following in the syslog:
[164572.785517] ------------[ cut here ]------------
[164572.785595] NETDEV WATCHDOG: enp4s0 (r8169): transmit queue 0 timed out
[164572.785677] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:461
dev_watchdog+0x1bb/0x1e0
[164572.785730] Modules linked in: snd_hda_codec_realtek
snd_hda_codec_generic snd_hda_codec_hdmi ohci_pci snd_hda_intel
snd_hda_codec snd_hwdep xhci_pci ehci_pci ohci_hcd xhci_hcd ehci_hcd
usbcore usb_common snd_hda_core snd_pcm snd_timer snd soundcore nfsd
auth_rpcgss oid_registry lockd grace sunrpc ip_tables x_tables ipv6
[164572.785807] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.0.0-amd #2
[164572.785842] Hardware name: ECS A75F-A/A75F-A, BIOS 4.6.5 09/14/2011
[164572.785878] EIP: dev_watchdog+0x1bb/0x1e0
[164572.785912] Code: 8b 50 3c 89 f8 e8 3d aa 0a 00 8b 7e f4 eb a4 89
f8 c6 05 e7 1c 6d c1 01 e8 72 4f fd ff 53 50 57 68 78 05 66 c1 e8 25
ad ba ff <0f> 0b 83 c4 10 eb c9 eb 1c 8d b4 26 00 00 00 00 8d b4 26 00
00 00
[164572.785963] EAX: 0000003b EBX: 00000000 ECX: 00000800 EDX: 00000103
[164572.785998] ESI: f4cbc264 EDI: f4cbc000 EBP: f4c99f74 ESP: f4c99f4c
[164572.786033] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210296
[164572.786067] CR0: 80050033 CR2: 020dc000 CR3: 2b80b000 CR4: 00000690
[164572.786102] Call Trace:
[164572.786135] <SOFTIRQ>
[164572.786168] ? qdisc_put_unlocked+0x40/0x40
[164572.786203] call_timer_fn+0x19/0xa0
[164572.786237] run_timer_softirq+0x337/0x380
[164572.786270] ? qdisc_put_unlocked+0x40/0x40
[164572.786302] ? rcu_process_callbacks+0xcb/0x380
[164572.786337] __do_softirq+0xd6/0x21c
[164572.786370] ? __irqentry_text_end+0x18/0x18
[164572.786404] call_on_stack+0x10/0x60
[164572.786435] </SOFTIRQ>
[164572.786467] ? irq_exit+0x91/0xc0
[164572.786495] ? smp_apic_timer_interrupt+0x56/0xa0
[164572.786525] ? apic_timer_interrupt+0xd5/0xdc
[164572.786555] ? acpi_idle_enter_s2idle+0x60/0x60
[164572.786584] ? cpuidle_enter_state+0x122/0x360
[164572.786614] ? tick_nohz_idle_stop_tick+0x27b/0x2a0
[164572.786644] ? cpuidle_enter+0xf/0x20
[164572.786673] ? call_cpuidle+0x1c/0x40
[164572.786701] ? do_idle+0x1e6/0x220
[164572.786730] ? cpu_startup_entry+0x25/0x40
[164572.786758] ? start_secondary+0x1a5/0x220
[164572.786787] ? startup_32_smp+0x15f/0x164
[164572.786816] ---[ end trace 662a5195537dbad8 ]---
next reply other threads:[~2019-03-10 19:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 19:02 VDR User [this message]
2019-03-10 19:35 ` r8169 driver from kernel 5.0 crashing Heiner Kallweit
2019-03-14 3:04 ` VDR User
2019-03-14 6:43 ` Heiner Kallweit
2019-03-14 15:10 ` VDR User
2019-03-14 18:08 ` Heiner Kallweit
2019-03-14 21:36 ` VDR User
2019-03-15 20:09 ` VDR User
2019-03-15 20:26 ` r8169 driver from kernel 5.0 crashing - napi_consume_skb Heiner Kallweit
2019-03-15 20:40 ` Alexander Duyck
2019-03-15 20:46 ` Heiner Kallweit
2019-03-15 22:09 ` Alexander Duyck
2019-03-15 22:27 ` Heiner Kallweit
[not found] ` <b470f0ee6071bded8e78e15e18df14ffbc32cd18.camel@linux.intel.com>
2019-03-16 9:07 ` Heiner Kallweit
2019-03-16 14:38 ` VDR User
2019-03-16 15:10 ` Heiner Kallweit
2019-03-16 17:08 ` Alexander Duyck
2019-03-17 8:25 ` Heiner Kallweit
2019-03-17 11:35 ` Heiner Kallweit
2019-03-17 15:23 ` VDR User
2019-03-17 15:41 ` VDR User
2019-03-17 15:49 ` Heiner Kallweit
2019-03-18 16:17 ` VDR User
2019-03-18 18:36 ` Heiner Kallweit
2019-03-21 19:35 ` VDR User
2019-03-22 19:03 ` Heiner Kallweit
2019-03-22 20:44 ` VDR User
2019-04-04 14:28 ` VDR User
2019-04-04 19:41 ` Heiner Kallweit
2019-04-04 22:11 ` VDR User
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='CAA7C2qju6tYKNiLuL96801EvWp6YODONd7a0d5JCu5rWdwXf=g@mail.gmail.com' \
--to=user.vdr@gmail.com \
--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).