Just to clarify Renjith tested on a Phoenix machine.
Based on Renjith's test result though, this is a fail and an extra change is
needed.
It turns out that this linux-firmware commit should come too:
1c513ec7 ("amdgpu: Update GC 11.0.1 and 11.0.4")
This is because of kernel commit
616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2
This actually changes for all RDNA3 GPUs, so Phoenix needs the updated
F/W too.
** Tags added: verification-failed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024427
Title:
potential S3 issue for amdgpu Navi 31/Navi33
Status in HWE Next:
New
Status in linux package in Ubuntu:
Triaged
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Lunar:
In Progress
Status in linux-firmware source package in Lunar:
Fix Committed
Status in linux-oem-6.1 source package in Lunar:
Invalid
Status in linux source package in Mantic:
Triaged
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-oem-6.1 source package in Mantic:
Invalid
Bug description:
[SRU Justification]
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.
========== original bug report ==========
amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue.
amdgpu:
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
Navi31:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc
Navi33:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2024427/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
