linux-kernel - Re: [PATCH 0/3] Fix Navi3x boot and hotplug problems

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8cae7afb-3e6d-42cd-925f-4ee3af920178@amd.com>
Date:   Thu, 28 Sep 2023 15:01:16 -0500
From:   Mario Limonciello <mario.limonciello@....com>
To:     Alex Deucher <alexdeucher@...il.com>,
        Sebastian Reichel <sre@...nel.org>
Cc:     amd-gfx@...ts.freedesktop.org,
        Alex Deucher <alexander.deucher@....com>, Jun.ma2@....com,
        linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH 0/3] Fix Navi3x boot and hotplug problems

On 9/28/2023 13:00, Alex Deucher wrote:
> On Thu, Sep 28, 2023 at 12:41 PM Mario Limonciello
> <mario.limonciello@....com> wrote:
>>
>> On some OEM systems multiple navi3x dGPUS are triggering RAS errors
>> and BACO errors.
>>
>> These errors come from elements of the OEM system that weren't part of
>> original test environment.  This series addresses those problems.
>>
>> NOTE: Although this series touches two subsystems, I would prefer to
>> take this all through DRM because there is a workaround in linux-next
>> that I would like to be reverted at the same time as picking up the first
>> two patches.
> 
> FWIW, the workaround is not in linux-next yet.  At the time I thought
> it was already fixed by the fixes in ucsi and power supply when we
> first encountered this.

I looked yesterday and I did see it there, but I think it was 
specifically because it had merged the amd-staging-drm-next tree.
It's not there today..

If Sebastian is OK, I'd still rather keep it all together so that people 
testing amd-staging-drm-next get the fixes.

> 
> Alex
> 
>>
>> Mario Limonciello (3):
>>    drm/amd: Fix detection of _PR3 on the PCIe root port
>>    power: supply: Don't count 'unknown' scope power supplies
>>    Revert "drm/amd/pm: workaround for the wrong ac power detection on smu
>>      13.0.0"
>>
>>   drivers/gpu/drm/amd/amdgpu/amdgpu_device.c           | 2 +-
>>   drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0.c       | 3 ++-
>>   drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_0_ppt.c | 1 +
>>   drivers/power/supply/power_supply_core.c             | 2 +-
>>   4 files changed, 5 insertions(+), 3 deletions(-)
>>
>> --
>> 2.34.1
>>