Hints removed. Closing this bug.
This issue cannot be found on J-azure, J-azure-fips, J-gcp-fips, J-mtk,
J-nvidia-tegra, J-xilinx.
We don't run this test on J-raspi, J-bluefield.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
** Tags removed:
This bug is awaiting verification that the linux-gcp-
fips/5.15.0-1055.63+fips2 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-gcp-fips' to
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
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-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1058.66+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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1027.31 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-xilinx-zynqmp'
to
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1022.22 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-tegra' to
This bug is awaiting verification that the linux-azure/5.15.0-1056.64
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
This bug is awaiting verification that the linux-raspi/5.15.0-1046.49
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
This bug is awaiting verification that the linux-
bluefield/5.15.0-1035.37 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-bluefield' to
This bug was fixed in the package linux - 5.15.0-94.104
---
linux (5.15.0-94.104) jammy; urgency=medium
* jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777)
* [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
(LP: #2028158)
- device-dax: Fix
There is no ARM64 for jammy-linux-ibm-gt-fips.
** Tags removed: verification-needed-jammy-linux-ibm-gt-fips
** Tags added: verification-done-jammy-linux-ibm-gt-fips
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the linux-ibm-gt-
fips/5.15.0-1052.55+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-jammy-linux-ibm-gt-fips' to
There is no ARM64 for intel iotg kernel.
** Tags removed: verification-needed-jammy-linux-intel-iotg
** Tags added: verification-dibe-jammy-linux-intel-iotg
** Tags removed: verification-dibe-jammy-linux-intel-iotg
** Tags added: verification-done-jammy-linux-intel-iotg
--
You received this
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1047.53 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-intel-iotg' to
Verified with Jammy 5.15.0-93.103 ARM64, this test is not failing
anymore.
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the linux/5.15.0-93.103 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' to 'verification-done-jammy-linux'. If
the problem still
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
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://lists.ubuntu.com/archives/kernel-team/2023-November/147192.html
** Description changed:
- First time seen this since ftrace refactor out from
- ubuntu_kernel_selftests to ubuntu-kselftests-ftrace
+
+ [Impact]
+ On ARM64 systems, tests like event-enable.tc, event-pid.tc in
+
** Summary changed:
- ftrace:test.d--event--subsystem-enable.tc fails with timeout on
focal:linux-hwe-5.15 ARM64
+ Change in trace file leads to test timeout in ftrace tests on 5.15 ARM64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
19 matches
Mail list logo
