[SRU][PULL][linux-firmware][Lunar] System hangs at S3 for amdgpu Navi 31/Navi33

[Timo Aaltonen]

You-Sheng Yang kirjoitti 6.7.2023 klo 11.28:
> BugLink: https://bugs.launchpad.net/bugs/2024427
> 
> [Impact]
> 
> Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms
> will sometimes fail to wake from S3.
> 
> [Fix]
> 
> kernel patches:
> ac2f5739fdca drm/amdgpu/mes11: enable reg active poll
> a2fe4534bb38 drm/amd/amdgpu: update mes11 api def
> da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
> 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
> 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4
> 
> firmware patches:
> * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release
> * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release
> 
> [Test Case]
> 
> $ checkbox-cli run com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
> 
> [Where problems could occur]
> 
> Little we know about the firmware fixes. However, while with these commits have
> been pulled via stable kernel fixes, the driver begins to request new firmware
> blobs of a different filename.
> 
> [Other Info]
> 
> The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and
> partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to
> be fixed.
> 
> For the firmware parts, they have been included in linux-firmware/mantic,
> leaving linux-firmware/lunar and linux-firmware/jammy to be fixed.
> 

Acked-by: Timo Aaltonen <timo.aaltonen at canonical.com>

-- 
t