This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.14 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-nvidia-6.5' to
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 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-fips' to
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
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-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+fips1 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-azure-fips' to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1027.31 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-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.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-jammy-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.04.1 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-
aws-6.5' to
This bug is awaiting verification that the linux-azure/6.5.0-1013.13
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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-azure' to 'verification-done-jammy-
linux-azure'. If
This bug is awaiting verification that the linux-raspi/5.4.0-1102.114
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-linux-raspi' to 'verification-done-focal-
linux-raspi'. If
This bug was fixed in the package linux - 5.4.0-171.189
---
linux (5.4.0-171.189) focal; urgency=medium
* focal/linux: 5.4.0-171.189 -proposed tracker (LP: #2048282)
* Packaging resync (LP: #1786013)
- [Packaging] remove helper scripts
- [Packaging] update annotations
This bug is awaiting verification that the linux-oracle/5.4.0-1117.126
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-linux-oracle' to 'verification-done-
focal-linux-oracle'.
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug was fixed in the package linux - 5.15.0-94.104
---
linux (5.15.0-94.104) jammy; urgency=medium
* jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777)
* [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
(LP: #2028158)
- device-dax: Fix
This bug is awaiting verification that the linux-
gcp-6.5/6.5.0-1013.13~22.04.1 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-6.5' to
This bug was fixed in the package linux - 6.5.0-17.17
---
linux (6.5.0-17.17) mantic; urgency=medium
* mantic/linux: 6.5.0-17.17 -proposed tracker (LP: #2049026)
* [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
anymore (LP: #2048919)
- [Config]
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+fips1 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-ibm-gt-fips' to
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1047.53 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-intel-iotg' to
Both Lunar (6.2.0-41.42) and Mantic (6.5.0-16.16) successfully verified by the
test plan.
root@ubuntu:~# dmesg -wT
[Wed Jan 10 08:28:27 2024] pci :08:00.0: [1af4:1042] type 00 class 0x01
[Wed Jan 10 08:28:27 2024] pci :08:00.0: reg 0x14: [mem
0x-0x0fff]
[Wed Jan 10
This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.2.0-41.42 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still
Both Focal (5.4.0-171.189) and Jammy (5.15.0-93.103) successfully verified by
the test plan.
root@ubuntu:~# dmesg -wT
[Tue Jan 9 03:23:18 2024] pci :08:00.0: [1af4:1042] type 00 class 0x01
[Tue Jan 9 03:23:18 2024] pci :08:00.0: reg 0x14: [mem
0x-0x0fff]
[Tue Jan 9
This bug is awaiting verification that the linux/5.15.0-93.103 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' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.4.0-171.189 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-linux' to 'verification-done-focal-linux'. If
the problem still
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed
** Description changed:
[Impact]
Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest
kernels >= 6.5 might be broken.
The inconsistency suggests a potential race condition.
[Fix]
Reverting the two specified commits appears to restore reliability.
==
** Description changed:
[Impact]
Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest
kernels >= 6.5 might be broken.
The inconsistency suggests a potential race condition.
[Fix]
Reverting the two specified commits appears to restore reliability.
==
29 matches
Mail list logo