Re: [Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-09-08 Thread Dan Watkins
On Sat, Sep 05, 2020 at 08:46:51PM -, Kreisch István András wrote: > I'm using a really old kernel with this same error: v3.13.170 with > Ubuntu 14.04.6. I could circumvent the issue by reduce the speed of the > ethernet interface from 1Gb to 100Mb using ethtool. > > ethtool –s eth3 speed 100

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-09-05 Thread Kreisch István András
Hi! I'm using a really old kernel with this same error: v3.13.170 with Ubuntu 14.04.6. I could circumvent the issue by reduce the speed of the ethernet interface from 1Gb to 100Mb using ethtool. ethtool –s eth3 speed 100 duplex full autoneg on Maybe it helps to operate until the fix is

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-09-04 Thread Dan Watkins
(Moved the groovy task back to New, not sure if that's the right process!) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-09-04 Thread Dan Watkins
And this is what I see on 5.9.0-050900rc3-generic: Sep 04 15:05:02 surprise kernel: [ cut here ] Sep 04 15:05:02 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Sep 04 15:05:02 surprise kernel: WARNING: CPU: 0 PID: 0 at

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-09-04 Thread Dan Watkins
I saw this traceback on the 4.15.18 mainline build: Sep 04 14:47:41 surprise kernel: [ cut here ] Sep 04 14:47:41 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Sep 04 14:47:41 surprise kernel: WARNING: CPU: 11 PID: 0 at

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-09-04 Thread Dan Watkins
I just saw this again on 5.8.0-18-generic, and this time I did not manually modify my networking state; I installed the new kernel and rebooted into it, and the problem exhibited immediately. (Fortunately, for whatever reason, a reboot into Windows and back to -18 _has_ come up with networking,

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-09-04 Thread Dan Watkins
I just saw this again on 5.8.0-18-generic, and this time I did not manually modify my networking state; I installed the new kernel and rebooted into it, and the problem exhibited immediately. (Fortunately, for whatever reason, a reboot into Windows and back to -18 _has_ come up with networking,

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-07-06 Thread Kai-Heng Feng
https://wiki.ubuntu.com/Kernel/MainlineBuilds -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-07-06 Thread Dan Watkins
> Possible to try older kernel releases? Like 4.15? I'm happy to try; how would I go about installing them on groovy? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title:

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-07-06 Thread Kai-Heng Feng
Dan, Possible to try older kernel releases? Like 4.15? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-07-06 Thread Dan Watkins
(I'm now running groovy on this system, in case that changes anything.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-07-06 Thread Dan Watkins
I have tested both rc3 and rc4; neither addresses the issue for me. I am seeing a slightly different call trace now though (this is from an rc3 boot): Jul 06 08:44:48 surprise kernel: [ cut here ] Jul 06 08:44:48 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-07-02 Thread Kai-Heng Feng
Would it be possible for you to do a reverse kernel bisection? First, find the first -rc kernel works and the last -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-29 Thread Rene Meier
I tried the mainline kernel and the error is gone. What next? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-29 Thread Kai-Heng Feng
If latest kernel doesn't work then we need to bisect between Bionic kernel and Focal kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-29 Thread Kai-Heng Feng
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-04 Thread Dan Watkins
OK, I just did the following (all on 5.4.0-33-generic): * modified /etc/default/grub to include " pcie_aspm=off" in the kernel command line * `update-grub` * `reboot` * double-checked that "pcie_aspm=off" was in the kernel command line, then booted * once booted and logged in, I disabled

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-04 Thread Dan Watkins
I'll try the command line change after my morning meetings; here's the requested debug output: $ sudo lspci -xxxs 00:01.3 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge 00: 22 10 53 14 07 04 10 00 00 00 04 06 10 00 81 00 10: 00 00 00 00 00 00

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-04 Thread Rene Meier
I can confirm this error on my system after upgrade from bionic to focal. System works "normaly" but error appears in the logs. Adding "pcie_aspm=off" does not help in my case. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-04 Thread Rene Meier
here comes the error: [ 60.259403] [ cut here ] [ 60.259405] NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out [ 60.259416] WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 [ 60.259417] Modules linked in: vboxnetadp(OE)

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-04 Thread AceLan Kao
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Focal) Status: New => Incomplete -- You received this bug notification because you are

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-03 Thread Kai-Heng Feng
Ok, it's LP: #1874464. Does this issue also happen on System76 platforms? In addition to L1.1, does it help if L1.2 gets disabled? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-03 Thread Kai-Heng Feng
Jeremy, the link you provided is the same as this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-03 Thread AceLan Kao
Dan, Please try Kai-Heng's suggestion adding "pcie_aspm=off" to see if it helps If it does, please also attach the following logs 1. sudo lspci -xxxs 00:01.3 2. sudo lspci -xxxs 05:00.0 Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-06-03 Thread Jeremy Soller
I believe https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874464/ is the cause. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169):

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-05-26 Thread Kai-Heng Feng
Can you please test kernel parameter "pcie_aspm=off"? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title:

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-05-26 Thread Nisalon Caje
I have the exact same bug on focal. But it happens randomly to me, while my server is under load. 2 of the servers I migrated to focal have the same issue (not in the same DC), so it excludes a hardware issue from ths particular machine. Here is my syslog May 26 10:04:15 service01K kernel:

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-04-27 Thread You-Sheng Yang
** Tags added: hwe-networking-ethernet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-04-27 Thread Dan Watkins
I'd be happy to assist in debugging this, is there anything I can do to help track it down? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0

[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out

2020-04-23 Thread Dan Watkins
Here are the NetworkManager logs when I first disabled my networking (note that ensp5s0 does get its link up reported correctly, but no traffic seems to go over it): Apr 23 09:42:54 surprise NetworkManager[1281]: [1587649374.1626] manager: disable requested (sleeping: no enabled: yes) Apr 23