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 <[email protected]> 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/1957026
Title:
AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
On AMD Yellow Carp B0 platforms, S0i3 is still not working.
[Fix]
This denpends on a few fixes for kernel driver that are all either in
v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed
dmcub firmware.
[Test Case]
On AMD RMT CRB board,
1. apply both kernel and firmware fixes
2. module blacklist amd_sfh as it's still under development,
3. trigger system suspend. Use power button to wake up the device.
4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero
On without any of above, the board may not cut device power during
suspend, and/or fail to resume and leaving a blank screen, and/or s0ix
stats remain all zeros.
[Where problems could occur]
On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't
support S0ix and has to be disabled. For the kernel side, the driver
fixes addressed a few procedure errors that should be unlikely to
introduce regressions; for the firmware side, also tested loading new
firmware on unpatched kernels and there is no difference found yet.
[Other Info]
For kernel driver fixes, patches for both oem-5.14 and jammy are
necessary; for firmware, that has been available in jammy branch but
not yet released, so only Focal will be nominated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1957026/+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
