This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf: f
This bug was fixed in the package linux - 5.4.0-77.86
---
linux (5.4.0-77.86) focal; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAU
This bug was fixed in the package linux - 5.8.0-59.66
---
linux (5.8.0-59.66) groovy; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SA
This bug was fixed in the package linux - 5.11.0-22.23
---
linux (5.11.0-22.23) hirsute; urgency=medium
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
-
This bug was fixed in the package linux - 5.11.0-20.21+21.10.1
---
linux (5.11.0-20.21+21.10.1) impish; urgency=medium
* impish/linux: 5.11.0-20.21+21.10.1 -proposed tracker (LP: #1930056)
* Packaging resync (LP: #1786013)
- update dkms package versions
[ Ubuntu: 5.11.0-20
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verifica
This patch has been applied to Groovy (20.10) via upstream stable update
(bug 1929132).
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Groovy)
Status: New => Fix Committed
--
You received this bug notification because you a
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag 'verifi
The fix for this bug has been applied to 18.04 Bionic kernel as part of
" Bionic update: upstream stable patchset 2021-05-25" (bug 1929603).
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
Patch came to 20.04/Focal via v5.4.117 stable.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
--
You received this b
Upstream stable patch from 5.11.19 referred to this bug.
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Hirsute)
Status: New => Fix Committed
--
You
I confirm that the situation improved a lot, I'm not getting the error
anymore.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
I've successfully upgraded to 5.11.0-18-generic and removed all
usbcore.quirks kernel parameters; so far everything is working. I'll
test more and I'll update the tags tomorrow appropriately.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
Can you please attach full dmesg with parameter
"usbcore.quirks=17ef:a387:k,17ef:a393:k,17ef:a391:k"?
--
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/1922651
Title:
r8152 tx status -71
S
It did not help, I'm still getting
[ 299.648322] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 300.672037] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 301.695990] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
on kernel 5.11.0-16-generic. As if the USB_QUIRK_NO_LPM quirk is no
longer t
> So, the k option, while improving the situation, doesn't seem to solve
it fully.
Or maybe the new kernel enabled link power management for the "Lenovo
USB3.1 Hub" devices?
The devices in question (excerpt from `lsusb`):
Bus 005 Device 003: ID 17ef:a393 Lenovo USB3.1 Hub
Bus 005 Device 004: ID
Maybe the Lenovo USB3.1 Hub device would benefit from having the 'k'
parameter? I'll try.
--
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/1922651
Title:
r8152 tx status -71
Status in lin
Hold on please, it looks like the bug is back - upon a boot I'm randomly
getting
[ 271.935097] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 272.959356] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 273.983324] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
even though I have the kernel
Oh, I misunderstood you then. Awesome work with the patch, it would be
great to have that directly in the 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/1922651
Title:
r8152 tx s
Right, I wrote on for this issue:
https://lkml.org/lkml/2021/4/12/1112
--
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/1922651
Title:
r8152 tx status -71
Status in linux package in Ubunt
I placed the parameter into /etc/default/grub as follows:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.quirks=17ef:a387:k"
I'm not sure how to create a patch from that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Is it possible to send a kernel patch for it? Thanks!
--
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/1922651
Title:
r8152 tx status -71
Status in linux package in Ubuntu:
Confirmed
B
The "usbcore.quirks=17ef:a387:k" kernel parameter workaround seems to be
working excellent so far!
--
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/1922651
Title:
r8152 tx status -71
Stat
Indeed: the PCI device is controlled by a different kernel driver
(r8169) as shown via lspci -k:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 0e)
Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet
I've seen comments regarding using usbcore.quirks; I'll try
usbcore.quirks=17ef:a387:k in order to disable the link power
management.
--
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/1922651
Okay the network seems to be working so far, this is encouraging, I'll
observe and let you know.
--
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/1922651
Title:
r8152 tx status -71
Status
BUT the Network Manager says "USB Ethernet" for the docking station
ethernet port, so perhaps the PCI device refers to the ethernet "dongle"
which can be attached to the computer? Yes: Network Manager says "PCI
Ethernet Connected" when I plug the cable into the dongle.
Found it:
~> lsusb -t|grep
Interestingly, the card does not seem to act as an USB device, but
rather as a PCI device. That's weird, since the card is located on a
docking station which is connected to the computer via USB. I guess this
is because Thunderbolt-over-USB or similar?
~> lspci|grep -i eth
02:00.0 Ethernet control
I need to correct myself: the card stopped working out of the blue and
started to print Tx status -71 to dmesg. So the statement "network works
perfectly while the computer is turned on" is not true.
Excerpt from the dmesg:
[11284.014421] audit: type=1400 audit(1617704946.490:148): apparmor="DENI
Finally, powering the notebook off (which seemingly also powered the
docking station off) then on after a couple of seconds seem to be
working as a workaround - the network works perfectly while the computer
is turned on.
--
You received this bug notification because you are a member of Kernel
Pa
Trying rmmod r8169 && modprobe r8169 doesn't seem to work:
[ 1273.946335] r8169 :02:00.0: can't disable ASPM; OS doesn't have ASPM
control
[ 1273.964669] libphy: r8169: probed
[ 1273.965172] r8169 :02:00.0 eth0: RTL8168ep/8111ep, 8c:8c:aa:1d:93:ca,
XID 502, IRQ 48
[ 1273.965178] r8169 0
33 matches
Mail list logo
