Activity log for bug #2042500

Date Who What changed Old value New value Message
2023-11-02 02:04:15 koba bug added bug
2023-11-02 02:04:32 koba bug task added linux-oem-6.1 (Ubuntu)
2023-11-02 02:04:48 koba nominated for series Ubuntu Jammy
2023-11-02 02:04:48 koba bug task added linux-oem-6.1 (Ubuntu Jammy)
2023-11-02 02:04:48 koba bug task added linux-oem-6.5 (Ubuntu Jammy)
2023-11-02 02:04:48 koba nominated for series Ubuntu Noble
2023-11-02 02:04:48 koba bug task added linux-oem-6.1 (Ubuntu Noble)
2023-11-02 02:04:48 koba bug task added linux-oem-6.5 (Ubuntu Noble)
2023-11-02 02:05:05 koba bug task added linux (Ubuntu)
2023-11-02 02:05:12 koba linux (Ubuntu Noble): status New In Progress
2023-11-02 02:05:15 koba linux (Ubuntu Noble): assignee koba (kobako)
2023-11-02 02:05:19 koba linux-oem-6.1 (Ubuntu Jammy): status New In Progress
2023-11-02 02:05:21 koba linux-oem-6.1 (Ubuntu Jammy): assignee koba (kobako)
2023-11-02 02:05:24 koba linux-oem-6.5 (Ubuntu Jammy): status New In Progress
2023-11-02 02:05:27 koba linux-oem-6.5 (Ubuntu Jammy): assignee koba (kobako)
2023-11-02 02:06:07 koba bug added subscriber Canonical Hardware Enablement
2023-11-02 02:06:14 koba tags oem-priority originate-from-2035307 stella
2023-11-02 02:15:24 koba description [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] [where the issue could happen] low, [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but do that after PCIe capability is restored in pci_restore_aspm_state() following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream (this is already forced by the parent-child ordering of Linux Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems where these regressions happened, just in case. For the TUXEDO case we only skip restore if the BIOS is involved in system suspend (that's forcing "mem_sleep=deep" in the command line). This is to avoid possible power regression when the default suspend to idle is used, and at the same time make sure the devices continue working after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~ pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too.
2023-11-02 02:30:17 Viral Wang bug added subscriber Viral Wang
2023-11-10 08:27:20 Anthony Wong nominated for series Ubuntu Mantic
2023-11-10 08:27:20 Anthony Wong bug task added linux (Ubuntu Mantic)
2023-11-10 08:27:20 Anthony Wong bug task added linux-oem-6.1 (Ubuntu Mantic)
2023-11-10 08:27:20 Anthony Wong bug task added linux-oem-6.5 (Ubuntu Mantic)
2023-11-13 12:31:17 Ubuntu Kernel Bot tags oem-priority originate-from-2035307 stella kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-needed-jammy-linux-oem-6.5
2023-11-14 12:22:57 Timo Aaltonen linux-oem-6.5 (Ubuntu Jammy): status In Progress Fix Committed
2023-11-15 18:22:07 koba linux (Ubuntu Mantic): status New In Progress
2023-11-15 18:22:07 koba linux (Ubuntu Mantic): assignee koba (kobako)
2023-11-15 18:22:28 koba linux (Ubuntu Jammy): status New In Progress
2023-11-15 18:22:28 koba linux (Ubuntu Jammy): assignee koba (kobako)
2023-11-15 18:22:47 koba linux-oem-6.1 (Ubuntu Mantic): status New Invalid
2023-11-15 18:22:58 koba linux-oem-6.1 (Ubuntu Noble): status New Invalid
2023-11-15 18:23:09 koba linux-oem-6.5 (Ubuntu Mantic): status New Invalid
2023-11-15 18:23:21 koba linux-oem-6.5 (Ubuntu Noble): status New Invalid
2023-11-16 04:20:18 Kai-Heng Feng tags kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-needed-jammy-linux-oem-6.5 kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.5
2023-11-20 23:11:16 Launchpad Janitor linux-oem-6.5 (Ubuntu Jammy): status Fix Committed Fix Released
2023-11-20 23:11:16 Launchpad Janitor cve linked 2023-31085
2023-11-20 23:11:16 Launchpad Janitor cve linked 2023-4244
2023-11-20 23:11:16 Launchpad Janitor cve linked 2023-5090
2023-11-20 23:11:16 Launchpad Janitor cve linked 2023-5345
2023-11-20 23:11:16 Launchpad Janitor cve linked 2023-5633
2023-11-21 01:27:31 Ubuntu Kernel Bot tags kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.5 kernel-spammed-jammy-linux-oem-6.1-v2 kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.5 verification-needed-jammy-linux-oem-6.1
2023-11-21 06:38:25 Timo Aaltonen linux-oem-6.1 (Ubuntu Jammy): status In Progress Fix Committed
2023-11-24 01:23:12 AceLan Kao tags kernel-spammed-jammy-linux-oem-6.1-v2 kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.5 verification-needed-jammy-linux-oem-6.1 kernel-spammed-jammy-linux-oem-6.1-v2 kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5
2023-12-05 09:36:21 Launchpad Janitor linux-oem-6.1 (Ubuntu Jammy): status Fix Committed Fix Released
2023-12-23 04:47:45 AceLan Kao linux (Ubuntu Jammy): assignee koba (kobako) AceLan Kao (acelankao)
2023-12-23 04:47:57 AceLan Kao linux (Ubuntu Mantic): assignee koba (kobako) AceLan Kao (acelankao)
2023-12-23 04:48:09 AceLan Kao linux (Ubuntu Noble): assignee koba (kobako) AceLan Kao (acelankao)
2023-12-28 03:33:17 AceLan Kao linux (Ubuntu Jammy): status In Progress Invalid
2024-03-26 03:26:13 AceLan Kao linux (Ubuntu Mantic): status In Progress Won't Fix
2024-04-04 12:35:04 Timo Aaltonen bug task added linux-oem-6.8 (Ubuntu)
2024-04-04 12:35:18 Timo Aaltonen linux-oem-6.8 (Ubuntu Jammy): status New Invalid
2024-04-04 12:35:28 Timo Aaltonen linux-oem-6.8 (Ubuntu Mantic): status New Invalid
2024-04-08 07:32:58 AceLan Kao linux-oem-6.8 (Ubuntu Noble): status New In Progress
2024-04-08 07:32:58 AceLan Kao linux-oem-6.8 (Ubuntu Noble): assignee AceLan Kao (acelankao)
2024-04-08 07:42:13 AceLan Kao description [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but do that after PCIe capability is restored in pci_restore_aspm_state() following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream (this is already forced by the parent-child ordering of Linux Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems where these regressions happened, just in case. For the TUXEDO case we only skip restore if the BIOS is involved in system suspend (that's forcing "mem_sleep=deep" in the command line). This is to avoid possible power regression when the default suspend to idle is used, and at the same time make sure the devices continue working after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~ pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too. SRU Justification for Noble [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] The new series of the fix has been merged into v6.9 6d4266675279 PCI/ASPM: Update save_state when configuration changes 64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates c198fafa0125 PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state() 17423360a27a PCI/ASPM: Save L1 PM Substates Capability for suspend/resume 1e11b5494c3d PCI/ASPM: Move pci_save_ltr_state() to aspm.c f3994bba8200 PCI/ASPM: Always build aspm.c fa84f4435a62 PCI/ASPM: Move pci_configure_ltr() to aspm.c [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~  pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present  rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible  rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [Where the problems could occur] ============================= [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but    do that after PCIe capability is restored in pci_restore_aspm_state()    following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream    (this is already forced by the parent-child ordering of Linux    Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields    in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems    where these regressions happened, just in case. For the TUXEDO case    we only skip restore if the BIOS is involved in system suspend    (that's forcing "mem_sleep=deep" in the command line). This is to    avoid possible power regression when the default suspend to idle is    used, and at the same time make sure the devices continue working    after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~  pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present  rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible  rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too.
2024-04-11 01:30:56 AceLan Kao description SRU Justification for Noble [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] The new series of the fix has been merged into v6.9 6d4266675279 PCI/ASPM: Update save_state when configuration changes 64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates c198fafa0125 PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state() 17423360a27a PCI/ASPM: Save L1 PM Substates Capability for suspend/resume 1e11b5494c3d PCI/ASPM: Move pci_save_ltr_state() to aspm.c f3994bba8200 PCI/ASPM: Always build aspm.c fa84f4435a62 PCI/ASPM: Move pci_configure_ltr() to aspm.c [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~  pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present  rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible  rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [Where the problems could occur] ============================= [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but    do that after PCIe capability is restored in pci_restore_aspm_state()    following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream    (this is already forced by the parent-child ordering of Linux    Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields    in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems    where these regressions happened, just in case. For the TUXEDO case    we only skip restore if the BIOS is involved in system suspend    (that's forcing "mem_sleep=deep" in the command line). This is to    avoid possible power regression when the default suspend to idle is    used, and at the same time make sure the devices continue working    after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~  pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present  rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible  rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too. SRU Justification for Noble [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] The new series of the fix has been merged into v6.9 6d4266675279 PCI/ASPM: Update save_state when configuration changes 64dbb2d70744 PCI/ASPM: Disable L1 before configuring L1 Substates c198fafa0125 PCI/ASPM: Call pci_save_ltr_state() from pci_save_pcie_state() 17423360a27a PCI/ASPM: Save L1 PM Substates Capability for suspend/resume 1e11b5494c3d PCI/ASPM: Move pci_save_ltr_state() to aspm.c f3994bba8200 PCI/ASPM: Always build aspm.c fa84f4435a62 PCI/ASPM: Move pci_configure_ltr() to aspm.c [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~  pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present  rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible  rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [Where the problems could occur] Hard to evaluate, these patches change the PCI/ASPM behavior and may lead to PCI devices work abnormal. ============================= [Impact] checkbox test case, after-suspend-mediacard/sdhc-insert, failed. [Fix] Commit a7152be79b62 ("Revert "PCI/ASPM: Save L1 PM Substates Capability for suspend/resume"") reverted saving and restoring of ASPM L1 Substates due to a regression that caused resume from suspend to fail on certain systems. However, we never added this capability back and this is now causing systems fail to enter low power CPU states, drawing more power from the battery. The original revert mentioned that we restore L1 PM substate configuration even though ASPM L1 may already be enabled. This is due the fact that the pci_restore_aspm_l1ss_state() was called before pci_restore_pcie_state(). Try to enable this functionality again following PCIe r6.0.1, sec 5.5.4 more closely by: 1) Do not restore ASPM configuration in pci_restore_pcie_state() but    do that after PCIe capability is restored in pci_restore_aspm_state()    following PCIe r6.0, sec 5.5.4. 2) ASPM is first enabled on the upstream component and then downstream    (this is already forced by the parent-child ordering of Linux    Device Power Management framework). 3) Program ASPM L1 PM substate configuration before L1 enables. 4) Program ASPM L1 PM substate enables last after rest of the fields    in the capability are programmed. 5) Add denylist that skips restoring on the ASUS and TUXEDO systems    where these regressions happened, just in case. For the TUXEDO case    we only skip restore if the BIOS is involved in system suspend    (that's forcing "mem_sleep=deep" in the command line). This is to    avoid possible power regression when the default suspend to idle is    used, and at the same time make sure the devices continue working    after resume when the BIOS is involved. [Test Case] 1. suspend and resume. 2. check if the error appears in dmesg ~~~  pcieport 0000:00:1c.0: pciehp: Slot(5): Card not present  rtsx_pci 0000:05:00.0: Unable to change power state from D0 to D3hot, device inaccessible  rtsx_pci 0000:05:00.0: Unable to change power state from D3cold to D0, device inaccessible ~~~ [where the issue could happen] low, the patch works well on the reported malfunctioned ASUS platform too.
2024-04-26 13:06:52 Roxana Nicolescu linux (Ubuntu Noble): status In Progress Fix Committed
2024-05-06 18:14:52 Ubuntu Kernel Bot tags kernel-spammed-jammy-linux-oem-6.1-v2 kernel-spammed-jammy-linux-oem-6.5-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 kernel-spammed-jammy-linux-oem-6.1-v2 kernel-spammed-jammy-linux-oem-6.5-v2 kernel-spammed-noble-linux-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 verification-needed-noble-linux
2024-05-07 03:47:14 AceLan Kao tags kernel-spammed-jammy-linux-oem-6.1-v2 kernel-spammed-jammy-linux-oem-6.5-v2 kernel-spammed-noble-linux-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 verification-needed-noble-linux kernel-spammed-jammy-linux-oem-6.1-v2 kernel-spammed-jammy-linux-oem-6.5-v2 kernel-spammed-noble-linux-v2 oem-priority originate-from-2035307 stella verification-done-jammy-linux-oem-6.1 verification-done-jammy-linux-oem-6.5 verification-done-noble-linux