This bug is awaiting verification that the linux-fips/6.8.0-38.38+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-noble-linux-fips' to 'verification-done-noble-
linux-fips'. If
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-38.38.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
This bug is awaiting verification that the linux-oracle/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-oracle' to 'verification-done-
noble-linux-oracle'. If
This bug is awaiting verification that the linux-riscv/6.8.0-38.38.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-riscv' to 'verification-done-noble-
linux-riscv'. If
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1009.9~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-
nvidia-6.8' to
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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.8' to
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1008.8~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-
ibm-6.8' to
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2006.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-raspi-realtime'
to
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-
azure-6.8/6.8.0-1010.10~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-
azure-6.8' to
This bug is awaiting verification that the linux-
hwe-6.8/6.8.0-38.38~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-
hwe-6.8' to
This bug is awaiting verification that the linux-ibm/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-ibm' to 'verification-done-noble-linux-
ibm'. If the
This bug is awaiting verification that the linux-nvidia/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-nvidia' to 'verification-done-
noble-linux-nvidia'. If
This bug is awaiting verification that the linux-gke/6.8.0-1006.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-gke' to 'verification-done-noble-linux-
gke'. If the
This bug was fixed in the package linux - 6.8.0-38.38
---
linux (6.8.0-38.38) noble; urgency=medium
* noble/linux: 6.8.0-38.38 -proposed tracker (LP: #2068318)
* race_sched in ubuntu_stress_smoke_test will cause kernel panic on 6.8 with
Azure Standard_A2_v2 instance (LP:
This bug is awaiting verification that the linux-nvidia-
lowlatency/6.8.0-1009.9.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-nvidia-
lowlatency' to
This bug is awaiting verification that the linux/6.8.0-38.38 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
** Changed in: linux (Ubuntu Noble)
Status: In Progress => 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/2068591
Title:
Noble: btrfs: re-introduce 'norecovery' mount option
To
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Roxana Nicolescu (roxanan)
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Invalid
19 matches
Mail list logo
