Eu recebi o mesmo erro e resolvi isso recarregando o driver para o dispositivo de rede. Primeiro precisa encontrar o dispositivo pci apropriado:
find /sys/devices -name enp3s0
Eu tenho /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/net/enp3s0
. Em seguida, remova o dispositivo pci e verifique novamente o barramento:
echo 1 >/sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/remove
echo 1 >/sys/devices/pci0000:00/0000:00:1c.2/rescan
Feito, a interface de rede é reinicializada.
Eu obtive o próximo log do kernel:
Apr 17 12:43:55 host kernel: r8169 0000:03:00.0 enp3s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 17 12:43:55 host kernel: r8169 0000:03:00.0 enp3s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 17 12:43:55 host kernel: r8169 0000:03:00.0 (unregistered net_device): rtl_counters_cond == 1 (loop: 1000, delay: 10).
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: reg 0x10: [io 0x0000-0x00ff]
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: reg 0x18: [mem 0x00000000-0x00000fff 64bit]
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit pref]
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: supports D1 D2
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: System wakeup disabled by ACPI
Apr 17 12:44:28 host kernel: i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: BAR 4: assigned [mem 0xf0100000-0xf0103fff 64bit pref]
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: BAR 2: assigned [mem 0xf7d00000-0xf7d00fff 64bit]
Apr 17 12:44:28 host kernel: pci 0000:03:00.0: BAR 0: assigned [io 0xe000-0xe0ff]
Apr 17 12:44:28 host kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Apr 17 12:44:28 host kernel: r8169 0000:03:00.0: irq 29 for MSI/MSI-X
Apr 17 12:44:28 host kernel: r8169 0000:03:00.0 eth0: RTL8168g/8111g at 0xffffc90007ce2000, 80:ee:73:xx:xx:xx, XID 0c000800 IRQ 29
Apr 17 12:44:28 host kernel: r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
Apr 17 12:44:28 host kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Apr 17 12:44:28 host kernel: r8169 0000:03:00.0 enp3s0: link down
Apr 17 12:44:28 host kernel: r8169 0000:03:00.0 enp3s0: link down
Apr 17 12:44:28 host kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
Apr 17 12:44:31 host kernel: r8169 0000:03:00.0 enp3s0: link up
Apr 17 12:44:31 host kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
De outra forma, você pode tentar recarregar o próprio driver, assim: rmmod r8169; modprobe r8169
. Eu não tentei isso porque eu tenho o segundo dispositivo de rede similar me usado para ssh.