All autopkgtests for the newly accepted linux-restricted-modules-azure-6.8
(6.8.0-1022.26~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-470/unknown (amd64)
nvidia-graphics-drivers-525-server/unknow
Hi Ben,
I made you a test kernel with the following commit reverted:
ubuntu-jammy-aws: f5be153733b4d3dab31e3660b54660f34ff90584
commit 44c76825d6eefee9eb7ce06c38e1a6632ac7eb7d
Author: Kees Cook
Date: Fri Feb 16 22:25:43 2024 -0800
Subject: x86: Increase brk randomness entropy for 64-bit system
** Description changed:
SRU Justification
[Impact]
* 20.04 Azure CVM (with 5.15 kernel) instances are failing to boot with
high reproducibility
[Fix]
* Clean reverts of the following commits:
* 8bd834015a5e: "UBUNTU: SAUCE: swiotlb: Split up single swiotlb lock"
* 3db34
Please check to see if the kernel is aware of the DisplayPort being
connected (while you have a monitor connected):
grep connected /sys/class/drm/*/status
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug not
You have been subscribed to a public bug:
2 days ago a ran general update from notification.
After I restarted suddenly my External Monitor connected through DisplayPort
did not post. Only the LVDS-1 internal screen. xrandr says DP-1 doesn't exist
# System Details Report
---
## Report details
-
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2096813
Title:
Ubuntu 20.04 confidential VM deployments
Public bug reported:
SRU Justification
[Impact]
* 20.04 Azure CVM (with 5.15 kernel) instances are failing to boot with
high reproducibility
[Fix]
* Clean reverts of the following commits:
* 8bd834015a5e: "UBUNTU: SAUCE: swiotlb: Split up single swiotlb lock"
* 3db34e258474: "UBUNTU: SAUCE: sw
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
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/2043409
there was an update today 5.15.0-131-generic. the issue is still visible
in dmesg.
UBSAN: shift-out-of-bounds in
/build/linux-sUKQ6b/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.389664] shift exponent 64 is too large for 64-bit type 'long long
unsig
All autopkgtests for the newly accepted linux-restricted-modules-gcp
(5.15.0-1076.85) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-525-server/unknown (amd64)
Please visit the excuses page listed below an
Public bug reported:
Raspberry Pi OS is configured with CONFIG_SERIAL_8250_NR_UARTS=5 which
is different to the Ubuntu 24.04 LTS for Raspberry PI
(CONFIG_SERIAL_8250_NR_UARTS=1).
The Broadcom BCM7271 UART uses that one 8250 Serial UART meaning none
are left for user configuration and use. I came
** Also affects: linux-nvidia-6.8 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-nvidia (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-6.8 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-nvid
** Also affects: linux-nvidia-6.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-nvidia-6.8 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubu
This bug was fixed in the package wireless-regdb -
2024.07.04-0ubuntu1~22.04.1
---
wireless-regdb (2024.07.04-0ubuntu1~22.04.1) jammy; urgency=medium
* Backport to jammy (LP: #2073274)
- debian/rules: Continue shipping CRDA regulatory.bin
-- Noah Wager Fri, 13 Sep 2024 11:08
** Changed in: wireless-regdb (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to wireless-regdb in Ubuntu.
https://bugs.launchpad.net/bugs/1906404
Title:
New upstream release 2020.11.
This bug was fixed in the package wireless-regdb -
2024.07.04-0ubuntu1~20.04.1
---
wireless-regdb (2024.07.04-0ubuntu1~20.04.1) focal; urgency=medium
* Backport to focal (LP: #2073274)
- debian/rules: Continue shipping CRDA regulatory.bin
- debian/control: Continue suggestin
This bug was fixed in the package wireless-regdb -
2024.07.04-0ubuntu1~18.04.1
---
wireless-regdb (2024.07.04-0ubuntu1~18.04.1) bionic; urgency=medium
* Backport to bionic (LP: #2073274)
- debian/rules: Continue shipping CRDA regulatory.bin
- debian/control: Continue suggest
This bug was fixed in the package wireless-regdb -
2024.07.04-0ubuntu1~16.04.1
---
wireless-regdb (2024.07.04-0ubuntu1~16.04.1) xenial; urgency=medium
* Backport to xenial (LP: #2073274)
- debian/rules: Continue shipping CRDA regulatory.bin
- debian/control: Continue suggest
This bug was fixed in the package wireless-regdb -
2024.07.04-0ubuntu1~16.04.1
---
wireless-regdb (2024.07.04-0ubuntu1~16.04.1) xenial; urgency=medium
* Backport to xenial (LP: #2073274)
- debian/rules: Continue shipping CRDA regulatory.bin
- debian/control: Continue suggest
The verification of the Stable Release Update for wireless-regdb 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 wireless-regdb -
2024.07.04-0ubuntu1~24.04.1
---
wireless-regdb (2024.07.04-0ubuntu1~24.04.1) noble; urgency=medium
* Backport to noble (LP: #2073274)
-- Noah Wager Fri, 13 Sep 2024 10:33:29
-0700
** Changed in: wireless-regdb (Ubuntu Noble)
** Also affects: linux-nvidia-lowlatency (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-nvidia-lowlatency (Ubuntu)
Status: New => Invalid
** Changed in: linux-nvidia-lowlatency (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notifica
** Also affects: linux-nvidia-lowlatency (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-nvidia-lowlatency (Ubuntu Noble)
Status: Fix Released => Fix Committed
** Changed in: linux-nvidia-lowlatency (Ubuntu Noble)
Assignee: Jacob Martin (jacobmartin) => (unas
** Also affects: linux-nvidia-lowlatency (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-lowlatency (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux
** Also affects: linux-nvidia-lowlatency (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-nvidia-lowlatency (Ubuntu)
Status: New => Fix Committed
** Changed in: linux-nvidia-lowlatency (Ubuntu)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
--
You rece
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
** Changed in: linux-nvidia (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a memb
Can you please be more verbose with the test plan?
How do you confirm that the system is FIPS-enabled? Is this something I
should be able to test myself in a VM? If so, how do I enable "fips-
updates?" What is the failure mode I should see before testing your
proposed version of ubuntu-release-upg
Public bug reported:
I am seeing sporadic (but relatively repeatable) crashes in a g++/QEMU
build environment (building on amd64, targeting arm64) when our Ubuntu
kernel was updated from 6.8.0-1019.21~22.04.1 to 6.8.0-1021.23~22.04.1.
While I am not 100% sure that the kernel is to blame, I do know
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
** Changed in: linux-nvidia (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a memb
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
** Changed in: linux-nvidia (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a memb
** Also affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu)
Status: New => Fix Committed
** Changed in: linux-nvidia (Ubuntu)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
--
You received this bug notification becaus
Could be connected to bug
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-6.8/+bug/2094733, but my issue relates to the 6.11 version line not
6.8 and I'm not sure if it is its own thing or the same underlying issue
"ported" to different minor kernel versions
** Also affects: linux-hwe-
This bug was fixed in the package linux-oem-6.8 - 6.8.0-1020.20
---
linux-oem-6.8 (6.8.0-1020.20) noble; urgency=medium
* noble/linux-oem-6.8: 6.8.0-1020.20 -proposed tracker (LP: #2093506)
* UBSAN: array-index-out-of-bounds in module mt76 in mt76_wcid_cleanup
(LP: #2091077)
This bug is awaiting verification that the linux-gke/5.15.0-1074.80
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-jammy-linux-gke' to 'verification-done-jammy-
linux-gke'. If the pro
This bug is awaiting verification that the linux-gcp/5.15.0-1076.85
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-jammy-linux-gcp' to 'verification-done-jammy-
linux-gcp'. If the pro
This bug was fixed in the package linux - 5.4.0-205.225
---
linux (5.4.0-205.225) focal; urgency=medium
* focal/linux: 5.4.0-205.225 -proposed tracker (LP: #2093621)
* Hold IOPOLL locks when triggering io_uring's deferred work (LP: #2078659) //
CVE-2023-21400
- io_uring:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1013.13
---
linux-oem-6.11 (6.11.0-1013.13) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1013.13 -proposed tracker (LP:
#2093482)
* randomly graphic glitch on some OLED edp panel(amdgpu) (LP: #2094986)
- SAUCE:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1013.13
---
linux-oem-6.11 (6.11.0-1013.13) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1013.13 -proposed tracker (LP:
#2093482)
* randomly graphic glitch on some OLED edp panel(amdgpu) (LP: #2094986)
- SAUCE:
This bug was fixed in the package linux-oem-6.11 - 6.11.0-1013.13
---
linux-oem-6.11 (6.11.0-1013.13) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1013.13 -proposed tracker (LP:
#2093482)
* randomly graphic glitch on some OLED edp panel(amdgpu) (LP: #2094986)
- SAUCE:
Public bug reported:
Using the relatively new Raspberry Pi 5B/16GB model, my SD card doesn't
work without a quirk passed kernel command line. Without the quirk the
logs are full of:
Jan 24 14:32:30 pi5-2 kernel: mmc_cqe_recovery: 3 callbacks suppressed
Jan 24 14:32:30 pi5-2 kernel: mmc0: running
I downgraded to `6.8.0-49-generic` and so far after a night I didn't
unlock to broken main screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2093268
Title:
Main screen
This bug is awaiting verification that the linux-gke/6.8.0-1018.22
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-noble-linux-gke' to 'verification-done-noble-
linux-gke'. If the prob
This bug is awaiting verification that the linux-gkeop/6.8.0-1005.7
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-noble-linux-gkeop' to 'verification-done-noble-
linux-gkeop'. If the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
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/2087687
44 matches
Mail list logo
