Messages in this thread | | | Date | Sun, 20 Feb 2022 19:03:23 +0100 | Subject | Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend? | From | Eric Valette <> |
| |
On 20/02/2022 16:48, Dominique Dumont wrote: > On Monday, 14 February 2022 22:52:27 CET Alex Deucher wrote: >> Does the system actually suspend? > > Not really. The screens looks like it's going to suspend, but it does come > back after 10s or so. The light mounted in the middle of the power button does > not switch off.
As I have a very similar problem and also commented on the original debian bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005005), I will add some information here on another amd only laptop (renoir AMD Ryzen 7 4800H with Radeon Graphics + Radeon RX 5500/5500M / Pro 5500M).
For me the suspend works once, but after the first resume (I do know know if it is in the suspend path or the resume path I see a RIP in the dmesg (see aditional info in debian bug)) and later suspend do not work: It only go to the kde login screen.
I was unable due to network connectivity to do a full bisect but tested with the patch I had on my laptop:
5.10.101 works, 5.10 from debian works 5.11 works 5.12 works 5.13 suspend works but when resuming the PC is dead I have to reboot 5.14 seems to work but looking at dmesg it is full of RIP messages at various places. 5.15.24 is a described 5.15 from debian is behaving identically 5.16 from debian is behaving identically.
>> Is this system S0i3 or regular S3?
For me it is real S3.
The proposed patch is intended for INTEl + intel gpu + amdgpu but I have dual amd GPU.
--eric
| |