This bug was fixed in the package linux-oem-5.14 - 5.14.0-1024.26
---------------
linux-oem-5.14 (5.14.0-1024.26) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP:
#1961191)
* Packaging resync (LP: #1786013)
- [Config] Update config to match upstream stable release
- [Packaging] update variants
* CVE-2022-0435
- tipc: improve size validations for received domain records
* CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent
* Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
- ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"
* USB port lost function after unplugging usb drive (LP: #1958850)
- block: add disk sequence number
- mm: hide laptop_mode_wb_timer entirely behind the BDI API
- block: pass a gendisk to blk_queue_update_readahead
- block: add a queue_has_disk helper
- block: move the bdi from the request_queue to the gendisk
- block: remove the bd_bdi in struct block_device
- nvme: use blk_mq_alloc_disk
- st: do not allocate a gendisk
- sg: do not allocate a gendisk
- block: cleanup the lockdep handling in *alloc_disk
- block: remove alloc_disk and alloc_disk_node
- block: remove the minors argument to __alloc_disk_node
- block: pass a request_queue to __blk_alloc_disk
- block: hold a request_queue reference for the lifetime of struct gendisk
- block: add an explicit ->disk backpointer to the request_queue
- writeback: make the laptop_mode prototypes available unconditionally
- sg: pass the device name to blk_trace_setup
- block: factor out a blk_try_enter_queue helper
- block: drain file system I/O on del_gendisk
- block: keep q_usage_counter in atomic mode after del_gendisk
- block: drain queue after disk is removed from sysfs
- nvdimm/pmem: stop using q_usage_count as external pgmap refcount
- nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned
* Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
- iommu/amd: Restore GA log/tail pointer on host resume
-- Timo Aaltonen <timo.aalto...@canonical.com> Thu, 17 Feb 2022
13:23:43 +0200
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0435
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0492
--
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/1960771
Title:
Use EC GPE for s2idle wakeup on AMD platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[Impact]
Opening lid doesn't wakeup some AMD platforms from s2idle.
[Fix]
Use EC GPE for lid events to wakeup the laptops.
[Test]
Close and only the lid. The affected laptop now can be woken up by lid.
[Where problems could occur]
The original issue was later fixed by "pinctrl: amd: Fix wakeups when
IRQ is shared with SCI". However, EC GPE is prone to cause spurious
wakeup, so we still need to keep an eye on the regression reports.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1960771/+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
