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-raspi-
realtime/6.8.0-2004.4 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-riscv/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-riscv' to 'verification-done-noble-
linux-riscv'. If
This bug is awaiting verification that the linux-oem-6.8/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-oem-6.8' to 'verification-done-
noble-linux-oem-6.8'.
This bug is awaiting verification that the linux-nvidia/6.8.0-1007.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-nvidia' to 'verification-done-
noble-linux-nvidia'. If
This bug is awaiting verification that the linux-intel/6.8.0-1005.12
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-intel' to 'verification-done-noble-
linux-intel'. If
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-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-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-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 was fixed in the package linux - 6.8.0-35.35
---
linux (6.8.0-35.35) noble; urgency=medium
* noble/linux: 6.8.0-35.35 -proposed tracker (LP: #2065886)
* CVE-2024-21823
- VFIO: Add the SPR_DSA and SPR_IAX devices to the denylist
- dmaengine: idxd: add a new
** Tags removed: verification-needed-noble-linux
** Tags added: verification-done-noble-linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058557
Title:
Kernel panic during checkbox
This bug is awaiting verification that the linux/6.8.0-32.32 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
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Mitchell Augustin (mitchellaugustin)
Status: In Progress
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
** Changed in: linux (Ubuntu)
Assignee: Jose Ogando Justo (joseogando) => Mitchell Augustin
(mitchellaugustin)
** Changed in: linux (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fix has landed upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/aio.c?h=v6.9-rc3=caeb4b0a11b3393e43f7fa8e0a5a18462acc66bd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A fix has been applied to vfs.fixes upstream and should land soon. I
have tested this patch and verified that the panic no longer occurs.
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This issue is still present upstream, so I reported it to the original
committer of the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058557
Title:
Kernel panic during checkbox
I have isolated the cause of this bug to this commit:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?h=Ubuntu-6.8.0-20.20=71eb6b6b0ba93b1467bccff57b5de746b09113d2
All versions that I tested before this commit during my bisect passed
the aiol test at least 15
It turns out that this issue does not appear with *every* run of the
aiol test on affected kernels, so multiple runs of that test may be
necessary for the panic to occur.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did some more version testing, and I have not been able to reproduce
this bug with the "aiol" stressor on either Upstream 6.5 or Ubuntu
6.5.0-26-generic-64k, so it was evidently introduced after that version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Earlier, I said that the device mapper observation did not seem to be a
hard line - however, further testing now indicates that the situations
where I observed panics when stressing nvme0n1 were due to an unrelated
bug that is present in the latest 6.5 mainline tree, but *not* the
latest 6.5
I did not observe this issue with any other stress_ng disk tests on
linux-image-6.8.0-11-generic-64k after 1 full run of the suite with the
"aiol" test disabled.
(When running the "aiol" test alone, it panicked reliably each time.)
--
You received this bug notification because you are a member
Upon further investigation, the device mapper observation does not seem
to be a hard line, as I was able to observe panics when stressing both
dm-0 and nvme0n1 under different circumstances.
At the moment, it also seems like the specific part of stress_ng_test
that is the culprit is the
I have observed that this panic does not seem to happen when stressing
non-device-mapper devices (ex: it panics when running /usr/lib/checkbox-
provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240,
but completes successfully when running /usr/lib/checkbox-provider-
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jose Ogando Justo (joseogando)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058557
Title:
Kernel panic during checkbox stress_ng_test
This is also reproducible on the latest mainline version
(https://kernel.ubuntu.com/mainline/v6.8/arm64/, retrieved 20 Mar 2024 @
5 PM):
20 Mar 22:54: Running stress-ng aiol stressor for 240 seconds...
[ 354.451450] Unable to handle kernel paging request at virtual address
17be9b4aa3e187be
[
28 matches
Mail list logo