6.1.0-1004-oem worked fine in terms of stability over yesterday's work day, with no amdgpu protection faults, but when I tried to suspend by closing the lid at the end of the work day, I got some very strange behaviour that I've never seen before - see video here: https://photos.app.goo.gl/hkyy9a9U2jJ7GPL59
I'll test your custom 5.17 kernel next, because it seems that the 5.17 train is the only viable one at the moment on this hardware. I reverted to 5.17.0-1025-eom today and everything went fine. As a point of comparison, I'm updating this bug on my personal laptop, which is a ThinkPad E14 AMD Gen3 - very similar specs to my work laptop, yet this one suspends fine on 6.1.0-1004-oem and has had no amdgpu problems that I know of. I'll add the lspci -nnvv for comparison shortly. -- 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: Triaged 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
