Fwd: Re: amd | ASUS ROG Strix G513QY fails to resume from suspend [regression] (#2008)

[Limonciello, Mario]

[Public]



> -----Original Message-----
> From: Thorsten Leemhuis <regressions at leemhuis.info>
> Sent: Tuesday, May 10, 2022 05:33
> To: Paul Menzel <pmenzel at molgen.mpg.de>; regressions at lists.linux.dev
> Cc: amd-gfx at lists.freedesktop.org; Limonciello, Mario
> <Mario.Limonciello at amd.com>
> Subject: Re: Fwd: Re: amd | ASUS ROG Strix G513QY fails to resume from
> suspend [regression] (#2008)
> 
> On 10.05.22 10:37, Paul Menzel wrote:
> > Dear Linux regressions folks,
> >
> > A user reported a regression [1], which also trickled down to the stable
> > series, for example between 5.15.13 and 5.15.14.
> >
> > [1]:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitla
> b.freedesktop.org%2Fdrm%2Famd%2F-
> %2Fissues%2F2008&data=05%7C01%7Cmario.limonciello%40amd.com%
> 7C48555e8619c04186687808da327076c3%7C3dd8961fe4884e608e11a82d994e
> 183d%7C0%7C0%7C637877755868268003%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C3000%7C%7C%7C&sdata=5m%2BEztsZA9qBT8vUSHVnvBCTBnB%2Bar
> U%2FnZqa3MC3lmA%3D&reserved=0
> 
> Many thx for forwarding. I'll add it to the tracking to ensure it's not
> forgotten:
> 
> #regzbot introduced: 887f75cfd0da44c19dd
> #regzbot from: spin83
> #regzbot title: drm: amdgpu: ASUS ROG Strix G513QY fails to resume from
> suspend
> #regzbot link:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitla
> b.freedesktop.org%2Fdrm%2Famd%2F-
> %2Fissues%2F2008&data=05%7C01%7Cmario.limonciello%40amd.com%
> 7C48555e8619c04186687808da327076c3%7C3dd8961fe4884e608e11a82d994e
> 183d%7C0%7C0%7C637877755868268003%7CUnknown%7CTWFpbGZsb3d8ey
> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
> 7C3000%7C%7C%7C&sdata=5m%2BEztsZA9qBT8vUSHVnvBCTBnB%2Bar
> U%2FnZqa3MC3lmA%3D&reserved=0
> 
> Maybe the culprit is actually daf8de0874ab5b74b38a38726fdd3d, the report
> is not clear on that, I just picked the newest the reporter mentioned
> for now.
> 
> See the ticket for details, there were a few replies already. According
> to Paul the problems trickled down to the stable series, for example
> between 5.15.13 and 5.15.14.

The discussion is trending to a revert.  The revert is submitted here:
https://patchwork.freedesktop.org/patch/485708/

> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
> 
> P.P.S.: This isn't a regression? This issue or a fix for it are already
> discussed somewhere else? It was fixed already? You want to clarify when
> the regression started to happen? Or point out I got the title or
> something else totally wrong? Then just reply -- ideally with also
> telling regzbot about it, as explained here:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinux
> -regtracking.leemhuis.info%2Ftracked-
> regression%2F&data=05%7C01%7Cmario.limonciello%40amd.com%7C4
> 8555e8619c04186687808da327076c3%7C3dd8961fe4884e608e11a82d994e183
> d%7C0%7C0%7C637877755868268003%7CUnknown%7CTWFpbGZsb3d8eyJW
> IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
> 3000%7C%7C%7C&sdata=od7XqKGQVoduIldm71Dfj42Vhq2oHuHFpLAtL
> B2nLvE%3D&reserved=0