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-nvidia/5.15.0-1011.11
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' to 'verification-done-jammy'. If the
problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.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-jammy' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1005.7~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' to
'verification-done-focal'. If the problem
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
Sorry I am late to the party on confirming the fix, was traveling.
Confirming that everything is working properly with the latest jammy-
proposed kernel.
tested package: linux-image-5.15.0-1021-aws 5.15.0-1021.25
ubuntu@ip-172-31-31-116:~$ sudo dmesg | grep 5.15.60
[0.00] Linux version
This bug is awaiting verification that the linux/5.15.0-50.56 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' to 'verification-done-jammy'. If the problem
still exists, change
** Description changed:
+ [SRU Justification]
+
+ Impact: The 5.15 kernel series introduced a regression compared to 5.13
+ related to virtual display code on AMD GPUs. This causes crashes for
+ cloud/VM users back to Focal (using rolling cloud or HWE kernels).
+
+ Fix: Upstream stable 5.15.61
** Package changed: linux-aws-5.15 (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in:
Patch now posted upstream for linux stable kernel 5.15
https://lore.kernel.org/stable/20220719185659.2068735-1-alexander.deuc...@amd.com/T/#u
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.15 in Ubuntu.
Alexander Deucher at AMD came up with a quick fix for the 5.15 branch,
which I was able to test and verify - amdgpu_fb.c, line 344:
-if (!amdgpu_device_has_dc_support(adev) && !amdgpu_virtual_display)
+if (!amdgpu_device_has_dc_support(adev) && !amdgpu_virtual_display &&
** Package changed: linux-meta-aws-5.15 (Ubuntu) => linux-aws-5.15
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981883
Title:
amdgpu module crash after 5.15 kernel
Suspect that
https://github.com/torvalds/linux/commit/6a6c2ab687c8eabaec4a55a4f13eb5ee68181403
might fix this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-aws-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1981883
Title:
This crash occurs after also firing several warnings with backtraces -
[ 318.108644] WARNING: CPU: 6 PID: 13667 at
drivers/gpu/drm/drm_crtc_helper.c:221
drm_helper_disable_unused_functions+0x32/0x50 [drm_kms_helper]
[ 318.109727] WARNING: CPU: 6 PID: 13667 at
14 matches
Mail list logo
