[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
ASPM issues come with quite different symptoms. Sometimes there's just a number of rx_missed errors and performance is significantly reduced, w/o tx timeout. Therefore at least in mainline I'd like to keep ASPM disabled per default. But every user or distro can use sysfs to enable selected ASPM states by using the attributes under /sys/class/net//device/link (provided that BIOS allows OS to control ASPM). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
For mainline that's too risky, because there has been a number of different symptoms of ASPM-related problems. And it would take time to assemble a blacklist, in the meantime users would complain about network problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Blacklist for what? ASPM L1? In mainline this wouldn't be needed because L1 is disabled per default. Downstream this could be an option, of course. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
That's why mainline r8169 disables ASPM completely. Users still have the option to re-enable individual ASPM states per sysfs, but that's at own risk. It's not known why and which combinations of board chipset / BIOS / NIC chipset version have an issue when ASPM L1 is enabled. All three components may contribute, unfortunately Realtek doesn't release errata information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Well, reason could by anything. Most users of this chip version don't have this problem, so it may be the BIOS. Is known meanwhile whether any (mainline) kernel version is fine on this system (so that issue can be bisected)? Also interesting would be whether the issue happens with r8168 too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
In addition you can try to set kernel command line parameter pcie_aspm=off. Or set pcie_aspm.policy=performance. In general it's a tradeoff: Older kernels didn't allow to enable ASPM at all, resulting in less battery life on notebooks. Newer kernels disable ASPM per default, but allow to re-enable it via sysfs. For this however they depend on proper BIOS support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1- This means ASPM sub-state 1.2 is enabled. This should not be the case because the driver disables ASPM at probe time. Also there's no message in dmesg that ASPM can't be controlled by OS. So this might be a BIOS bug. This could also explain why there are not significantly more such reports, as RTL8168h is a very common chip version. Regarding the iperf log it's not clear whether it's rx or tx direction. If client is the system we talk about, then it's tx direction. Please run iperf also with the "-R" option. Please also check with irq cialescing enabled: ethtool -C rx-usecs 200 tx-usecs 200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
The "lspci -vv" output misses the relevant part. Please execute the command as root. The firmware hasn't changed for years, so this should not be the reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880076] Re: ubuntu 20.4 - retransmitts with r8169
Main reason of missed rx packets is ASPM issues. Helpful would be the output of "lspci -vv" to see whether the ASPM L1 sub-states are enabled. What you can also try: - Change ASPM settings in BIOS - Comment out the following in rtl_hw_start_8168h_1: rtl_hw_aspm_clkreq_enable(tp, true); - Play with rx interrupt coalescing (see ethtool -C) I also have a system with RTL8168h and don't face the decribed issue. So it seems to be system-dependent. Appreciated would be a git bisect between last known good and current version. As mentioned before there have been quite some changes to r8169, and manually reverting some of them + testing would be a cumbersome work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880076 Title: ubuntu 20.4 - retransmitts with r8169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load
Changed status to invalid, because issue was caused by a BIOS bug. ** Changed in: linux-signed (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876593 Title: Ethernet not working/Realtek RTL8169 fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load
Interesting. Did you switch off the machine after flashing the updated BIOS (and before re-testing) or did you just reboot? In the latter case this may be an explanation. Often a BIOS initializes certain things on cold boot only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876593 Title: Ethernet not working/Realtek RTL8169 fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load
Typically it helps to do a rmmod r8169 + modprobe r8169 to work around the BIOS
bug.
Maybe also a PHY soft reset helps to make the PHY behave sanely again.
Can you test whether the following fixes the issue for you?
diff --git a/drivers/net/ethernet/realtek/r8169_main.c
b/drivers/net/ethernet/realtek/r8169_main.c
index 8b665f2ec..9b1ad5d45 100644
--- a/drivers/net/ethernet/realtek/r8169_main.c
+++ b/drivers/net/ethernet/realtek/r8169_main.c
@@ -5104,6 +5104,17 @@ static int r8169_mdio_write_reg(struct mii_bus *mii_bus,
int phyaddr,
return 0;
}
+static void rtl_phy_soft_reset(struct rtl8169_private *tp)
+{
+ int i = 30;
+
+ rtl_writephy(tp, MII_BMCR, BMCR_ANENABLE | BMCR_RESET);
+
+ do {
+ msleep(20);
+ } while (rtl_readphy(tp, MII_BMCR) & BMCR_RESET && --i);
+}
+
static int r8169_mdio_register(struct rtl8169_private *tp)
{
struct pci_dev *pdev = tp->pci_dev;
@@ -5123,6 +5134,11 @@ static int r8169_mdio_register(struct rtl8169_private
*tp)
new_bus->read = r8169_mdio_read_reg;
new_bus->write = r8169_mdio_write_reg;
+ /* A BIOS bug causes few boards to report an invalid PHY ID otherwise */
+ if (tp->mac_version == RTL_GIGA_MAC_VER_25 ||
+ tp->mac_version == RTL_GIGA_MAC_VER_26)
+ rtl_phy_soft_reset(tp);
+
ret = devm_mdiobus_register(new_bus);
if (ret)
return ret;
--
2.26.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876593
Title:
Ethernet not working/Realtek RTL8169 fails to load
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load
Seems your BIOS was never updated, see https://www.gigabyte.com/Motherboard/GA-890GPA-UD3H-rev-20/support #support-dl-bios. Versions FD and FE include some LAN fixes. Best update to latest version FF and re-test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876593 Title: Ethernet not working/Realtek RTL8169 fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load
Thanks, this phy_id value is not a valid Realtek PHY ID. You seem to be affected by a known BIOS bug (few Gigabyte boards from 2009/2010 seem to be affected). See here: https://bugzilla.kernel.org/show_bug.cgi?id=202275#c7 Please try to enable "LAN Boot ROM" option in BIOS. ** Bug watch added: Linux Kernel Bug Tracker #202275 https://bugzilla.kernel.org/show_bug.cgi?id=202275 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876593 Title: Ethernet not working/Realtek RTL8169 fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876593] Re: Ethernet not working/Realtek RTL8169 fails to load
Also before the generic PHY driver was loaded as fallback, the actual PHY driver would be RTL8211B. Did you check what the error message says? Do you have r8169.ko and/or realtek.ko in your initramfs? And to be sure: In the good case, please report the PHY ID (search for phy_id under /sys). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876593 Title: Ethernet not working/Realtek RTL8169 fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1876593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873512] Re: Ubuntu 20.04 kernel 5.4.0-24 ethernet RTL810xE stopped working
Few chip versions of RTL810xE missed a dedicated PHY driver. This was fixed in mainline in 5.4.32. Please update your kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873512 Title: Ubuntu 20.04 kernel 5.4.0-24 ethernet RTL810xE stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824038] Re: Network adapter doesn't work after returning from suspend
This sounds more like a platform issue (especially as WiFi seems to be affected too). Few months ago we had something similiar and it turned out to be a problem with Intel PCI bridge code. The only way I see for now is to find a working version and then bisect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824038 Title: Network adapter doesn't work after returning from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
@Steve, there's some resistance amongst kernel maintainers against additional module parameters. Each new parameter increases complexity and makes maintenance harder. Most likely it would result in a NAK when trying to fix an issue with one broken exotic (sorry..) system in the kernel, especially if a userspace workaround is available (disabling MSI via sysfs for the network device). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
Whether other systems suffer from the same MSI-X incompatability we'll know only once I get more such bug reports. So far your report is the only one. You said if MSI-X is enabled it doesn't even boot. Any error message or does it just silently stop? And no, I'm not aware of any way to disable MSI-X only. The kernel treats it as a sub-feature of MSI, therefore functions like pci_dev_msi_enabled() return true if MSI or MSI-X is active for a device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
Good that it's fixed for you. Indeed your BIOS seems to be broken with regard to MSI-X. According to the vendor part of the MAC address your mini PC is some no-name China product? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
One more hint: I found few reports where people had problems (independent of what is being discussed here) with MSI-X when VT-d is disabled in the BIOS. Could you check this as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779817] Re: r8169 no internet after suspending
Apart from switching to a more up-to-date API after this commit MSI-X will be used if available. Maybe your system has a problem with MSI-X. If you keep the commit and just do the following change, does it fix the issue? Replace flags = PCI_IRQ_ALL_TYPES; with flags = PCI_IRQ_LEGACY | PCI_IRQ_MSI; Also it would be important to know which exact chip version you have. Can you provide a full dmesg output? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
