[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux- oracle-6.2/6.2.0-1015.15~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.2' to 'verification-done-jammy-linux-oracle-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.2' to 'verification-failed-jammy-linux-oracle-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oracle-6.2-v2 verification-needed-jammy-linux-oracle-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux-oracle/6.2.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-oracle' to 'verification-done- lunar-linux-oracle'. If the problem still exists, change the tag 'verification-needed-lunar-linux-oracle' to 'verification-failed-lunar- linux-oracle'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-oracle-v2 verification-needed-lunar-linux-oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux-riscv/6.2.0-36.37.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-riscv' to 'verification-done-lunar- linux-riscv'. If the problem still exists, change the tag 'verification- needed-lunar-linux-riscv' to 'verification-failed-lunar-linux-riscv'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-riscv-v2 verification-needed-lunar-linux-riscv -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug was fixed in the package linux - 6.2.0-36.37 --- linux (6.2.0-36.37) lunar; urgency=medium * lunar/linux: 6.2.0-36.37 -proposed tracker (LP: #2038076) * Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7 (LP: #2035181) - selftests/bpf: fix static assert compilation issue for test_cls_*.c * CVE-2023-4244 - netfilter: nf_tables: don't skip expired elements during walk - netfilter: nf_tables: adapt set backend to use GC transaction API - netfilter: nft_set_hash: mark set element as dead when deleting from packet path - netfilter: nf_tables: GC transaction API to avoid race with control plane - netfilter: nf_tables: don't fail inserts if duplicate has expired - netfilter: nf_tables: fix kdoc warnings after gc rework - netfilter: nf_tables: fix GC transaction races with netns and netlink event exit path - netfilter: nf_tables: GC transaction race with netns dismantle - netfilter: nf_tables: GC transaction race with abort path - netfilter: nf_tables: use correct lock to protect gc_list - netfilter: nf_tables: defer gc run if previous batch is still pending - netfilter: nft_dynset: disallow object maps - netfilter: nft_set_rbtree: skip sync GC for new elements in this transaction * CVE-2023-4563 - netfilter: nf_tables: remove busy mark and gc batch API * CVE-2023-42756 - netfilter: ipset: Fix race between IPSET_CMD_CREATE and IPSET_CMD_SWAP * CVE-2023-4623 - net/sched: sch_hfsc: Ensure inner classes have fsc curve * Fix unstable audio at low levels on Thinkpad P1G4 (LP: #2037077) - ALSA: hda/realtek - ALC287 I2S speaker platform support * Lunar update: upstream stable patchset 2023-09-21 (LP: #2037005) - Upstream stable to v6.1.41, v6.4.6 - io_uring: treat -EAGAIN for REQ_F_NOWAIT as final for io-wq - ALSA: hda/realtek - remove 3k pull low procedure - ALSA: hda/realtek: Add quirk for Clevo NS70AU - ALSA: hda/realtek: Enable Mute LED on HP Laptop 15s-eq2xxx - maple_tree: set the node limit when creating a new root node - maple_tree: fix node allocation testing on 32 bit - keys: Fix linking a duplicate key to a keyring's assoc_array - perf probe: Add test for regression introduced by switch to die_get_decl_file() - btrfs: fix warning when putting transaction with qgroups enabled after abort - fuse: revalidate: don't invalidate if interrupted - fuse: Apply flags2 only when userspace set the FUSE_INIT_EXT - btrfs: set_page_extent_mapped after read_folio in btrfs_cont_expand - btrfs: zoned: fix memory leak after finding block group with super blocks - fuse: ioctl: translate ENOSYS in outarg - btrfs: fix race between balance and cancel/pause - selftests: tc: set timeout to 15 minutes - selftests: tc: add 'ct' action kconfig dep - regmap: Drop initial version of maximum transfer length fixes - of: Preserve "of-display" device name for compatibility - regmap: Account for register length in SMBus I/O limits - arm64/fpsimd: Ensure SME storage is allocated after SVE VL changes - can: mcp251xfd: __mcp251xfd_chip_set_mode(): increase poll timeout - can: bcm: Fix UAF in bcm_proc_show() - can: gs_usb: gs_can_open(): improve error handling - selftests: tc: add ConnTrack procfs kconfig - dma-buf/dma-resv: Stop leaking on krealloc() failure - drm/amdgpu/vkms: relax timer deactivation by hrtimer_try_to_cancel - drm/amdgpu/pm: make gfxclock consistent for sienna cichlid - drm/amdgpu/pm: make mclk consistent for smu 13.0.7 - drm/client: Fix memory leak in drm_client_target_cloned - drm/client: Fix memory leak in drm_client_modeset_probe - drm/amd/display: only accept async flips for fast updates - drm/amd/display: Disable MPC split by default on special asic - drm/amd/display: check TG is non-null before checking if enabled - drm/amd/display: Keep PHY active for DP displays on DCN31 - ASoC: fsl_sai: Disable bit clock with transmitter - ASoC: fsl_sai: Revert "ASoC: fsl_sai: Enable MCTL_MCLK_EN bit for master mode" - ASoC: tegra: Fix ADX byte map - ASoC: rt5640: Fix sleep in atomic context - ASoC: cs42l51: fix driver to properly autoload with automatic module loading - ASoC: codecs: wcd938x: fix missing clsh ctrl error handling - ASoC: codecs: wcd-mbhc-v2: fix resource leaks on component remove - ASoC: qdsp6: audioreach: fix topology probe deferral - ASoC: tegra: Fix AMX byte map - ASoC: codecs: wcd938x: fix resource leaks on component remove - ASoC: codecs: wcd938x: fix missing mbhc init error handling - ASoC: codecs: wcd934x: fix resource leaks on component remove - ASoC: codecs: wcd938x: fix codec initialisation race - ASoC: codecs: wcd938x: fix soundwire initialisation race - ext4: correct inline offset when handling xattrs in inode body - drm/radeon: Fix
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux- starfive-6.2/6.2.0-1008.9~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- starfive-6.2' to 'verification-done-jammy-linux-starfive-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux- starfive-6.2' to 'verification-failed-jammy-linux-starfive-6.2'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-starfive-6.2-v2 verification-needed-jammy-linux-starfive-6.2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux- aws-6.5/6.5.0-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux- azure-6.5/6.5.0-1007.7~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.5' to 'verification-done-jammy-linux-azure-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.5' to 'verification-failed-jammy-linux-azure-6.5'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-6.5-v2 verification-needed-jammy-linux-azure-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
** Tags removed: verification-needed-lunar-linux ** Tags added: verification-done-lunar-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux/6.2.0-36.37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar- linux' to 'verification-failed-lunar-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug was fixed in the package linux - 6.5.0-7.7 --- linux (6.5.0-7.7) mantic; urgency=medium * mantic/linux: 6.5.0-7.7 -proposed tracker (LP: #2037611) * kexec enable to load/kdump zstd compressed zimg (LP: #2037398) - [Packaging] Revert arm64 image format to Image.gz * Mantic minimized/minimal cloud images do not receive IP address during provisioning (LP: #2036968) - [Config] Enable virtio-net as built-in to avoid race * Miscellaneous Ubuntu changes - SAUCE: Add mdev_set_iommu_device() kABI - [Config] update gcc version in annotations -- Andrea Righi Thu, 28 Sep 2023 10:19:24 +0200 ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: New Status in linux-oem-6.1 source package in Jammy: Fix Released 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 Released 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1023.23
---
linux-oem-6.1 (6.1.0-1023.23) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1023.23 -proposed tracker (LP: #2033827)
* Jammy update: v6.1.53 upstream stable release (LP: #2035359)
- Revert "bridge: Add extack warning when enabling STP in netns."
- Partially revert "drm/amd/display: Fix possible underflow for displays
with
large vblank"
- scsi: ufs: Try harder to change the power mode
- Revert "Revert drm/amd/display: Enable Freesync Video Mode by default"
- ARM: dts: imx: Set default tuning step for imx7d usdhc
- powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
- media: uapi: HEVC: Add num_delta_pocs_of_ref_rps_idx field
- Revert "MIPS: unhide PATA_PLATFORM"
- phy: qcom-snps-femto-v2: use qcom_snps_hsphy_suspend/resume error code
- media: amphion: use dev_err_probe
- media: pulse8-cec: handle possible ping error
- media: pci: cx23885: fix error handling for cx23885 ATSC boards
- 9p: virtio: fix unlikely null pointer deref in handle_rerror
- 9p: virtio: make sure 'offs' is initialized in zc_request
- ksmbd: fix out of bounds in smb3_decrypt_req()
- ksmbd: validate session id and tree id in compound request
- ksmbd: no response from compound read
- ksmbd: fix out of bounds in init_smb2_rsp_hdr()
- ASoC: da7219: Flush pending AAD IRQ when suspending
- ASoC: da7219: Check for failure reading AAD IRQ events
- ASoC: nau8821: Add DMI quirk mechanism for active-high jack-detect
- ethernet: atheros: fix return value check in atl1c_tso_csum()
- m68k: Fix invalid .section syntax
- s390/dasd: use correct number of retries for ERP requests
- s390/dasd: fix hanging device after request requeue
- fs/nls: make load_nls() take a const parameter
- ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
- ASoc: codecs: ES8316: Fix DMIC config
- ASoC: rt711: fix for JD event handling in ClockStop Mode0
- ASoC: rt711-sdca: fix for JD event handling in ClockStop Mode0
- ASoC: atmel: Fix the 8K sample parameter in I2SC master
- ALSA: usb-audio: Add quirk for Microsoft Modern Wireless Headset
- platform/x86: intel: hid: Always call BTNL ACPI method
- platform/x86/intel/hid: Add HP Dragonfly G2 to VGBS DMI quirks
- platform/x86: think-lmi: Use kfree_sensitive instead of kfree
- platform/x86: asus-wmi: Fix setting RGB mode on some TUF laptops
- platform/x86: huawei-wmi: Silence ambient light sensor
- drm/amd/smu: use AverageGfxclkFrequency* to replace previous GFX Curr
Clock
- drm/amd/display: Guard DCN31 PHYD32CLK logic against chip family
- drm/amd/display: Exit idle optimizations before attempt to access PHY
- ovl: Always reevaluate the file signature for IMA
- ata: pata_arasan_cf: Use dev_err_probe() instead dev_err() in data_xfer()
- ALSA: usb-audio: Update for native DSD support quirks
- staging: fbtft: ili9341: use macro FBTFT_REGISTER_SPI_DRIVER
- security: keys: perform capable check only on privileged operations
- kprobes: Prohibit probing on CFI preamble symbol
- clk: fixed-mmio: make COMMON_CLK_FIXED_MMIO depend on HAS_IOMEM
- vmbus_testing: fix wrong python syntax for integer value comparison
- Revert "wifi: ath6k: silence false positive -Wno-dangling-pointer warning
on
GCC 12"
- net: dsa: microchip: KSZ9477 register regmap alignment to 32 bit
boundaries
- net: annotate data-races around sk->sk_{rcv|snd}timeo
- net: usb: qmi_wwan: add Quectel EM05GV2
- wifi: brcmfmac: Fix field-spanning write in brcmf_scan_params_v2_to_v1()
- powerpc/powermac: Use early_* IO variants in via_calibrate_decr()
- idmaengine: make FSL_EDMA and INTEL_IDMA64 depends on HAS_IOMEM
- platform/x86/amd/pmf: Fix unsigned comparison with less than zero
- scsi: lpfc: Remove reftag check in DIF paths
- scsi: qedi: Fix potential deadlock on _percpu->p_work_lock
- net: hns3: restore user pause configure when disable autoneg
- drm/amdgpu: Match against exact bootloader status
- wifi: cfg80211: remove links only on AP
- wifi: mac80211: Use active_links instead of valid_links in Tx
- netlabel: fix shift wrapping bug in netlbl_catmap_setlong()
- bnx2x: fix page fault following EEH recovery
- cifs: fix sockaddr comparison in iface_cmp
- cifs: fix max_credits implementation
- sctp: handle invalid error codes without calling BUG()
- scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity
- scsi: storvsc: Always set no_report_opcodes
- scsi: lpfc: Fix incorrect big endian type assignment in bsg loopback path
- LoongArch: Let pmd_present() return true when splitting pmd
- LoongArch: Fix the write_fcsr() macro
- ALSA: seq: oss: Fix racy open/close of MIDI devices
- net: sfp: handle 100G/25G active optical cables in sfp_parse_support
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug was fixed in the package linux-oem-6.5 - 6.5.0-1004.4
---
linux-oem-6.5 (6.5.0-1004.4) jammy; urgency=medium
* jammy/linux-oem-6.5: 6.5.0-1004.4 -proposed tracker (LP: #2036238)
* Infiniate systemd loop when power off the machine with multiple MD RAIDs
(LP: #2036184)
- SAUCE: md: do not _put wrong device in md_seq_next
* dell-uart-backlight fails to communicate with the scalar IC somtimes.
(LP: #2035299)
- SAUCE: platform/x86: dell-uart-backlight: add small delay after write
command
[ Ubuntu: 6.5.0-6.6 ]
* mantic/linux: 6.5.0-6.6 -proposed tracker (LP: #2035595)
* Mantic update: v6.5.3 upstream stable release (LP: #2035588)
- drm/amd/display: ensure async flips are only accepted for fast updates
- cpufreq: intel_pstate: set stale CPU frequency to minimum
- tpm: Enable hwrng only for Pluton on AMD CPUs
- Input: i8042 - add quirk for TUXEDO Gemini 17 Gen1/Clevo PD70PN
- Revert "fuse: in fuse_flush only wait if someone wants the return code"
- Revert "f2fs: clean up w/ sbi->log_sectors_per_block"
- Revert "PCI: tegra194: Enable support for 256 Byte payload"
- Revert "net: macsec: preserve ingress frame ordering"
- reiserfs: Check the return value from __getblk()
- splice: always fsnotify_access(in), fsnotify_modify(out) on success
- splice: fsnotify_access(fd)/fsnotify_modify(fd) in vmsplice
- splice: fsnotify_access(in), fsnotify_modify(out) on success in tee
- eventfd: prevent underflow for eventfd semaphores
- fs: Fix error checking for d_hash_and_lookup()
- iomap: Remove large folio handling in iomap_invalidate_folio()
- tmpfs: verify {g,u}id mount options correctly
- selftests/harness: Actually report SKIP for signal tests
- vfs, security: Fix automount superblock LSM init problem, preventing NFS
sb
sharing
- ARM: ptrace: Restore syscall restart tracing
- ARM: ptrace: Restore syscall skipping for tracers
- btrfs: zoned: skip splitting and logical rewriting on pre-alloc write
- erofs: release ztailpacking pclusters properly
- locking/arch: Avoid variable shadowing in local_try_cmpxchg()
- refscale: Fix uninitalized use of wait_queue_head_t
- clocksource: Handle negative skews in "skew is too large" messages
- powercap: arm_scmi: Remove recursion while parsing zones
- OPP: Fix potential null ptr dereference in
dev_pm_opp_get_required_pstate()
- OPP: Fix passing 0 to PTR_ERR in _opp_attach_genpd()
- selftests/resctrl: Add resctrl.h into build deps
- selftests/resctrl: Don't leak buffer in fill_cache()
- selftests/resctrl: Unmount resctrl FS if child fails to run benchmark
- selftests/resctrl: Close perf value read fd on errors
- sched/fair: remove util_est boosting
- arm64/ptrace: Clean up error handling path in sve_set_common()
- sched/psi: Select KERNFS as needed
- cpuidle: teo: Update idle duration estimate when choosing shallower state
- x86/decompressor: Don't rely on upper 32 bits of GPRs being preserved
- arm64/fpsimd: Only provide the length to cpufeature for xCR registers
- sched/rt: Fix sysctl_sched_rr_timeslice intial value
- perf/imx_ddr: don't enable counter0 if none of 4 counters are used
- selftests/futex: Order calls to futex_lock_pi
- irqchip/loongson-eiointc: Fix return value checking of eiointc_index
- ACPI: x86: s2idle: Post-increment variables when getting constraints
- ACPI: x86: s2idle: Fix a logic error parsing AMD constraints table
- thermal/of: Fix potential uninitialized value access
- cpufreq: amd-pstate-ut: Remove module parameter access
- cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver
- tools/nolibc: arch-*.h: add missing space after ','
- tools/nolibc: fix up startup failures for -O0 under gcc < 11.1.0
- x86/efistub: Fix PCI ROM preservation in mixed mode
- cpufreq: powernow-k8: Use related_cpus instead of cpus in driver.exit()
- cpufreq: tegra194: add online/offline hooks
- cpufreq: tegra194: remove opp table in exit hook
- selftests/bpf: Fix bpf_nf failure upon test rerun
- libbpf: only reset sec_def handler when necessary
- bpftool: use a local copy of perf_event to fix accessing :: Bpf_cookie
- bpftool: Define a local bpf_perf_link to fix accessing its fields
- bpftool: Use a local copy of BPF_LINK_TYPE_PERF_EVENT in pid_iter.bpf.c
- bpftool: Use a local bpf_perf_event_value to fix accessing its fields
- libbpf: Fix realloc API handling in zero-sized edge cases
- bpf: Clear the probe_addr for uprobe
- bpf: Fix an error around PTR_UNTRUSTED
- bpf: Fix an error in verifying a field in a union
- crypto: qat - change value of default idle filter
- tcp: tcp_enter_quickack_mode() should be static
- hwrng: nomadik - keep clock enabled while hwrng is registered
- hwrng: pic32 - use devm_clk_get_enabled
- regmap: maple: Use
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Mantic) Status: Confirmed => Fix Committed -- 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/2034504 Title: Enable ASPM for NVMe behind VMD 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: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed 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: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed 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: Confirmed 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
** Tags removed: verification-needed-jammy-linux-oem-6.1 ** Tags added: verification-done-jammy-linux-oem-6.1 -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed 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: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed 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: Confirmed 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1023.23 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-done- jammy-linux-oem-6.1'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.1' to 'verification-failed-jammy- linux-oem-6.1'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.1-v2 verification-needed-jammy-linux-oem-6.1 -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed 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: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed 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: Confirmed 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed 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: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed 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: Confirmed 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
[Kernel-packages] [Bug 2034504] Re: Enable ASPM for NVMe behind VMD
** Tags added: oem-priority originate-from-200 somerville ** Tags added: originate-from-2032928 -- 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/2034504 Title: Enable ASPM for NVMe behind VMD Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed 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: New Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed 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: Confirmed 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] ASPM of NVMe behind VMD is not enabled when BIOS FADT doesn't allow ASPM to be modified. That causes higher overall power consumption. [Fix] Allow ASPM to be enabled. While at this, remove old cruft that can interfere upstream VMD driver. [Test] Check the value of `/sys/kernel/debug/pmc_core/slp_s0_residency_usec`. Now system can reach deepest power saving state during sleep. [Where problems could occur] Some NVMe may have I/O issue when ASPM is enabled. But for this scenario the issue will also appear when VMD is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034504/+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
