Ubuntu 20.10 (Groovy Gorilla) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
On 04.11.2023 18:01, frank wrote:
> hi, i have the same on ubuntu 22.4 / kernel 6.2.0-35
>
> [Sa Nov 4 16:05:18 2023] [ cut here ]
> [Sa Nov 4 16:05:18 2023] NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0
> timed out
> [Sa Nov 4 16:05:18 2023] WARNING: CPU: 4 PID: 0
hi, i have the same on ubuntu 22.4 / kernel 6.2.0-35
[Sa Nov 4 16:05:18 2023] [ cut here ]
[Sa Nov 4 16:05:18 2023] NETDEV WATCHDOG: enp3s0 (r8169): transmit queue 0
timed out
[Sa Nov 4 16:05:18 2023] WARNING: CPU: 4 PID: 0 at net/sched/sch_generic.c:525
dev_watchdog+0
Hi,
I am facing the same problem in Focal, but not with the onboard
TL8111/8168/8411 PCI Express Gigabit Ethernet Controller, but with the
USB 3.0 one I have (SIX Electronics Corp. AX88179 Gigabit Ethernet):
[ cut here ]
[94104.121581] NETDEV WATCHDOG: waneth (ax88179_178
Probably you need to hack BIOS code to keep monitoring clkreq# as an
interrupt.If not possible,I believe you can capture it by the Scope.
--
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/1874
Bruce, how do you observe APSM L1 residency? I'd like to do the same.
--
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 time
Inadvertently,I found Realtek NIC came in and out of the aspm L1 state
in an unreasonably high frequency even during downloading something.For
a NVME device,it does not show this symptom during it's working and
having workloads in flight which can be indicated by monitoring clkreq#
being asserted/d
The distro kernel also needs to think of laptop power consumption, so we
need to enable ASPM by default to achieve maximum battery life.
So it's a choice between keep the blacklist in the distro kernel or in a
distro udev rule file.
Let me think about it...
--
You received this bug notification
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 sta
Is it possible to defaults to ASPM enabled, and disable ASPM in
rtl8169_tx_timeout()?
--
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): trans
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 Kernel
Pack
I mean keep the default ASPM L0/L1 set by PCI, and create a blacklist in
r8169.
--
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 qu
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Heiner, can we use something like DMI-based blacklist in the r8169
driver? Whitelist doesn't scale that well...
--
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 WATCH
If problem happens on certain platform,SOC/BIOS/NIC chipset are
something we know of,which combination of them causing the issue could
also be known by regression test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Forgot to mention this problem also exists in hirsute with
5.11.0-7620-generic.
--
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 qu
I just want to share a quick observation related to this bug. I've
noticed that when there is a kernel update and doing a soft-reboot, this
problem shows up. When this occurs, I do a soft-shutdown and power up
and the problem is resolved.
--
You received this bug notification because you are a me
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 component
I could see this issue with same Call trace pasted above with ubuntu
20.04/20.10/21.04.
Had a look at relevant kernel code and found all of them disable only ASPM L1.1
rather than ASPM completely.Rebuilt the kernel by disabling whole ASPM feature
this NETDEV WATCHDOG call trace disappears.
code
Trace from that mainline kernel:
kernel: [ cut here ]
kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
kernel: WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:442
dev_watchdog+0x24c/0x250
kernel: Modules linked in: scsi_transport_iscsi binfmt_misc veth
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.
--
Y
Subscribe r8169 maintainer Heiner Kallweit...
--
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 p
Hi Kai-Heng,
Here is the (much longer) trace from that kernel.
Thanks!
kernel: [ cut here ]
kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
kernel: WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:442
dev_watchdog+0x24c/0x250
kernel: Modules linked
Dan, let's try latest mainline kernel again:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10-rc2/amd64/
... and report the issue to upstream if issue persists.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
Dan,
Given that it's a kernel regression, would it be possible to try mainline
kernel and do a kernel bisection if issue persists?
--
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
T
Still seeing this with that kernel:
kernel: [ cut here ]
kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
kernel: WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:442
dev_watchdog+0x25b/0x270
kernel: Modules linked in: xt_comment iptable_mangle iptable_
Sorry, I pasted the wrong link, here it is:
https://people.canonical.com/~khfeng/lp1874464/
--
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):
I'd like to add that I'm seeing this with Groovy as well:
Oct 26 19:08:40 ubuntu kernel: [ cut here ]
Oct 26 19:08:40 ubuntu kernel: NETDEV WATCHDOG: enp3s0 (r8169): transmit queue
0 timed out
Oct 26 19:08:40 ubuntu kernel: WARNING: CPU: 6 PID: 0 at
net/sched/sch_generic.
On Fri, Oct 16, 2020 at 03:05:09AM -, Kai-Heng Feng wrote:
> Can you please test this kernel:
> https://people.canonical.com/~khfeng/lp1896576/
Thanks for the kernel! Still seeing this, unfortunately:
kernel: [ cut here ]
kernel: NETDEV WATCHDOG: enp5s0 (r8169): trans
Can you please test this kernel:
https://people.canonical.com/~khfeng/lp1896576/
--
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 q
Actually, looks like I spoke too soon. I just upgraded to
5.8.0-22-generic and I'm seeing the issue still:
Oct 13 10:43:37 surprise kernel: [ cut here ]
Oct 13 10:43:37 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit
queue 0 timed out
Oct 13 10:43:37 surprise k
On Sat, Oct 10, 2020 at 09:01:15PM -, Kai-Heng Feng wrote:
> Dan, it will be great if you can revert workaround [1] and apply
> possible fix [2] to see if it helps.
>
> I guess you no longer see the issue because of the workaround.
>
> [1]
> https://git.launchpad.net/~ubuntu-kernel/ubuntu/+s
Dan, it will be great if you can revert workaround [1] and apply
possible fix [2] to see if it helps.
I guess you no longer see the issue because of the workaround.
[1]
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable/commit/?id=759bc16ddfd4d7f3e195a9662d9d067625b805b6
Oh the workaround actually enables L0s and L1. Please just comment the
line out.
--
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 q
Thanks for the test kernel! I can no longer reproduce this on the most
recent two kernels in groovy (5.8.0-19-generic, 5.8.0-20-generic) nor
with that test kernel.
I think we can mark this Incomplete for groovy too, and I'll respond if
I see this again.
Thanks to you and Kai-Heng for all your he
Could you try this test kernel to see if it helps.
I applied one commit[1] on top of focal kernel master-next branch
https://people.canonical.com/~acelan/bugs/lp1874464
1. https://patchwork.ozlabs.org/project/linux-
pci/patch/20201007132808.647589-1-ian.kuml...@gmail.com/
--
You received this bu
I'm still seeing this issue, and it now sometimes appears on boot
without me having done anything. What can I do to help move this
forward?
--
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/1
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
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 implement
(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 0
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
net/sched/sch_generic.c
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
/home/kernel/COD/linu
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, so
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, so
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 p
> 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:
NETDE
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
(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 ti
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
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 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.
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
S
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 (r8169)
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 (r8169)
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 network
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 00
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 Ubun
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) vboxn
** 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
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
T
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 i
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 sub
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): trans
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:
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: [161
** 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
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 (r8169):
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 0
67 matches
Mail list logo