Hi
In Debian we got the report in https://bugs.debian.org/1114806 that suspend to RAM fails (amdgpu driver hang) and Niklas Cathor was both able to bisect the issue down to 8345a71fc54b ("drm/amdgpu: Add more checks to PSP mailbox") (which was backported to 6.12.2 as well).
There is an upstream report as well at https://gitlab.freedesktop.org/drm/amd/-/issues/4531 matching the issue and fixed by 440cec4ca1c2 ("drm/amdgpu: Wait for bootloader after PSPv11 reset").
Unfortunately the commit does not apply cleanly to 6.16.y as well as there were the changes around 9888f73679b7 ("drm/amdgpu: Add a noverbose flag to psp_wait_for").
Attached patch backports the commit due to this context changes, assuming it is not desirable to pick as well 9888f73679b7.
Does that looks good? If yes, can you please consider picking it up or the next 6.16.y stable series as well?
Regards, Salvatore
On Sun, Sep 14, 2025 at 01:18:11PM +0200, Salvatore Bonaccorso wrote:
Hi
In Debian we got the report in https://bugs.debian.org/1114806 that suspend to RAM fails (amdgpu driver hang) and Niklas Cathor was both able to bisect the issue down to 8345a71fc54b ("drm/amdgpu: Add more checks to PSP mailbox") (which was backported to 6.12.2 as well).
There is an upstream report as well at https://gitlab.freedesktop.org/drm/amd/-/issues/4531 matching the issue and fixed by 440cec4ca1c2 ("drm/amdgpu: Wait for bootloader after PSPv11 reset").
Unfortunately the commit does not apply cleanly to 6.16.y as well as there were the changes around 9888f73679b7 ("drm/amdgpu: Add a noverbose flag to psp_wait_for").
Attached patch backports the commit due to this context changes, assuming it is not desirable to pick as well 9888f73679b7.
Does that looks good? If yes, can you please consider picking it up or the next 6.16.y stable series as well?
I have a revert of the offending commit in the 6.16.y queue right now, as this was pointed out as causing a problem: https://lore.kernel.org/all/20250904220457.473940-1-alexander.deucher@amd.co... so that should resolve this issue, right?
thanks,
greg k-h
Hi Greg,
[note fixing up my typo for the Debian bug, sorry about that]
On Sun, Sep 14, 2025 at 01:43:38PM +0200, Greg Kroah-Hartman wrote:
On Sun, Sep 14, 2025 at 01:18:11PM +0200, Salvatore Bonaccorso wrote:
Hi
In Debian we got the report in https://bugs.debian.org/1114806 that suspend to RAM fails (amdgpu driver hang) and Niklas Cathor was both able to bisect the issue down to 8345a71fc54b ("drm/amdgpu: Add more checks to PSP mailbox") (which was backported to 6.12.2 as well).
There is an upstream report as well at https://gitlab.freedesktop.org/drm/amd/-/issues/4531 matching the issue and fixed by 440cec4ca1c2 ("drm/amdgpu: Wait for bootloader after PSPv11 reset").
Unfortunately the commit does not apply cleanly to 6.16.y as well as there were the changes around 9888f73679b7 ("drm/amdgpu: Add a noverbose flag to psp_wait_for").
Attached patch backports the commit due to this context changes, assuming it is not desirable to pick as well 9888f73679b7.
Does that looks good? If yes, can you please consider picking it up or the next 6.16.y stable series as well?
I have a revert of the offending commit in the 6.16.y queue right now, as this was pointed out as causing a problem: https://lore.kernel.org/all/20250904220457.473940-1-alexander.deucher@amd.co... so that should resolve this issue, right?
Ah good, yes that should be equally fine (I missed the pending revert). Thanks a lot!
Regards, Salvatore
Hi Greg,
On 9/14/25 1:43 PM, Greg Kroah-Hartman wrote:
On Sun, Sep 14, 2025 at 01:18:11PM +0200, Salvatore Bonaccorso wrote:
Hi
In Debian we got the report in https://bugs.debian.org/1114806 that suspend to RAM fails (amdgpu driver hang) and Niklas Cathor was both able to bisect the issue down to 8345a71fc54b ("drm/amdgpu: Add more checks to PSP mailbox") (which was backported to 6.12.2 as well).
There is an upstream report as well at https://gitlab.freedesktop.org/drm/amd/-/issues/4531 matching the issue and fixed by 440cec4ca1c2 ("drm/amdgpu: Wait for bootloader after PSPv11 reset").
Unfortunately the commit does not apply cleanly to 6.16.y as well as there were the changes around 9888f73679b7 ("drm/amdgpu: Add a noverbose flag to psp_wait_for").
Attached patch backports the commit due to this context changes, assuming it is not desirable to pick as well 9888f73679b7.
Does that looks good? If yes, can you please consider picking it up or the next 6.16.y stable series as well?
I have a revert of the offending commit in the 6.16.y queue right now, as this was pointed out as causing a problem: https://lore.kernel.org/all/20250904220457.473940-1-alexander.deucher@amd.co... so that should resolve this issue, right?
Yes, I can confirm that applying that revert to 6.16.y solves the issue on my machine as well.
cheers, Niklas
linux-stable-mirror@lists.linaro.org