R8169 flaky again?

General system Kernel & Hardware
1

So once again my network stopped in the middle of work. Journalctl shows:

Jul 10 11:25:57 onyx-pc kernel: ------------[ cut here ]------------
Jul 10 11:25:57 onyx-pc kernel: NETDEV WATCHDOG: eno2 (r8169): transmit queue 0 timed out 5912 ms
Jul 10 11:25:57 onyx-pc kernel: WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x2b2/0x2c0
Jul 10 11:25:57 onyx-pc kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) r8169 realtek mdio_devres libphy btrfs blake2b_generic xor raid6_pq libcrc32c snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_cadence snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils soundwire_generic_allocation soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core intel_tcc_cooling snd_soc_sst_ipc x86_pkg_temp_thermal snd_soc_sst_dsp intel_powerclamp snd_soc_acpi_intel_match coretemp snd_soc_acpi snd_soc_core kvm_intel squashfs vfat fat snd_compress iwlmvm btusb kvm i915 hid_multitouch btrtl irqbypass mac80211 btbcm ac97_bus ee1004 snd_pcm_dmaengine btintel iTCO_wdt btmtk intel_pmc_bxt rapl bluetooth hid_microsoft joydev mousedev ff_memless ecdh_generic mei_hdcp mei_pxp eeprom iTCO_vendor_support intel_rapl_msr libarc4 snd_hda_codec_hdmi drm_buddy intel_cstate i2c_algo_bit
Jul 10 11:25:57 onyx-pc kernel:  iwlwifi snd_hda_intel processor_thermal_device_pci_legacy ttm spi_nor snd_intel_dspcfg processor_thermal_device snd_intel_sdw_acpi drm_display_helper processor_thermal_rfim snd_hda_codec intel_uncore asus_nb_wmi mtd pcspkr wmi_bmof mxm_wmi acpi_cpufreq processor_thermal_mbox cfg80211 i2c_i801 cec processor_thermal_rapl snd_hda_core mei_me i2c_smbus intel_lpss_pci intel_rapl_common intel_gtt intel_lpss i2c_hid_acpi snd_hwdep mei intel_soc_dts_iosf intel_pch_thermal idma64 i2c_hid int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_tad acpi_pad mac_hid vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) pkcs8_key_parser snd_aloop snd_pcm snd_timer snd soundcore v4l2loopback_dc(OE) videodev mc sg crypto_user loop fuse bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 hid_asus asus_wmi ledtrig_audio sparse_keymap platform_profile rfkill hid_logitech_hidpp hid_logitech_dj usbhid dm_crypt cbc encrypted_keys trusted asn1_encoder tee dm_mod crct10dif_pclmul crc32_pclmul serio_raw
Jul 10 11:25:57 onyx-pc kernel:  crc32c_intel atkbd polyval_clmulni libps2 polyval_generic vivaldi_fmap gf128mul ghash_clmulni_intel sha512_ssse3 nvme aesni_intel crypto_simd spi_intel_pci xhci_pci nvme_core spi_intel cryptd nvme_common xhci_pci_renesas i8042 video serio wmi [last unloaded: libphy]
Jul 10 11:25:57 onyx-pc kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: P           OE      6.4.2-zen1-1-zen #1 15beba18fcc845d3cdda7d868aeee3f23302845b
Jul 10 11:25:57 onyx-pc kernel: Hardware name: ASUSTeK COMPUTER INC. ROG Strix G531GT/G531GT, BIOS G531GT.308 02/01/2021
Jul 10 11:25:57 onyx-pc kernel: RIP: 0010:dev_watchdog+0x2b2/0x2c0
Jul 10 11:25:57 onyx-pc kernel: Code: fe ff ff 48 89 ef c6 05 a8 c0 45 01 01 e8 c6 87 f9 ff 45 89 f8 44 89 f1 48 89 ee 48 89 c2 48 c7 c7 78 40 2b a4 e8 6e 51 35 ff <0f> 0b e9 b4 fe ff ff 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90
Jul 10 11:25:57 onyx-pc kernel: RSP: 0018:ffffab9c40280e58 EFLAGS: 00010286
Jul 10 11:25:57 onyx-pc kernel: RAX: 0000000000000000 RBX: ffff8d7aa39a441c RCX: 0000000000000027
Jul 10 11:25:57 onyx-pc kernel: RDX: ffff8d81ddb616c8 RSI: 0000000000000001 RDI: ffff8d81ddb616c0
Jul 10 11:25:57 onyx-pc kernel: RBP: ffff8d7aa39a4000 R08: 0000000000000001 R09: 00000000ffffffea
Jul 10 11:25:57 onyx-pc kernel: R10: ffffffffa4a5ad40 R11: ffffffffa4ab2d40 R12: ffff8d7aa39a44c8
Jul 10 11:25:57 onyx-pc kernel: R13: ffff8d7a82436a00 R14: 0000000000000000 R15: 0000000000001718
Jul 10 11:25:57 onyx-pc kernel: FS:  0000000000000000(0000) GS:ffff8d81ddb40000(0000) knlGS:0000000000000000
Jul 10 11:25:57 onyx-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 10 11:25:57 onyx-pc kernel: CR2: 000017e400378000 CR3: 000000051b620003 CR4: 00000000003706e0
Jul 10 11:25:57 onyx-pc kernel: Call Trace:
Jul 10 11:25:57 onyx-pc kernel:  <IRQ>
Jul 10 11:25:57 onyx-pc kernel:  ? __warn+0x81/0x1b0
Jul 10 11:25:57 onyx-pc kernel:  ? dev_watchdog+0x2b2/0x2c0
Jul 10 11:25:57 onyx-pc kernel:  ? report_bug+0x202/0x270
Jul 10 11:25:57 onyx-pc kernel:  ? handle_bug+0x3c/0x80
Jul 10 11:25:57 onyx-pc kernel:  ? exc_invalid_op+0x19/0xc0
Jul 10 11:25:57 onyx-pc kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jul 10 11:25:57 onyx-pc kernel:  ? dev_watchdog+0x2b2/0x2c0
Jul 10 11:25:57 onyx-pc kernel:  ? dev_watchdog+0x2b2/0x2c0
Jul 10 11:25:57 onyx-pc kernel:  ? __pfx_dev_watchdog+0x10/0x10
Jul 10 11:25:57 onyx-pc kernel:  call_timer_fn+0x24/0x130
Jul 10 11:25:57 onyx-pc kernel:  run_timer_softirq+0x407/0xac0
Jul 10 11:25:57 onyx-pc kernel:  ? __pfx_dev_watchdog+0x10/0x10
Jul 10 11:25:57 onyx-pc kernel:  ? timerqueue_add+0x98/0xb0
Jul 10 11:25:57 onyx-pc kernel:  __do_softirq+0xd1/0x2c8
Jul 10 11:25:57 onyx-pc kernel:  irq_exit_rcu+0xc0/0xf0
Jul 10 11:25:57 onyx-pc kernel:  sysvec_apic_timer_interrupt+0x72/0x90
Jul 10 11:25:57 onyx-pc kernel:  </IRQ>
Jul 10 11:25:57 onyx-pc kernel:  <TASK>
Jul 10 11:25:57 onyx-pc kernel:  asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jul 10 11:25:57 onyx-pc kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x830
Jul 10 11:25:57 onyx-pc kernel: Code: 8a c8 1a ff e8 05 f2 ff ff 8b 53 04 49 89 c6 0f 1f 44 00 00 31 ff e8 53 96 19 ff 45 84 ff 0f 85 c4 02 00 00 fb 0f 1f 44 00 00 <45> 85 ed 0f 88 9e 02 00 00 49 63 f5 4c 89 f2 48 8d 04 76 48 8d 04
Jul 10 11:25:57 onyx-pc kernel: RSP: 0018:ffffab9c40147e90 EFLAGS: 00000246
Jul 10 11:25:57 onyx-pc kernel: RAX: ffff8d81ddb73f00 RBX: ffff8d81ddb7f500 RCX: 0000000000000000
Jul 10 11:25:57 onyx-pc kernel: RDX: 0000000000000005 RSI: fffffff71633f765 RDI: 0000000000000000
Jul 10 11:25:57 onyx-pc kernel: RBP: 0000000000000004 R08: 0000000000000002 R09: 000000003161f36f
Jul 10 11:25:57 onyx-pc kernel: R10: 0000000000000172 R11: 0000000000000007 R12: ffffffffa4b45fa0
Jul 10 11:25:57 onyx-pc kernel: R13: 0000000000000004 R14: 0000089e148556a1 R15: 0000000000000000
Jul 10 11:25:57 onyx-pc kernel:  cpuidle_enter+0x2d/0x40
Jul 10 11:25:57 onyx-pc kernel:  do_idle+0x1d8/0x230
Jul 10 11:25:57 onyx-pc kernel:  cpu_startup_entry+0x1d/0x20
Jul 10 11:25:57 onyx-pc kernel:  start_secondary+0x12b/0x150
Jul 10 11:25:57 onyx-pc kernel:  secondary_startup_64_no_verify+0x10b/0x10b
Jul 10 11:25:57 onyx-pc kernel:  </TASK>
Jul 10 11:25:57 onyx-pc kernel: ---[ end trace 0000000000000000 ]---
Jul 10 11:25:58 onyx-pc kernel: pcieport 0000:00:1d.6: Data Link Layer Link Active not set in 1000 msec
Jul 10 11:25:58 onyx-pc kernel: r8169 0000:03:00.0 eno2: Can't reset secondary PCI bus, detach NIC

and inxi report:

[onyx@onyx-pc ~]$ inxi -aN
Network:
  Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: Unknown lanes: 63
    link-max: gen: 6 speed: 64 GT/s port: 3000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
[onyx@onyx-pc ~]$ inxi
CPU: 6-core Intel Core i7-9750H (-MT MCP-) speed/min/max: 2149/800/2601 MHz
Kernel: 6.4.2-zen1-1-zen x86_64 Up: 2h 50m Mem: 4869.1/31949.4 MiB (15.2%)
Storage: 2.29 TiB (55.6% used) Procs: 396 Shell: Bash inxi: 3.3.27

So, should I be dropping back to the r8168? Or is there something else afoot?

2

https://bugzilla.kernel.org/show_bug.cgi?id=217596
Upstream code cleanup causes bug for R8169. Numerous reports of this. Solution: recompile kernel with code reversion, or use LTS.

3

This to me is strange because most of us use r8169 kernel module. It is referencing a TP link offboard Ethernet.

Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Micro-Star MSI X570-A PRO driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 27:00.0 chip-ID: 10ec:8168
    class-ID: 0200

It works fine on my hardware.

Screenshot_20230710_175656
Screenshot_20230710_175656699×122 12.9 KB

1 Like
4

Mine usually works too, but it’s random; after 2/3 hours of constant use, it will suddenly drop off, and require reboot. Not optimal :rofl:

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.