[Kernel-packages] [Bug 2042385] Re: Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on
This bug was fixed in the package linux - 6.8.0-11.11 --- linux (6.8.0-11.11) noble; urgency=medium * noble/linux: 6.8.0-11.11 -proposed tracker (LP: #2053094) * Miscellaneous Ubuntu changes - [Packaging] riscv64: disable building unnecessary binary debs -- Paolo Pisati Wed, 14 Feb 2024 00:04:31 +0100 ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Released -- 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/2042385 Title: Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. [Misc] For Unstable, built with mantic configuration ~~~ $ git push m_cbd remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx remote: * 1/9 workers busy, 0 builds queued remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK remote: 2023-11-20 16:14:16 kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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 2042385] Re: Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on
** Summary changed: - Fix RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on + Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on -- 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/2042385 Title: Fix RPL-U CPU C-state always keep at C3 when system run PHM with idle screen on Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] RPL-U CPU C-state alway keep at C3 when system run PHM with idle screen on. [Fix] Realtek r8168h/r8111's ASPM is blocked due to users report the regression on their platform[0]. Add quirks for some Dell Platforms to enable ASPM and allow RPL-U sleep deeper. [0], https://bugzilla.kernel.org/show_bug.cgi?id=217814 [where the issue could happen] Medium, may have the regression but the risk is limited in some Dell platforms. we will ask Realtek's effort once the regression is observed. [Misc] For Unstable, built with mantic configuration ~~~ $ git push m_cbd remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-c281d2b48f02-DyYx remote: * 1/9 workers busy, 0 builds queued remote: 2023-11-20 16:19:03 kobako-mantic-c281d2b48f02-DyYx/amd64/BUILD-OK remote: 2023-11-20 16:21:38 kobako-mantic-c281d2b48f02-DyYx/arm64/BUILD-OK remote: 2023-11-20 16:18:54 kobako-mantic-c281d2b48f02-DyYx/armhf/BUILD-OK remote: 2023-11-20 16:22:08 kobako-mantic-c281d2b48f02-DyYx/ppc64el/BUILD-OK remote: 2023-11-20 16:14:16 kobako-mantic-c281d2b48f02-DyYx/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next ~~~ To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042385/+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
