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-xilinx-
zynqmp/5.15.0-1025.29 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/5.15.0-1018.18~20.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-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1005.5 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-
igx' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1027.29 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-1040.43
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-nvidia-
tegra/5.15.0-1018.18 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/5.15.0-1048.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-aws' to 'verification-done-jammy-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/5.15.0-1050.57
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 was fixed in the package linux - 5.15.0-86.96
---
linux (5.15.0-86.96) jammy; urgency=medium
* jammy/linux: 5.15.0-86.96 -proposed tracker (LP: #2036575)
* 5.15.0-85 live migration regression (LP: #2036675)
- Revert "KVM: x86: Always enable legacy FP/SSE in allowed
Hi, is there a timeline on when this patch will reach the general
availability kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2032176
Title:
Crashing with CPU soft lock on GA
No crashes observed with the proposed kernel. Changed the tag to
'verification-done-jammy-linux'.
** 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
Currently, testing out the linux/5.15.0-85.95 version of kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2032176
Title:
Crashing with CPU soft lock on GA kernel 5.15.0.79.76 and
This bug is awaiting verification that the linux/5.15.0-85.95 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
Right, fix-committed means it is applied to git and will be included in
the 2023.09.04 SRU cycle. The fix for 5.15 is to change the default of
tdp_mmu to off (like you did for testing). Changing the deployments like
you did would be the work-around in the mean-time.
The parent Ubuntu state
We are still seeing this issue on 5.15.0-82-generic for 22.04 (Jammy)
Since the (Ubuntu Jammy) is on Fix Committed and not Fix Released, I
would assume this is normal right? And the Fix Released status on
(Ubuntu) means the bug is not present on other Ubuntu versions?
--
You received this bug
** 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://bugs.launchpad.net/bugs/2032176
Title:
Crashing with CPU soft lock on GA kernel
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Stefan Bader (smb)
** Description changed:
+ Impact:
+ We had reports of VM setups
Confirm the instances with tdp_mmu=0 does not seem to crash. Had 5
instances running for 4 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2032176
Title:
Crashing with CPU soft
19 matches
Mail list logo
