Similar to the issue on upstream https://gitlab.freedesktop.org/drm/amd/-/issues/2220
Compare what we backported and the kernel versions reported on the upstream bug, I feel like it's below commit introduce the regression Could you try this test kernel to see if it helps, it only reverts the below commit. https://people.canonical.com/~acelan/bugs/lp2002467/ commit d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a Author: Lijo Lazar <lijo.la...@amd.com> Date: Fri Sep 30 10:43:08 2022 +0530 drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x MMHUB 2.1.x versions don't have ATCL2. Remove accesses to ATCL2 registers. Since they are non-existing registers, read access will cause a 'Completer Abort' and gets reported when AER is enabled with the below patch. Tagging with the patch so that this is backported along with it. v2: squash in uninitialized warning fix (Nathan Chancellor) Fixes: 8795e182b02d ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()") Signed-off-by: Lijo Lazar <lijo.la...@amd.com> Reviewed-by: Guchun Chen <guchun.c...@amd.com> Signed-off-by: Alex Deucher <alexander.deuc...@amd.com> Cc: sta...@vger.kernel.org ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2220 https://gitlab.freedesktop.org/drm/amd/-/issues/2220 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Incomplete Bug description: When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [ 1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
