Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
- To: Éric Valette <eric.valette@free.fr>
- Cc: Salvatore Bonaccorso <carnil@debian.org>, Dominique Dumont <dod@debian.org>, Sasha Levin <sashal@kernel.org>, David Airlie <airlied@linux.ie>, "Pan, Xinhui" <Xinhui.Pan@amd.com>, LKML <linux-kernel@vger.kernel.org>, amd-gfx list <amd-gfx@lists.freedesktop.org>, Luben Tuikov <luben.tuikov@amd.com>, Maling list - DRI developers <dri-devel@lists.freedesktop.org>, Alex Deucher <alexander.deucher@amd.com>, 1005005@bugs.debian.org, Evan Quan <evan.quan@amd.com>, Christian König <christian.koenig@amd.com>, Alex Deucher <alexdeucher@gmail.com>
- Subject: Bug#1005005: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic in suspend (v2)") on suspend?
- From: Thorsten Leemhuis <regressions@leemhuis.info>
- Date: Mon, 21 Mar 2022 15:30:02 +0100
- Message-id: <[🔎] 41eaaf17-1456-5971-e7d9-e5ccc65bcf01@leemhuis.info>
- Reply-to: Thorsten Leemhuis <regressions@leemhuis.info>, 1005005@bugs.debian.org
- In-reply-to: <[🔎] ba7faa48-68a5-41f9-9192-f843e17c5a07@free.fr>
- References: <Ygf7KuWyc0d4HIFu@eldamar.lan> <CADnq5_MfR99OhjumQESCO7Oq+JVOHOVgyVQHX4FpGFDnPu6CyQ@mail.gmail.com> <5164225.DI6hChFYCN@ylum> <c62d4ba9-2214-ca7d-ee78-ee19a9bf51e6@free.fr> <CADnq5_MWqz7-XhOS4zfuzi3=_nKa72iYaO0BcKNcVDwEvZ+YHw@mail.gmail.com> <[🔎] 61c2b2ce-d749-3723-ad27-f40e1c49d967@leemhuis.info> <[🔎] ba7faa48-68a5-41f9-9192-f843e17c5a07@free.fr> <164405721350.15142.10930772309423612672.reportbug@ylum.maison>
On 21.03.22 13:07, Éric Valette wrote:
> 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.
This thread/the debian bug report
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005005 ) is getting
long which makes things hard to grasp. But to me it looks a lot like the
problem you are facing is different from the problem that others ran
into and bisected -- but I might be totally wrong there. Have you ever
tried reverting 3c196f056666 to seem if it helps (sorry if that's
mentioned in the bug report somewhere, as I said, it became long)? I
guess a bisection from your side really would help a lot; but before you
go down that route you might want to give 5.17 and the latest 5.15.y
kernel a try.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.
Reply to: