This bug is awaiting verification that the linux-
nvidia-6.5/6.5.0-1014.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-jammy-linux-nvidia-6.5' to
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-
aws-6.5/6.5.0-1013.13~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.5' to
This bug is awaiting verification that the linux-azure/6.5.0-1013.13
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
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-
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 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 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
This bug is awaiting verification that the linux-
gcp-6.5/6.5.0-1013.13~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-
gcp-6.5' to
This bug was fixed in the package linux-hwe-6.5 - 6.5.0-17.17~22.04.1
---
linux-hwe-6.5 (6.5.0-17.17~22.04.1) jammy; urgency=medium
* jammy/linux-hwe-6.5: 6.5.0-17.17~22.04.1 -proposed tracker (LP:
#2048369)
* Mantic update: v6.5.4 upstream stable release (LP: #2041999)
-
This bug was fixed in the package linux - 6.5.0-17.17
---
linux (6.5.0-17.17) mantic; urgency=medium
* mantic/linux: 6.5.0-17.17 -proposed tracker (LP: #2049026)
* [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
anymore (LP: #2048919)
- [Config]
** Tags removed: verification-needed-jammy-linux
verification-needed-jammy-linux-ibm-gt-fips
verification-needed-jammy-linux-intel-iotg verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux
verification-done-jammy-linux-ibm-gt-fips
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
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
This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
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)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
Issue on 201711-25989 is also different. There's a timeout between
Docker and Checkbox. The system is well and alive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046217
Title:
Issue on 201702-25401 is different. Quite likely caused by faulty CPU
fan and faulty memory.
** Description changed:
- During the jammy-hwe migration test, I found some machines failed to run
- the pm-graph.
-
>From the log in pstore the issue was caused by iwlwifi.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046217
Title:
Some machines can't pass the pm-graph test
Status in
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046217
Title:
Some machines can't pass the
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2046217
Title:
Some
** Also affects: linux-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.5 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-signed-hwe-6.5 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this
27 matches
Mail list logo
