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.
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/hkyy9a9U2jJ7 GPL59
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.