Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?

["Éric Valette" <eric.valette@free.fr>]

My problem has never been fixed. The proposed patch has been applied to 5.15. I do not remerber which version 28 maybe.

I still have à RIP in pm_suspend. Did not test the Last two 15 versions.

I can leave with 5.10 est using own compiled kernels.

Thanks for asking.

21 mars 2022 09:58:01 Thorsten Leemhuis <regressions@leemhuis.info>:

> Hi, this is your Linux kernel regression tracker. Top-posting for once,
> to make this easily accessible to everyone.
> 
> Dominique/Salvatore/Eric, what's the status of this regression?
> According to the debian bug tracker the problem is solved with 5.16 and
> 5.17, but was 5.15 ever fixed?
> 
> Ciao, Thorsten
> 
> On 21.02.22 15:16, Alex Deucher wrote:
>> On Mon, Feb 21, 2022 at 3:29 AM Eric Valette <eric.valette@free.fr> wrote:
>>> 
>>> 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.
>> 
>> It doesn't really matter what the platform is, it could still
>> potentially help on your system, it depends on the bios implementation
>> for your platform and how it handles suspend. You can try the patch,
>> but I don't think you are hitting the same issue.  I bisect would be
>> helpful in your case.
>> 
>> Alex