** Tags added: originate-from-2033332

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2033025

Title:
  Fix numerous AER related issues

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux-oem-6.5 source package in Jammy:
  Fix Released
Status in linux source package in Lunar:
  Fix Committed
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux-oem-6.5 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux-oem-6.5 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  Numerous issues triggered from AER/DPC services
  - When AER is shared with PME, cutting the power off the device can trigger 
AER IRQ. Since AER IRQ is shared with PME, it's treated like a wakeup source, 
preventing the system from entering sleep.

  - When system resume from S3, device can reset itself and start
  sending PTM messages, triggering AER and reset the entire hierarchy.
  Since the hardware/firmware starts before software, it's never soon
  enough to put a band-aid from kernel.

  - Following above one, device firmware restarts before kernel resume,
  when DPC is triggered then the device is gone without any recovering
  method. We really want to prevent that from happening.

  [Fix]
  Disable and re-enable AER and DPC services on suspend and resume, 
respectively.
  Right now the the PCI mailing list doesn't have a consensus which PCI state 
(D3hot vs D3cold) should the AER/DPC services should be disabled, so re-instate 
the old workaround for now.

  [Test]
  One the workaround is applied, symptoms described above can no longer be 
observed.

  [Where problems could occur]
  Theoretically there can be some "real" issues get unnoticed once AER gets 
temporarily disabled, but the benefit far outweighs the downside.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2033025/+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