mbox series

[0/1,SRU,OEM-5.14] Yellow Carp S0i3 stability fix

Message ID 20211015195801.1043106-1-alex.hung@canonical.com
Headers show
Series Yellow Carp S0i3 stability fix | expand

Message

Alex Hung Oct. 15, 2021, 7:58 p.m. UTC 
BugLink: https://bugs.launchpad.net/bugs/1945348

[Impact]

  Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8.


  [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v5_2> failed -110
  amdgpu 0000:04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110).
  PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110
  amdgpu 0000:04:00.0: PM: failed to resume async: error -110

[Fix]

  The patch fixes this by forcing exit gfxoff for sdma resume.

  The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519)

[Test]

  This is requested by AMD.

[Where problems could occur]

  Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware.

Prike Liang (1):
  drm/amdgpu: force exit gfxoff on sdma resume for rmb s0ix

 drivers/gpu/drm/amd/amdgpu/sdma_v5_2.c | 8 ++++++++
 1 file changed, 8 insertions(+)

Comments

Tim Gardner Oct. 18, 2021, 12:39 p.m. UTC | #1 
Acked-by: Tim Gardner <tim.gardner@canonical.com>

On 10/15/21 1:58 PM, Alex Hung wrote:
>    BugLink: https://bugs.launchpad.net/bugs/1945348
> 
> [Impact]
> 
>    Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8.
> 
> 
>    [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v5_2> failed -110
>    amdgpu 0000:04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110).
>    PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110
>    amdgpu 0000:04:00.0: PM: failed to resume async: error -110
> 
> [Fix]
> 
>    The patch fixes this by forcing exit gfxoff for sdma resume.
> 
>    The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519)
> 
> [Test]
> 
>    This is requested by AMD.
> 
> [Where problems could occur]
> 
>    Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware.
> 
> Prike Liang (1):
>    drm/amdgpu: force exit gfxoff on sdma resume for rmb s0ix
> 
>   drivers/gpu/drm/amd/amdgpu/sdma_v5_2.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
Timo Aaltonen Oct. 25, 2021, 3:34 p.m. UTC | #2 
On 15.10.2021 22.58, Alex Hung wrote:
>    BugLink: https://bugs.launchpad.net/bugs/1945348
> 
> [Impact]
> 
>    Below errors are reported with S0i3 on Yellow carp where under stress testing with 5.14.0 through 5.14.8.
> 
> 
>    [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v5_2> failed -110
>    amdgpu 0000:04:00.0: amdgpu: amdgpu_device_ip_resume failed (-110).
>    PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110
>    amdgpu 0000:04:00.0: PM: failed to resume async: error -110
> 
> [Fix]
> 
>    The patch fixes this by forcing exit gfxoff for sdma resume.
> 
>    The patch is in 5.15-rc4 (https://github.com/torvalds/linux/commit/26db706a6d77b9e184feb11725e97e53b7a89519)
> 
> [Test]
> 
>    This is requested by AMD.
> 
> [Where problems could occur]
> 
>    Low risk. This only affects AMD platforms with s0ix supports. The changes repeat what is (should be) done in firmware.
> 
> Prike Liang (1):
>    drm/amdgpu: force exit gfxoff on sdma resume for rmb s0ix
> 
>   drivers/gpu/drm/amd/amdgpu/sdma_v5_2.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 

This got applied via v5.14.10