Experiencing the same issue on a new XPS 9640.
Downgrading to a known kernel as pointed by others (linux-
image-6.8.0-36-generic) has problems with other areas like WiFi and
soundcard.
The solution was to upgrade the kernel to mainline 6.9.1 onwards up to
6.9.12. (6.9 still gives mouse cursor gli
I confirm that kernel 5.15.0-119 from the proposed2 PPA fixes this issue
on Jammy.
Thank you, Matthew, for your kind explanation, and to all the developers
who worked on this!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8
This isn't fixed in the jammy 6.5.0-1024-aws kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2018303
Title:
move sev-guest module from linux-modules-extra to linux-modules
St
I'm just adding here that this is still a problem with 6.1.0 and my
Intel 7260 wireless device. Adding my log in case it helps somehow.
-
[ 75.351025] [ cut here ]
[ 75.351028] Timeout waiting for hardware access (CSR_GP_CNTRL 0x)
[ 75.351
I put them at the same location
https://people.canonical.com/~mschiu77/lp2073676/ for acp test. If it's
not working, we will have to do bisect. It might need 10~13 test kernels
to find out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Many thanks doko, the debdiff looks reasonable and good.
I did a test build (based on v1.22.6ubuntu6.1
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+sourcepub/16274696/+listing-archive-extra)
and wasn't able to find an indication of FBs (in the debug symbols) anymore
(using read
Hello Frank, or anyone else affected,
Accepted dpkg into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dpkg/1.22.6ubuntu6.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
Frank, can you help me in writing up some test cases for both of these
bugs? SO that we have formally a test case someone can follow or at
least understand. Thanks!
** Changed in: dpkg (Ubuntu Noble)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-noble
Frank, can you help me in writing up some test cases for both of these
bugs? SO that we have formally a test case someone can follow or at
least understand. Thanks!
** Changed in: dpkg (Ubuntu Noble)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-noble
Hello Frank, or anyone else affected,
Accepted dpkg into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dpkg/1.22.6ubuntu6.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubu
This bug was fixed in the package linux - 5.15.0-118.128
---
linux (5.15.0-118.128) jammy; urgency=medium
* jammy/linux: 5.15.0-118.128 -proposed tracker (LP: #2072255)
* Jammy update: v5.15.160 upstream stable release (LP: #2070292)
- drm/amd/display: Fix division by zero in
This bug was fixed in the package linux - 5.15.0-118.128
---
linux (5.15.0-118.128) jammy; urgency=medium
* jammy/linux: 5.15.0-118.128 -proposed tracker (LP: #2072255)
* Jammy update: v5.15.160 upstream stable release (LP: #2070292)
- drm/amd/display: Fix division by zero in
This bug is awaiting verification that the linux-azure/5.15.0-1070.79
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 t
This bug is awaiting verification that the linux-ibm/5.15.0-1060.63
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' to 'verification-done-jammy-
linux-ibm'. If the pro
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1067.73~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-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-oracle/5.15.0-1065.71
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-oracle' to 'verification-done-
jammy-linux-oracle'. I
This bug is awaiting verification that the linux-raspi/5.15.0-1060.63
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 t
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-118.128~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-
hwe-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1018.18
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-gcp-tcpx' to 'verification-done-
focal-linux-gcp-tc
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1050.57~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-
gkeop-5.15' to 'verification-done-focal
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux-aws - 6.8.0-1013.14
---
linux-aws (6.8.0-1013.14) noble; urgency=medium
* noble/linux-aws: 6.8.0-1013.14 -proposed tracker (LP: #2072173)
* [aws] Backport CMA pool per numa functionality for 22.04 and 20.04
(LP: #2067516)
- net: ena
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 6.8.0-40.40
---
linux (6.8.0-40.40) noble; urgency=medium
* noble/linux: 6.8.0-40.40 -proposed tracker (LP: #2072201)
* FPS of glxgear with fullscreen is too low on MTL platform (LP: #2069380)
- drm/i915: Bypass LMEMBAR/GTTMMADR for M
This bug was fixed in the package linux - 5.4.0-192.212
---
linux (5.4.0-192.212) focal; urgency=medium
* focal/linux: 5.4.0-192.212 -proposed tracker (LP: #2072305)
* Focal update: v5.4.278 upstream stable release (LP: #2071668)
- x86/tsc: Trust initial offset in architectur
This bug was fixed in the package linux - 5.4.0-192.212
---
linux (5.4.0-192.212) focal; urgency=medium
* focal/linux: 5.4.0-192.212 -proposed tracker (LP: #2072305)
* Focal update: v5.4.278 upstream stable release (LP: #2071668)
- x86/tsc: Trust initial offset in architectur
This bug was fixed in the package linux - 5.4.0-192.212
---
linux (5.4.0-192.212) focal; urgency=medium
* focal/linux: 5.4.0-192.212 -proposed tracker (LP: #2072305)
* Focal update: v5.4.278 upstream stable release (LP: #2071668)
- x86/tsc: Trust initial offset in architectur
This bug was fixed in the package linux-oem-6.8 - 6.8.0-1010.10
---
linux-oem-6.8 (6.8.0-1010.10) noble; urgency=medium
* noble/linux-oem-6.8: 6.8.0-1010.10 -proposed tracker (LP: #2072187)
* No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
(LP: #2073049
This bug was fixed in the package linux-riscv - 6.8.0-40.40.1
---
linux-riscv (6.8.0-40.40.1) noble; urgency=medium
* noble/linux-riscv: 6.8.0-40.40.1 -proposed tracker (LP: #2072197)
* Noble update: v6.8.12 upstream stable release (LP: #2071621)
- SAUCE: pwm: opencores: drop
This bug was fixed in the package linux-nvidia - 6.8.0-1011.11
---
linux-nvidia (6.8.0-1011.11) noble; urgency=medium
* noble/linux-nvidia: 6.8.0-1011.11 -proposed tracker (LP: #2072186)
* PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores"
(LP: #2071655)
This bug was fixed in the package linux-nvidia - 6.8.0-1011.11
---
linux-nvidia (6.8.0-1011.11) noble; urgency=medium
* noble/linux-nvidia: 6.8.0-1011.11 -proposed tracker (LP: #2072186)
* PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores"
(LP: #2071655)
This bug was fixed in the package linux-nvidia - 6.8.0-1011.11
---
linux-nvidia (6.8.0-1011.11) noble; urgency=medium
* noble/linux-nvidia: 6.8.0-1011.11 -proposed tracker (LP: #2072186)
* PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores"
(LP: #2071655)
This bug is awaiting verification that the linux-bluefield/5.4.0-1090.97
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-bluefield' to 'verification-done-
focal-linux-bluef
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-
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-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-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-
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-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-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-
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-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-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-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-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-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-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-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-
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-
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-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-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-
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-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-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-
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-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/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-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-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-
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-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-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-
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-azure/5.4.0-1135.142
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-azure' to 'verification-done-focal-
linux-azure'. If t
This bug is awaiting verification that the linux-
raspi-5.4/5.4.0-1114.126~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-
raspi-5.4' to 'verification-done-bionic
This bug is awaiting verification that the linux-
gcp-5.4/5.4.0-1134.143~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-
gcp-5.4' to 'verification-done-bionic-lin
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-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-
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
1 - 100 of 239 matches
Mail list logo