This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If th
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~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-
riscv-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-raspi/6.8.0-1009.10
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-raspi' to 'verification-done-noble-
linux-raspi'. If th
This bug is awaiting verification that the linux-azure/6.8.0-1012.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-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If th
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~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-
riscv-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-40.40.1~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-
riscv-6.8' to 'verification-done-jammy-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
Public bug reported:
SRU Justification:
[Impact]
* bpf selftest do not compile. See the error below.
Commit "bpf: Allow reads from uninit stack" introduced the usage of '__failure',
without bringing the commit where this is defined.
This prevents us from running other tests and it also affects t
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2008.8 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-raspi-realtime'
to 'verification-done-noble-li
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Philip Cox (philcox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Changed in: linux-kvm (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2076213
Title:
eventinj ubuntu_kvm_unit_test bionic:oracle-5.4 fla
Public bug reported:
dpkg: error processing package linux-image-6.8.0-40-generic (--configure):
installed linux-image-6.8.0-40-generic package post-installation script
subprocess returned error exit status 11
No apport report written because MaxReports is reached already
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-
lowlatency/6.8.0-40.40.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
--- Comment From fran...@de.ibm.com 2024-08-08 08:52 EDT---
Three additional commits are necessary to allow cherry picking with minimal
effort:
3c724f1a1caa s390: uv: Add offset comments to UV query struct and fix naming
ac640db3a026 s390/uv: Add SE hdr query information
daec8d408308 Docum
** Tags removed: verification-needed-noble-linux-lowlatency
** Tags added: verification-done-noble-linux-lowlatency
--
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/2071889
Title:
a critic
** No longer affects: linux-kvm (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/2076213
Title:
eventinj ubuntu_kvm_unit_test bionic:oracle-5.4 flaky "vec 32/int $33"
Status
Would running https://gist.githubusercontent.com/julian-
klode/85e3f85c410a1b856a93dce77208/raw/488b8509e6f23fe48f917961fe711b285dcb2e28/dwprod.py
on /usr/lib/libc.so.6 to find the relevant flag (or absence thereof) be
enough as a test case?
--
You received this bug notification because you a
Hi @ktecho,
Thank you for taking the time to open this bug report.
I just want to make sure I understand everything going on here...
There is a fix upstream that Diogo submitted, and you would like for it
to make it into the Noble (24.04) kernel. That patch should fix the
issue you are hitting
** Description changed:
- The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
+ SRU Justification:
+
+ [ Impact ]
+
+ * The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
In absence of a dwarf unwinder (as
** Description changed:
- Power's Linux ABIs all require an explicit call chain be stored on the call
stack frames which are all accessible via the stack pointer.
- Therefore, having a (soft/simulated) frame pointer does not improve
backtraces at all on Power.
+ SRU Justification:
- However,
** Description changed:
SRU Justification:
[ Impact ]
- * The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
+ * The preferred way of doing stack unwinding on Linux on Z is via dwarf call
frame information.
In absence of a dwarf unwinder (
Hi @schopin, I agree - that is what is now under option 1) under test
plan in the SRU Justification.
--
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/2064539
Title:
Revert back frame point
Already resolved long time ago.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038752
Title:
6.5.1005.7 has broken Proton prefix creation
Status in linux-meta-oem-6.5 pack
** Changed in: linux-meta-oem-6.5 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2038752
Title:
6.5.1005.7 has broken Proton pref
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
This bug is awaiting verification that the linux/6.8.0-43.43 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' to 'verification-done-noble-linux'. If
the problem still exist
I will test out -43 when I get home tonight.
--
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/2072755
Title:
i915: Fixup regressions introduced with enabling single CCS engine
Status in l
** Tags removed: verification-needed-focal-linux-azure
** Tags added: verification-done-focal-linux-azure
--
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/2073414
Title:
Include Azure Site
Public bug reported:
My touchpad was working fine, but suddenly it stopped working. I've
tried all the solutions available on the internet, but nothing has
solved the issue. When I tried to list the detected devices (less
/proc/bus/input/devices), the touchpad didn't appear. I'm not sure how
to so
No, I shouldn't have mentioned it. This laptops have a problem, and it's
work-arounded by doing the masking and unmasking of interrupt 0x6E. The
fix is not in the kernel yet, so I have the work-around enabled since
one year ago.
This is a totally different problem: since one month ago, the compute
This cherry pick will cover noble and oracular. Backporting this from
6.10 to 5.15 is not feasible for the Jammy kernel. Also this will be
in the 6.8 kernel in 22.04.5.
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Won't Fix
--
You received this bug notification because you
solution in linux/6.8.0-43.43 works for me.
--
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/2073358
Title:
Kubuntu 24.04 freezes after plugging in ethernet cable
Status in linux package
Public bug reported:
I've been using a Lenovo X12 Detachable Gen 2 model from 2024 [1] to
encode some video files with ffmpeg, and the system becomes completely
unresponsive for as long as the process executes. Although small, this
is a pretty good device hardware wise, and while executing the sys
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803835/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
htt
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803834/+files/version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in Ubuntu.
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2076361/+attachment/5803836/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency in U
Hi Ranjan,
What is the regression risk? Also in your steps for testing, what does
r0 and r1 stand for in this step "ro and r1 creation and deletion"?
** Description changed:
[Impact]
This update has been initiated to incorporate the mpi3mr driver from upstream
into the upcoming Ubuntu rele
** Also affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-signed (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ub
It seems to fix the problem for me too.
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
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/2073358
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
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/2074380
Title:
[UBUNTU 22.04] s390/cpum_cf: make crypto counter
** Description changed:
[Impact]
* Microsoft has requested a patch to address a kernel panic issue
+ similar to the upstream issue here -
+
https://patchwork.kernel.org/project/netdevbpf/patch/20240731213046.6194-2-pa...@netfilter.org/
[Fix]
* Clean cherry-pick upstream commit 58
This bug was fixed in the package linux-azure - 5.4.0-1135.142
---
linux-azure (5.4.0-1135.142) focal; urgency=medium
* focal/linux-azure: 5.4.0-1135.142 -proposed tracker (LP: #2072263)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from
This bug was fixed in the package linux-nvidia-tegra-igx -
5.15.0-1013.13
---
linux-nvidia-tegra-igx (5.15.0-1013.13) jammy; urgency=medium
* jammy/linux-nvidia-tegra-igx: 5.15.0-1013.13 -proposed tracker
(LP: #2072515)
* Add OOTM branching to fix GPU driver version mismatch
This bug was fixed in the package linux-azure - 5.15.0-1070.79
---
linux-azure (5.15.0-1070.79) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1070.79 -proposed tracker (LP: #2072209)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from
This bug was fixed in the package linux-azure - 6.8.0-1012.14
---
linux-azure (6.8.0-1012.14) noble; urgency=medium
* noble/linux-azure: 6.8.0-1012.14 -proposed tracker (LP: #2072175)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from ke
This bug was fixed in the package linux-azure - 6.8.0-1012.14
---
linux-azure (6.8.0-1012.14) noble; urgency=medium
* noble/linux-azure: 6.8.0-1012.14 -proposed tracker (LP: #2072175)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from ke
This bug was fixed in the package linux-azure - 6.8.0-1012.14
---
linux-azure (6.8.0-1012.14) noble; urgency=medium
* noble/linux-azure: 6.8.0-1012.14 -proposed tracker (LP: #2072175)
* Packaging resync (LP: #1786013)
- [Packaging] debian.azure/dkms-versions -- update from ke
This bug is awaiting verification that the linux-
azure-5.4/5.4.0-1135.142~18.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-bionic-linux-
azure-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
ibm-5.15/5.15.0-1060.63~20.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-focal-linux-
ibm-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
azure-5.4/5.4.0-1135.142~18.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-bionic-linux-
azure-5.4' to 'verification-done-bionic
Wanting to test whether the fix had also made it into the focal-proposed
(Ubuntu 20.04) kernel version -119, despite the absence of any
indication of that in the bug status description, I tried to install the
proposed kernel, but I can't:
# trying to install from proposed2 (also tested proposed, w
All autopkgtests for the newly accepted dpkg (1.22.6ubuntu6.1) for noble have
finished running.
The following regressions have been reported in tests triggered by the package:
aodh/unknown (s390x)
apache2/2.4.58-1ubuntu8.4 (armhf)
apache2/unknown (s390x)
apt/2.7.14build2 (s390x)
apt-cacher/unknow
All autopkgtests for the newly accepted dpkg (1.22.6ubuntu6.1) for noble have
finished running.
The following regressions have been reported in tests triggered by the package:
aodh/unknown (s390x)
apache2/2.4.58-1ubuntu8.4 (armhf)
apache2/unknown (s390x)
apt/2.7.14build2 (s390x)
apt-cacher/unknow
Adding the "verification-done-focal-linux-aws-5.15" since this bug
doesn't affect focal:linux-azure-5.15
** Tags removed: kernel-spammed-bionic-linux-azure-5.4-v2
kernel-spammed-focal-linux-ibm-5.15-v2
verification-needed-bionic-linux-azure-5.4
verification-needed-focal-linux-aws-5.15
verifica
Public bug reported:
The nvidia-fs prebuilt module linux-modules-nvidia-fs-5.15.0-ABIN-
nvidia(-lowlatency) packages provide nvidia-fs-dkms. The linux-
nvidia(-lowlatency) meta packages depend on either the latest linux-
modules-nvidia-fs-5.15.0-ABIN-nvidia(-lowlatency), or "nvidia-fs-dkms"
as an
Hi Ian,
I have since found out that I need to apply this against linux-firmware.
So ignore those test kernels for now.
** Package changed: linux (Ubuntu Noble) => linux-firmware (Ubuntu
Noble)
** Changed in: linux-firmware (Ubuntu Noble)
Assignee: (unassigned) => Michael Reed (mreed8855)
-
AceLan Kao,
In summary, I did not see any improvement, but perhaps some of the extended
debugging is helpful.
I did the following steps over the course of my work day, so I might have
missed a step, but here is the order of what I did:
I added the ubuntu kernel repo:
$ sudo add-apt-repository p
101 - 200 of 239 matches
Mail list logo
