NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out

ribcage · 2020-11-10 13:13:45

Hello, I hope you won't kick me out for using Debian 10? It's impossible to register on Debian forums, so I thought maybe someone could help me here. I did consider changing to Devuan though.

So here's the problem, I have a PCI NIC and sometimes in dmesg I get this message:

[245059.532807] ------------[ cut here ]------------
[245059.532813] NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out
[245059.532855] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x1b6/0x1c0
[245059.532857] Modules linked in: tcp_diag udp_diag inet_diag unix_diag msr binfmt_misc hid_generic usbhid hid iTCO_wdt pcspkr iTCO_vendor_support serio_raw intel_rng rng_core evdev sg nfsd auth_rpcgss lm85 nfs_acl hwmon_vid lockd grace parport_pc ppdev sunrpc lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic uas usb_storage fscrypto ecb crypto_simd cryptd aes_i586 sd_mod ata_generic ata_piix libata uhci_hcd ehci_pci ehci_hcd r8169 psmouse usbcore scsi_mod realtek i2c_i801 libphy lpc_ich usb_common button
[245059.532930] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.0-6-686-pae #1 Debian 4.19.67-2
[245059.532931] Hardware name:  /D865PERL                       , BIOS RL86510A.86A.0069.P12.0310231435 10/23/2003
[245059.532936] EIP: dev_watchdog+0x1b6/0x1c0
[245059.532940] Code: 8b 50 3c 89 f8 e8 62 cc 10 00 8b 7e f0 eb a3 89 f8 c6 05 6b 03 93 d2 01 e8 c7 de fc ff 53 50 57 68 c4 3d 85 d2 e8 0e e4 ad ff <0f> 0b 83 c4 10 eb c9 8d 76 00 3e 8d 74 26 00 55 89 e5 57 56 89 d6
[245059.532942] EAX: 0000003b EBX: 00000000 ECX: f6fcb56c EDX: 00000007
[245059.532944] ESI: f68cb2e8 EDI: f68cb000 EBP: f68c1f68 ESP: f68c1f40
[245059.532946] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00210292
[245059.532948] CR0: 80050033 CR2: b7df2530 CR3: 2c784000 CR4: 000006f0
[245059.532950] Call Trace:
[245059.532953]  <SOFTIRQ>
[245059.532960]  ? pfifo_fast_enqueue+0xf0/0xf0
[245059.532965]  call_timer_fn+0x2f/0x130
[245059.532968]  ? pfifo_fast_enqueue+0xf0/0xf0
[245059.532971]  run_timer_softirq+0x3b5/0x400
[245059.532977]  __do_softirq+0xb2/0x275
[245059.532981]  ? __softirqentry_text_start+0x8/0x8
[245059.532986]  call_on_stack+0x45/0x50
[245059.532987]  </SOFTIRQ>
[245059.532991]  ? irq_exit+0xc5/0xd0
[245059.532995]  ? smp_apic_timer_interrupt+0x6c/0x130
[245059.532997]  ? apic_timer_interrupt+0xd5/0xdc
[245059.533000]  ? __cpuidle_text_start+0x8/0x8
[245059.533003]  ? native_safe_halt+0x11/0x20
[245059.533005]  ? default_idle+0x1f/0x150
[245059.533010]  ? arch_cpu_idle+0x12/0x20
[245059.533012]  ? default_idle_call+0x2d/0x30
[245059.533016]  ? do_idle+0x1bf/0x240
[245059.533019]  ? __do_sys_reboot+0x3b/0x210
[245059.533022]  ? cpu_startup_entry+0x65/0x70
[245059.533026]  ? rest_init+0x88/0x8a
[245059.533029]  ? start_kernel+0x446/0x45f
[245059.533032]  ? i386_start_kernel+0xac/0xb0
[245059.533035]  ? startup_32_smp+0x164/0x168
[245059.533038] ---[ end trace e06e3df1061a1cfc ]---

Often I was able to trigger it by initiating a download with wget and nearly maxing out the bandwidth. When I would do it via SSH, the shell would hang for a few seconds, then return some time later. But not always, other times I could seemingly push the link to the max for a long time. It also recently happened with high activity on a BitTorrent client.

Could a BIOS update help? I'm hesitant to do it because the update process is very inconvenient and I've read about issues with later BIOS versions on this board.

A little more info:

root@debian:~# lspci -vvv
...
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI Gigabit Ethernet Controller (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family PCI Gigabit Ethernet NIC
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 22
	Region 0: I/O ports at b800 [size=256]
	Region 1: Memory at ff9ffc00 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at ff9c0000 [disabled] [size=128K]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Kernel driver in use: r8169
	Kernel modules: r8169

Could this have something to do with power management or IRQ? This is the only PCI card on this board.

root@debian:~# ip -d link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0 minmtu 0 maxmtu 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 
2: enp2s1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether (mac removed) brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 60 maxmtu 7152 addrgenmode none numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535

The message in dmesg mentions "[245059.532960] ? pfifo_fast_enqueue+0xf0/0xf0", could I try a different queue algorithm, if that's what it is?

root@debian:~# modinfo r8169
filename:       /lib/modules/4.19.0-6-686-pae/kernel/drivers/net/ethernet/realtek/r8169.ko
firmware:       rtl_nic/rtl8107e-2.fw
firmware:       rtl_nic/rtl8107e-1.fw
firmware:       rtl_nic/rtl8168h-2.fw
firmware:       rtl_nic/rtl8168h-1.fw
firmware:       rtl_nic/rtl8168g-3.fw
firmware:       rtl_nic/rtl8168g-2.fw
firmware:       rtl_nic/rtl8106e-2.fw
firmware:       rtl_nic/rtl8106e-1.fw
firmware:       rtl_nic/rtl8411-2.fw
firmware:       rtl_nic/rtl8411-1.fw
firmware:       rtl_nic/rtl8402-1.fw
firmware:       rtl_nic/rtl8168f-2.fw
firmware:       rtl_nic/rtl8168f-1.fw
firmware:       rtl_nic/rtl8105e-1.fw
firmware:       rtl_nic/rtl8168e-3.fw
firmware:       rtl_nic/rtl8168e-2.fw
firmware:       rtl_nic/rtl8168e-1.fw
firmware:       rtl_nic/rtl8168d-2.fw
firmware:       rtl_nic/rtl8168d-1.fw
license:        GPL
softdep:        pre: realtek
description:    RealTek RTL-8169 Gigabit Ethernet driver
author:         Realtek and the Linux r8169 crew <netdev@vger.kernel.org>
alias:          pci:v00000001d00008168sv*sd00002410bc*sc*i*
alias:          pci:v00001737d00001032sv*sd00000024bc*sc*i*
alias:          pci:v000016ECd00000116sv*sd*bc*sc*i*
alias:          pci:v00001259d0000C107sv*sd*bc*sc*i*
alias:          pci:v00001186d00004302sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv00001186sd00004B10bc*sc*i*
alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*
alias:          pci:v000010FFd00008168sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008168sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008167sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008161sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008136sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008129sv*sd*bc*sc*i*
alias:          pci:v000010ECd00002600sv*sd*bc*sc*i*
alias:          pci:v000010ECd00002502sv*sd*bc*sc*i*
depends:        libphy
retpoline:      Y
intree:         Y
name:           r8169
vermagic:       4.19.0-6-686-pae SMP mod_unload modversions 686 
sig_id:         PKCS#7
signer:         Debian Secure Boot CA
sig_key:        A7:46:8D:EF
sig_hashalgo:   sha256
signature:      78:24:91:CC:A6:D0:5C:2D:EE:3A:FE:32:1D:76:8A:5E:50:BE:93:1B:
		03:8F:21:5E:F9:4A:14:D6:8F:07:D0:7D:12:A5:FE:64:3A:29:A3:87:
		3D:C5:62:F6:C0:68:E0:57:A1:9E:19:20:05:4A:80:63:7B:39:87:6B:
		49:2D:E8:A2:CA:E3:5F:EF:50:8C:B7:16:33:D9:CC:E8:34:AA:80:A0:
		82:DE:E9:6F:2B:C3:39:8A:A3:38:66:D8:8A:A1:E5:08:0B:5F:6F:FD:
		80:54:23:46:EF:96:A8:CE:0E:36:E8:AB:CA:BF:BD:87:19:A7:7D:12:
		20:E6:40:F6:30:72:77:1C:A6:D2:C7:EC:FC:81:17:C1:77:4C:D3:BA:
		0E:F8:44:A6:9D:93:9E:76:9E:C8:8C:D0:89:5B:34:D9:C7:E1:FC:CB:
		CB:63:13:01:14:B3:5A:00:9B:C3:DD:8F:6E:C4:70:62:4E:2C:E0:58:
		43:28:AC:25:72:A2:7B:ED:39:03:B3:AE:F3:AE:53:D9:62:22:3C:ED:
		3C:52:DB:93:0E:0E:DB:EC:F5:58:DF:04:3A:66:D9:B1:69:A2:97:64:
		28:9B:A7:07:62:F2:57:DB:AA:2B:F8:D3:59:2E:B7:D6:68:A0:22:19:
		30:98:D1:5B:C4:59:62:C9:17:57:C7:01:86:6C:9A:B8
parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
parm:           debug:Debug verbosity level (0=none, ..., 16=all) (int)

The second line from the last looks interesting. It says "Unsafe on 32 bit slot" and my slot is 32 bit as far as I know.

Head_on_a_Stick · 2020-11-10 17:02:51

ribcage wrote:

It's impossible to register on Debian forums

Why? What happens when you try? I'm a moderator on the Debian forums so I might be able to help with that and you really shouldn't be posting a Debian problem here.

FWIW you can try the r8168 driver instead and see if that's any more stable:

https://packages.debian.org/buster/r8168-dkms

ribcage · 2020-11-10 17:43:56

Head_on_a_Stick wrote:

ribcage wrote:
It's impossible to register on Debian forums
Why? What happens when you try? I'm a moderator on the Debian forums so I might be able to help with that and you really shouldn't be posting a Debian problem here.
FWIW you can try the r8168 driver instead and see if that's any more stable:
https://packages.debian.org/buster/r8168-dkms

Thank you, I will try that.

I can't register because I am not receiving the verification email for six hours, I tried the re-send button. My mail is yahoo.com. As a side note, the confirmation code while registering is inhumanely difficult to read and SSL is not working.

Head_on_a_Stick · 2020-11-10 17:48:53

ribcage wrote:

I can't register because I am not receiving the verification email for six hours, I tried the re-send button.

Okay, I'll raise the issue with the administrators. We've had another user report the same problem so something must be wrong. Thanks for the feedback.

ribcage wrote:

SSL is not working

The boards have never supported https and they probably never will. It is not a problem unless you use the same password everywhere, which is a stupid thing to do.

ribcage · 2020-11-10 17:53:07

Head_on_a_Stick wrote:

ribcage wrote:
I can't register because I am not receiving the verification email for six hours, I tried the re-send button.
Okay, I'll raise the issue with the administrators. We've had another user report the same problem so something must be wrong. Thanks for the feedback.
ribcage wrote:
SSL is not working
The boards have never supported https and they probably never will. It is not a problem unless you use the same password everywhere, which is a stupid thing to do.

Thank you. To be honest I don't care much about SSL, but may I ask why Debian forums choose not to use it?

Also, r8168-dkms description says "...for RealTek ... Gigabit Ethernet controllers with PCI-Express interface." while mine is PCI, not PCI-Express. Will this driver still work for me? And from what I see, I must compile it myself?

Head_on_a_Stick · 2020-11-10 17:58:29

ribcage wrote:

why Debian forums choose not to use it?

No idea, sorry. The boards are donated by a kind Debian developer so we don't look the gift horse in the mouth, so to speak.

ribcage wrote:

Will this driver still work for me?

Only one way to find out

ribcage wrote:

And from what I see, I must compile it myself?

Installing the package will run the compilation for you.

The officially official Devuan Forum!

#1 2020-11-10 13:13:45

NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out

#2 2020-11-10 17:02:51

Re: NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out

#3 2020-11-10 17:43:56

Re: NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out

#4 2020-11-10 17:48:53

Re: NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out

#5 2020-11-10 17:53:07

Re: NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out

#6 2020-11-10 17:58:29

Re: NETDEV WATCHDOG: enp2s1 (r8169): transmit queue 0 timed out

Board footer