This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1961121

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
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:
  Incomplete
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:
  New
Status in linux source package in Jammy:
  Incomplete
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     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to