This bug is awaiting verification that the linux-oem-5.14/5.14.0-1025.27 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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.
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: verification-needed-focal -- 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/1961121 Title: Not able to enter s2idle state on AMD platforms Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] AMD Systems don't enter PC6 at runtime and cause failures to enter s2idle. Currently the fix is from kernel driver rather than MP2 firmware, which disable interrupts from kernel driver to fix MP2 firmware blocking CPUOFF. [Fix] The fixes involve 1) cancelling delayed work when entering s0ix and re-scheduling it when resuming from s0ix, and 2) clearing interrupts during the driver initialization and sensor command operations. [Test] This is requested by AMD and was tested on AMD CRB. [Where problems could occur] Risk is low to medium. Some code flow changes are guarded by reasonable conditions, but the fixes introduced additional suspend and resume operations. Having said that, clearing interrupts before driver initialization and cancelling work before entering sleeping states are standard approaches are usually safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961121/+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
