This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-38.38.1~22.04.2 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-
lowlatency-hwe-6.8' to
This bug is awaiting verification that the linux-oracle/6.8.0-1006.6
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-oracle' to 'verification-done-
noble-linux-oracle'. If
This bug is awaiting verification that the linux-
lowlatency/6.8.0-35.35.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
This bug is awaiting verification that the linux-ibm/6.8.0-1006.6 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-ibm' to 'verification-done-noble-linux-
ibm'. If the
This bug is awaiting verification that the linux-gcp/6.8.0-1008.9 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-gcp' to 'verification-done-noble-linux-
gcp'. If the
This bug is awaiting verification that the linux-gke/6.8.0-1004.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-gke' to 'verification-done-noble-linux-
gke'. If the
This bug is awaiting verification that the linux-aws/6.8.0-1009.9 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-aws' to 'verification-done-noble-linux-
aws'. If the
This bug is awaiting verification that the linux-azure/6.8.0-1008.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-azure' to 'verification-done-noble-
linux-azure'. If
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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.8' to
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when
In proposed: https://launchpad.net/ubuntu/+source/linux/6.8.0-19.19
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049390
Andrea already applied it to the kernel config, thanks!
https://lists.ubuntu.com/archives/kernel-team/2024-March/149278.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049390
Title:
Please
Since my kernel patch for bug 1970069 is being blocked upstream at the
moment, reducing the loglevel to 3 is becoming more of a priority.
Otherwise I don't see us making sufficient progress on bug 1970069.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For the general use case I think that reducing the verbosity makes
sense. About our testing, I think we're not booting kernels with
"quiet", and if we do we should definitely drop it from the kernel boot
options.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
14 matches
Mail list logo
