This bug is awaiting verification that the linux-oem-6.11/6.11.0-1025.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done- noble-linux-oem-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-failed- noble-linux-oem-6.11'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2112290 Title: fwts s3 test shows High Failures: last_hw_sleep less than 70% on AMD platforms Status in HWE Next: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.14 package in Ubuntu: Invalid Status in linux-oem-6.11 source package in Noble: Fix Committed Status in linux-oem-6.14 source package in Noble: Fix Committed Bug description: [Impact] Got the following messages while doing fwts s3 tests Expected /sys/power/suspend_stats/last_hw_sleep to be at least 70% of the last sleep cycle, got 66.10%. (x 1) Expected /sys/power/suspend_stats/last_hw_sleep to be at least 70% of the last sleep cycle, got 65.54%. (x 6) Expected /sys/power/suspend_stats/last_hw_sleep to be at least 70% of the last sleep cycle, got 65.64%. (x 9) Expected /sys/power/suspend_stats/last_hw_sleep to be at least 70% of the last sleep cycle, got 65.75%. (x 1) Expected /sys/power/suspend_stats/last_hw_sleep to be at least 70% of the last sleep cycle, got 65.44%. (x 3) Expected /sys/power/suspend_stats/last_hw_sleep to be at least 70% of the last sleep cycle, got 65.65%. (x 5) [Fix] AMD provides a patch to clear the smu_virt_addr table explicitly [Test] Runs `sudo fwts s3 --multiple=10` on AMD machines, the result.log should not contain the message mentioned above. [Where problems could occur] Clear smu_virt_addr table explicitly during setup won't introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2112290/+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
