FS#60832 - Linux 4.19.x Breaks My Networking
Attached to Project:
Arch Linux
Opened by Alberto Díaz López (Takuya) - Friday, 16 November 2018, 23:19 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 09 December 2018, 21:27 GMT
Opened by Alberto Díaz López (Takuya) - Friday, 16 November 2018, 23:19 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 09 December 2018, 21:27 GMT
|
Details
Description: Linux 4.19.x breaks networking, i have to
restart a few times to have the network working, but if i
restart again, it brokes again and i have to restart a few
times more. It's a wired network.
Additional info: * package version(s) 4.19.2 * config and/or log files etc. Steps to reproduce: |
This task depends upon
This is my Ethernet network information.
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11).
The motherboard is an ASUS Z97-P. I'm pretty sure that's a problem with the drivers.
I suppose i can't edit the ticket after being opened.
if i launch into an x11 session when the internet is not working the networkmanager icon in kde's system tray will have a yellow icon. if the computer was suspended, on wake the kde networkmanager system tray icon is greyed out.
network card: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
mobo: MSI Z97 PC Mate (MS-7850)
the network card is onboard
not sure what other information to give or where relevant logs would be
note that ive never had to rollback before and i must have fudged it a bit because after rolling back to 4.18.16 x11 would not start so something about video drivers may show up in the 4.18.16 log, but networking was working fine as expected so i assume it is ok
i didnt include 4.19.1 but it has the same issue as 4.19.2. this issue started with 4.19.1 but i waited for 4.19.2 in case that solved my issue
4.18.16 shows
[ 4.281922] r8169 0000:03:00.0 enp3s0: link down
[ 4.281924] r8169 0000:03:00.0 enp3s0: link down
[ 4.281990] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 6.825247] r8169 0000:03:00.0 enp3s0: link up
[ 6.825261] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
4.19.2 bad shows
[ 9.752643] r8169 0000:03:00.0 enp3s0: Link is Down
[ 12.291561] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 12.291576] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 12.956853] r8169 0000:03:00.0 enp3s0: Link is Down
4.19.2 good shows
[ 12.148609] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
Ethernet controller does not wake up from suspend, ip link shows no carrier. Reloading r8169 module appears to fix the problem without rebooting.
I don't have r8169.debug enabled since I'm kinda in a middle of work, but as it stands after resuming from suspend but before reloading the module I have just (skipping other devices)
[37188.676093] r8169 0000:04:00.0 enp4s0: Link is Down
[37189.598093] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
[37189.598497] Generic PHY r8169-400:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
[37189.724585] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
After reloading the module I get
[37293.525027] libphy: r8169: probed
[37293.525329] r8169 0000:04:00.0 eth0: RTL8168g/8111g, 54:e1:ad:8e:5a:76, XID 50900880, IRQ 136
[37293.525331] r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[37293.527475] r8169 0000:04:00.0 enp4s0: renamed from eth0
[37293.550214] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
[37293.550640] Generic PHY r8169-400:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-400:00, irq=IGNORE)
[37293.671789] IPv6: ADDRCONF(NETDEV_UP): enp4s0: link is not ready
[37295.242124] r8169 0000:04:00.0 enp4s0: Link is Up - 100Mbps/Full - flow control rx/tx
[37295.242133] IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
first boot:
[ 4.692198] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 4.693091] r8169 0000:03:00.0 enp3s0: Link is Down
[ 7.225659] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 7.225679] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 9.975526] r8169 0000:03:00.0 enp3s0: Link is Down
reload #1:
[ 327.995292] libphy: r8169: probed
[ 327.995574] r8169 0000:03:00.0 eth0: RTL8168g/8111g, d8:cb:8a:c2:ab:dc, XID 4c000880, IRQ 28
[ 327.995576] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 327.997876] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 328.022015] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 328.022286] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[ 328.148757] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 330.810033] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 330.810044] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 332.225058] r8169 0000:03:00.0 enp3s0: Link is Down
reload #2:
[ 375.725115] libphy: r8169: probed
[ 375.725380] r8169 0000:03:00.0 eth0: RTL8168g/8111g, d8:cb:8a:c2:ab:dc, XID 4c000880, IRQ 28
[ 375.725382] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 375.727315] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 375.761673] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 375.762015] Generic PHY r8169-300:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[ 375.888752] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 378.444944] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 378.444962] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
i have r8169.debug=16 enabled but dont seem to have any extra output
I'll update the status tomorrow.
I just continued using normally the system, but since yesterday evening/night i noted that it's not working again, sometimes it boots everything alright, some other times, it boots with the networking disabled. Looks like it was an error.
How can i cancel the request of task closure?
Tested again on Linux 4.19.4 and the same issues. I also add some dmesg logs when the networking is not working after booting.
4.19.4 Network Not Working After Booting
[ 2.081972] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 2.687627] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 2.815219] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 2.815524] r8169 0000:03:00.0 enp3s0: Link is Down
[ 6.411025] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 6.411036] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
[ 7.467569] r8169 0000:03:00.0 enp3s0: Link is Down
4.19.4 Networking Working Normally After Booting
[ 2.066610] r8169 0000:03:00.0 enp3s0: renamed from eth0
[ 2.587504] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 2.715280] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready
[ 5.585957] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off
[ 5.585970] IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready
There's discussion about this on the LKML:
https://marc.info/?t=154279781800003&r=1&w=2
There's a patch that seems to workaround the issue here:
https://marc.info/?l=linux-kernel&m=154291066330748&w=2
But the root cause is still being investigated/discussed.
Bugzilla entry to keep tabs on too:
https://bugzilla.redhat.com/show_bug.cgi?id=1650984