This bug was fixed in the package linux-oem-6.1 - 6.1.0-1020.20
---------------
linux-oem-6.1 (6.1.0-1020.20) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1020.20 -proposed tracker (LP: #2030594)
* CVE-2022-40982
- init: Provide arch_cpu_finalize_init()
- x86/cpu: Switch to arch_cpu_finalize_init()
- ARM: cpu: Switch to arch_cpu_finalize_init()
- ia64/cpu: Switch to arch_cpu_finalize_init()
- loongarch/cpu: Switch to arch_cpu_finalize_init()
- m68k/cpu: Switch to arch_cpu_finalize_init()
- mips/cpu: Switch to arch_cpu_finalize_init()
- sh/cpu: Switch to arch_cpu_finalize_init()
- sparc/cpu: Switch to arch_cpu_finalize_init()
- um/cpu: Switch to arch_cpu_finalize_init()
- init: Remove check_bugs() leftovers
- init: Invoke arch_cpu_finalize_init() earlier
- init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
- x86/init: Initialize signal frame size late
- x86/fpu: Remove cpuinfo argument from init functions
- x86/fpu: Mark init functions __init
- x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
- x86/speculation: Add Gather Data Sampling mitigation
- x86/speculation: Add force option to GDS mitigation
- x86/speculation: Add Kconfig option for GDS
- KVM: Add GDS_NO support to KVM
- x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build
- x86/xen: Fix secondary processors' FPU initialization
- x86/mm: fix poking_init() for Xen PV guests
- x86/mm: Use mm_alloc() in poking_init()
- mm: Move mm_cachep initialization to mm_init()
- x86/mm: Initialize text poking earlier
- Documentation/x86: Fix backwards on/off logic about YMM support
- [Config]: Enable CONFIG_ARCH_HAS_CPU_FINALIZE_INIT
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume
- SAUCE: whitelist platforms that needs save/restore ASPM L1SS for
suspend/resume
* CVE-2023-20593
- x86/cpu/amd: Move the errata checking functionality up
- x86/cpu/amd: Add a Zenbleed fix
* Fix repeated errors of blacklisting during bootup (LP: #2029363)
- certs: make blacklisted hash available in klog
- KEYS: Add new function key_create()
- certs: don't try to update blacklist keys
* Fix AMD gpu hang when screen off/on (LP: #2028740)
- drm/amd/display: Keep PHY active for dp config
* CVE-2023-4015
- netfilter: nf_tables: skip immediate deactivate in _PREPARE_ERROR
* CVE-2023-3995
- netfilter: nf_tables: disallow rule addition to bound chain via
NFTA_RULE_CHAIN_ID
* CVE-2023-3777
- netfilter: nf_tables: skip bound chain on rule flush
* CVE-2023-4004
- netfilter: nft_set_pipapo: fix improper element removal
-- Timo Aaltonen <timo.aalto...@canonical.com> Wed, 16 Aug 2023
15:20:53 +0300
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-40982
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-20593
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3777
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3995
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4004
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-4015
--
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/1980829
Title:
System freeze after resuming from suspend due to PCI ASPM settings
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux-oem-6.0 source package in Focal:
Invalid
Status in linux-oem-6.1 source package in Focal:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-5.14 source package in Kinetic:
Invalid
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux-oem-6.1 source package in Kinetic:
Invalid
Bug description:
For OEM-6.1
[Impact]
While doing some tests such as suspend/resume or CPU stress tests the system
would hang.
[Fix]
Below commit fixed the issue, but not going to be merged into mainline.
The patch is still under discussion and have other variance, and we already
merged the origin patch into oem-6.0 and 5.15/5.19 for a year, so could
consider it's safer for us.
https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/
I also created a DMI quirk to make the patches only affects on listed
platforms.
[Test]
The affected machines could suspend/resume well.
[Where problems could occur]
The patches only affects on the listed platforms, and won't affect other
platforms.
======================================================================
For Jammy/Kinetic SRU
[Impact]
While doing some tests such as suspend/resume or CPU stress tests the system
would hang.
[Fix]
The 2 commits fix the issue, but still not get accepted yet.
https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/
https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/
So, I created a DMI quirk to make the patches only affects on listed
platforms.
[Test]
Verified on the failed machines and ODM also verified on their side.
[Where problems could occur]
The patches only affects on the listed platforms, and won't affect other
platforms.
======================================================================
For OEM-6.0
[Impact]
While doing some tests such as suspend/resume or CPU stress tests the system
would hang.
[Fix]
The 2 commits fix the issue, but still not get accepted yet.
https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/
https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/
[Test]
Verified on the failed machines and ODM also verified on their side.
[Where problems could occur]
The 2 patches look pretty safe to me, they try to preserve the ASPM state of
devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1980829/+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
