Hello Kleber, or anyone else affected,
Accepted bcmwl into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package
FYI - This bug is for back-porting dwarves and libbpf to focal fixing
support for newer kernels:
https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811
It wont make mainline releases work on focal, but it will again be
possible to compile a kernel using the focal toolchain.
--
You r
Dear Kai-Heng, you seem to hit the point, thank you!
5.13.0-7007 (lp1920674-debug-4) with my "standard" kernel boot parameters seems
to work:
A) no system freeze or crash
B) X acceleration works
C) hibernation still does NOT work
I will keep testing the system stability, dmesg attached.
1) Can
Yes, please promote this dkms update to -security and -updates. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932164
Title:
lime-forensics/1.9-1ubuntu0.2 ADT test fail
Yes, this needs to go to -security as well. The reason is that users
tracking only -security will need to get this update when the default
hwe kernel in focal upgrades to 5.11.
What's the standard way of documenting this on the SRU template?
--
You received this bug notification because you are
I was able to build and load broadcom-sta (6.30.223.271-12ubuntu0.1) in
a focal VM with both generic 5.4 and hwe-5.11 kernels.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/193216
autopkgtests with linux-hwe-5.11 also completed successfully:
amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/amd64/b/broadcom-sta/20210720_094014_cb2c7@/log.gz
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
** Description changed:
[Im
Public bug reported:
[Impact]
Ubuntu-oem-5.10-5.10.0-1027.28 includes some amdgpu patches to support s2idle
feature, but it leads to the white screen while vt switching during booting up.
[Fix]
After bisect the kernel, we need below commit to fix this issue.
0b08c54bb7a37 drm/amd/display: Fix th
** Description changed:
[Impact]
This is a scripted bug report about ADT failures while running bcmwl
tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is
caused by the dep8 tests of the tested source or the kernel has yet to
be determined.
Testing failed on:
Confirmed that bcmwl (6.30.223.271+bdcom-0ubuntu7~20.04.3) in focal-
proposed can be built and loaded with both -generic 5.4 and hwe-5,11
kernels.
Autopkgtests also completed successfully:
* focal/linux:
- amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/2021
** Changed in: linux-intel (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1929901
Title:
[EHL][TGL] EDAC support
Status in int
** Changed in: linux-intel (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1929892
Title:
[TGL] enable USB-dw3
Status in intel:
** Description changed:
-
- [Impact]
+ [Impact]
This is a scripted bug report about ADT failures while running rtl8812au
tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is
caused by the dep8 tests of the tested source or the kernel has yet to
be determined.
T
Public bug reported:
Regardless the true battery charge, any bluetooth connected device (I
have tried with headphones, mouse, joystick) report 100% charge:
$ upower --dump
...
...
Device: /org/freedesktop/UPower/devices/mouse_dev_CC_60_9A_82_E6_F1
native-path: /org/bluez/hci0/dev_CC_6
Confirmed that rtl8812au (4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3)
can be built and loaded on a focal amd64 VM with both -generic 5.4 and
-hwe-5.11 kernels.
Autopkgtests also completed successfully with hwe-5.11:
- amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r
Trying to see if impish u-boot is also broken at the moment.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-risc
$ dpkg-query -W u-boot-qemu
u-boot-qemu 2021.01+dfsg-3ubuntu9.1
$ qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -kernel
/usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -device virtio-net-
device,netdev=eth0 -netdev user,id
Confirmed that xtables-addons (3.9-1ubuntu0.2~20.04.3) can be built and
loaded in a Focal amd64 VM running both -generic 5.4 and -hwe-5.11
kernels.
Autopkgtests also completed successfully with hwe-5.11:
amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/x/xtables-addons
Impish is not affected, as it still skips fdtdir under qemu completely.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in
Oh https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu9.1
is an orphan, as it did not make it into impish.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
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/18
Could be similar to lp:1899465
--
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/1836694
Title:
memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with
Bionic
Status in ubuntu
https://www.infobrez.com/attendance-management-software
https://www.infobrez.com/attendance-management-software
--
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/1690085
Title:
Ryzen 1800X
Thanks for raising this question, myself too face the same.
https://www.infobrez.com/Payroll-software
--
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/1690085
Title:
Ryzen 1800X freeze - r
The verification of the Stable Release Update for dahdi-linux has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
This bug was fixed in the package dahdi-linux - 1:2.11.1~dfsg-1ubuntu6.3
---
dahdi-linux (1:2.11.1~dfsg-1ubuntu6.3) focal; urgency=medium
* Non-maintainer upload.
* Backported from Hirsute 1:2.11.1~dfsg-1ubuntu8 (LP: #1932161)
- Fix FTBFS with Linux 5.10
- Added Linux-5.9-
The verification of the Stable Release Update for lime-forensics has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you enco
This bug was fixed in the package lime-forensics - 1.9-1ubuntu0.3
---
lime-forensics (1.9-1ubuntu0.3) focal; urgency=medium
* Non-maintainer upload.
* Backported from Hirsute 1.9.1-2 (LP: #1932164)
- debian/patches/10_fix_5.10.patch: created to fix build and install for
Here's a patch that should fix the build issue on s390x (or more in
general on all systems that don't have USB support enabled).
** Patch added: "evdi-support-usbless-systems.debdiff"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+attachment/5512245/+files/evdi-support-usbless-sy
Logs:
[ 594.291317] ACPI: Hardware changed while hibernated, success doubtful!
[ 594.411609] BUG: kernel NULL pointer dereference, address: 01f4
[ 594.424658] #PF: supervisor write access in kernel mode
[ 594.424660] #PF: error_code(0x0002) - not-present page
[ 594.424661] PGD 0 P4
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux-oracle - 5.11.0-1013.14
---
linux-oracle (5.11.0-1013.14) hirsute; urgency=medium
[ Ubuntu: 5.11.0-25.27 ]
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oracle (5.11.0-1012.12) hirsute; urgen
This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux-azure - 5.4.0-1055.57
---
linux-azure (5.4.0-1055.57) focal; urgency=medium
[ Ubuntu: 5.4.0-80.90 ]
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-azure (5.4.0-1054.56) focal; urgency=medium
This bug was fixed in the package linux - 5.4.0-80.90
---
linux (5.4.0-80.90) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.4.0-79.88) focal; urgency=medium
* focal/linux: 5.4.0-79.88 -proposed tracker (LP:
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux - 5.4.0-80.90
---
linux (5.4.0-80.90) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.4.0-79.88) focal; urgency=medium
* focal/linux: 5.4.0-79.88 -proposed tracker (LP:
This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.4.0-80.90
---
linux (5.4.0-80.90) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.4.0-79.88) focal; urgency=medium
* focal/linux: 5.4.0-79.88 -proposed tracker (LP:
This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux - 5.4.0-80.90
---
linux (5.4.0-80.90) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.4.0-79.88) focal; urgency=medium
* focal/linux: 5.4.0-79.88 -proposed tracker (LP:
This bug was fixed in the package linux - 5.11.0-25.27
---
linux (5.11.0-25.27) hirsute; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.11.0-24.25) hirsute; urgency=medium
* test_pmtu_vti4_link_add_mtu() test from
This bug was fixed in the package linux - 5.4.0-80.90
---
linux (5.4.0-80.90) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (5.4.0-79.88) focal; urgency=medium
* focal/linux: 5.4.0-79.88 -proposed tracker (LP:
This bug was fixed in the package linux - 5.8.0-63.71
---
linux (5.8.0-63.71) groovy; urgency=medium
* Possible io_uring regression with QEMU on Ubuntu's kernel (LP: #1935017)
- SAUCE: Revert "block: don't ignore REQ_NOWAIT for direct IO"
linux (5.8.0-62.70) groovy; urgency=med
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
This bug was fixed in the package linux - 4.15.0-151.157
---
linux (4.15.0-151.157) bionic; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux (4.15.0-150.155) bionic; urgency=medium
* bionic/linux: 4.15.0-150.155 -propos
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1009.10
---
linux-oem-5.13 (5.13.0-1009.10) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1038.40
---
linux-oem-5.10 (5.10.0-1038.40) focal; urgency=medium
* CVE-2021-33909
- SAUCE: seq_file: Disallow extremely large seq buffer allocations
linux-oem-5.10 (5.10.0-1037.38) focal; urgency=medium
* focal/linux
Public bug reported:
Jul 20 14:40:23 anonster kernel: [ 1716.692818] mlx5_core :03:00.0:
assert_var[0] 0x
Jul 20 14:40:23 anonster kernel: [ 1716.698541] mlx5_core :03:00.0:
assert_var[1] 0x
Jul 20 14:40:23 anonster kernel: [ 1716.704240] mlx5_core :03:00.0:
assert_v
FYI, that patch is intended specifically for s2idle, which will not work
on those older kernels without significant other backports. Are you
sure that this patch alone really helps the issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
> 1) Can you please briefly explain what the problem was?
Patch with explanation:
https://lore.kernel.org/lkml/20210720172216.59613-1-kai.heng.f...@canonical.com/
> 2) Will your patch be backported to the 5.4 and 5.8 lines?
It should be automatically picked to any stable kernel.
5.8 is EOL soon BT
The verification passed for focal. The daily images are building with
u-boot-menu-4.0.2ubuntu5~20.04.1. I have successfully booted these daily
images in qemu and Unmatched hardware.
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-29-generic riscv64)
* Documentation: https://help.ubuntu.com
* Ma
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.1
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubuntu0.20.10.1) groovy;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.144-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-390 (390.144-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop buildfix_kernel_5.13.
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubuntu0.20.04.1) focal;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.211.00-0ubunt0.21.04.1
---
nvidia-graphics-drivers-418-server (418.211.00-0ubunt0.21.04.1) hirsute;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.142.00-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-450-server (450.142.00-0ubuntu0.21.04.1) hirsute;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Dro
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu0.20.10.1) groovy; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
12:48:27 +0200
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu0.21.04.1) hirsute; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
12:46:59 +0200
** Changed in
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.142.00-0ubuntu0.20.10.1
---
nvidia-graphics-drivers-450-server (450.142.00-0ubuntu0.20.10.1) groovy;
urgency=medium
* New upstream release (LP: #1933980).
* debian/templates/dkms_nvidia.conf.in:
- Drop
This bug was fixed in the package nvidia-graphics-drivers-460 -
460.91.03-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-460 (460.91.03-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1933980).
-- Alberto Milone Fri, 09 Jul 2021
12:53:30 +0200
** Changed in:
1 - 100 of 161 matches
Mail list logo
