** Also affects: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: linux-oem-5.14 (Ubuntu)
       Status: Fix Committed => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Focal)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945348

Title:
  Yellow Carp S0i3 stability fix

Status in amd:
  Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [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.

  ===== original descriptions =====

  A problem is identified with S0i3 on Yellow carp where under stress
  testing with 5.14.0 through 5.14.8 sometimes there will be failures.

  It will manifest as:

  [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

  The fix for this will be going into 5.15-rcX and also to 5.14.y.  Just want 
to give a pointer to Canonical team that if this comes up where to expect the 
fix for OEM kernel.
  The patch going into 5.15-rcX and 5.14.y is: 
https://lists.freedesktop.org/archives/amd-gfx/2021-September/069451.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1945348/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to