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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <68ac824b-3419-4644-a355-24341540fa6d@free.fr>
Date:   Thu, 24 Feb 2022 12:22:23 +0000 (UTC)
From:   Éric Valette <eric.valette@...e.fr>
To:     Alex Deucher <alexdeucher@...il.com>
Cc:     Dominique Dumont <dod@...ian.org>,
        Salvatore Bonaccorso <carnil@...ian.org>,
        Sasha Levin <sashal@...nel.org>,
        amd-gfx list <amd-gfx@...ts.freedesktop.org>,
        David Airlie <airlied@...ux.ie>,
        "Pan, Xinhui" <Xinhui.Pan@....com>,
        LKML <linux-kernel@...r.kernel.org>,
        Maling list - DRI developers 
        <dri-devel@...ts.freedesktop.org>,
        Luben Tuikov <luben.tuikov@....com>, 1005005@...s.debian.org,
        Alex Deucher <alexander.deucher@....com>,
        Evan Quan <evan.quan@....com>,
        Christian König <christian.koenig@....com>
Subject: Re: Regression from 3c196f056666 ("drm/amdgpu: always reset the
 asic in suspend (v2)") on suspend?

On 2/21/22 15:16, Alex Deucher wrote:

>>>> 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.

Trying to add the pach on top of 5.15.24, I got a already applied message and indeed the patch is already there. So this particular patch it does not fix my problem.

Saw new modif in 5.15.25. Will try and check if I can find time to bissect.

-- eric