[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b3c39447-c02a-a021-8a4f-499aa962980c@leemhuis.info>
Date: Mon, 21 Mar 2022 20:00:28 +0100
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: dod@...ian.org, Eric Valette <eric.valette@...e.fr>,
Salvatore Bonaccorso <carnil@...ian.org>
Cc: Sasha Levin <sashal@...nel.org>, David Airlie <airlied@...ux.ie>,
"Pan, Xinhui" <Xinhui.Pan@....com>,
LKML <linux-kernel@...r.kernel.org>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>,
Luben Tuikov <luben.tuikov@....com>,
Maling list - DRI developers
<dri-devel@...ts.freedesktop.org>,
Alex Deucher <alexander.deucher@....com>,
1005005@...s.debian.org, Evan Quan <evan.quan@....com>,
Christian König <christian.koenig@....com>,
Alex Deucher <alexdeucher@...il.com>
Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the asic
in suspend (v2)") on suspend?
On 21.03.22 19:49, Dominique Dumont wrote:
> On Monday, 21 March 2022 09:57:59 CET Thorsten Leemhuis wrote:
>> 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?
>
> I don't think so.
>
> On kernel side, the commit fixing this issue is
> e55a3aea418269266d84f426b3bd70794d3389c8 .
>
> According to the logs of [1] , this commit landed in v5.17-rc3
>
> HTH
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
And from there it among others got backported to 5.15.22:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.15.y&id=8a15ac1786c92dce6ecbeb4e4c237f5f80c2c703
https://lwn.net/Articles/884107/
Another indicator that Eric's problem is something else.
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.
Powered by blists - more mailing lists