From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4737635C6BE; Tue, 21 Jul 2026 21:29:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784669348; cv=none; b=ijXNhh9q89fDZc9QS4HWstvcZErHIWoDuWzzrH0NDC/bzCgw+NthHIh8AQF+p17bHUVHtO+fwAXGk2n2N72NbXgv+pCMJMh1CD+qz7hkPiWs7YFQy/ANmnO95B2jWIi38nFreJm8Xnx4zyYtXUOcfl+XCoZDs81vIy1A4xusLVg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784669348; c=relaxed/simple; bh=cIEupPf6Cz0EJZ2kteLyjenCsXsq7BKLe5KSY8j6soM=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=Uog1Y/gxdTbLOrUTVuWruZVnMNfrACjRzhFylBq/fBBAXA2bEJXJwYjOEKu2dsSQeBnb6kOE1CeDn7okPAxajJQGBrWrsw7EJfvdPCD32BYOXwp3OBApvQ7z5eZTN8a/Bh+yJ9u3PGaTiGsXeTONqw0FHZ8qzcTBDB2bCxEFD7c= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=eR2lLdQI; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="eR2lLdQI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5A3EE1F00A3A; Tue, 21 Jul 2026 21:29:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784669342; bh=N93/PkrpMpa7xf6p17AlUfABQgQnaDHbrRRRETv6Knc=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=eR2lLdQI+IC7drQUGybTWeZ9k3n/9QmpEBNPale7CwnopLnqMa/8rvfCfD/0Iia8p /9rvEt/HMCDhKRQHAqU1RdEI3sFgNjhKog+AUIb8wTLC5qEL9lHs6ep88uMJm4h/r+ 0pvjCHV/mmr1ulRnOZUdAh5UkMlJtNAyt3U+kfuY= From: Greg Kroah-Hartman To: stable@vger.kernel.org Cc: Greg Kroah-Hartman , patches@lists.linux.dev, "Carlos Bilbao (Lambda)" , Bjorn Helgaas , Sasha Levin Subject: [PATCH 6.1 0475/1067] PCI/ASPM: Dont reconfigure ASPM entering low-power state Date: Tue, 21 Jul 2026 17:17:56 +0200 Message-ID: <20260721152435.240835154@linuxfoundation.org> X-Mailer: git-send-email 2.55.0 In-Reply-To: <20260721152424.521567757@linuxfoundation.org> References: <20260721152424.521567757@linuxfoundation.org> User-Agent: quilt/0.69 X-stable: review X-Patchwork-Hint: ignore Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 6.1-stable review patch. If anyone has any objections, please let me know. ------------------ From: Carlos Bilbao [ Upstream commit c855c9921da72e535c24737c748f603a52d03f7e ] Reconfiguring ASPM when a device transitions to low-power state can enable L1.1/L1.2 substates on the PCIe link at a time when the device is sleeping and may be unable to exit them. ASPM should be reconfigured on D0 entry (resume), not on the way down. pci_set_low_power_state() calls pcie_aspm_pm_state_change() after writing D3hot to PCI_PM_CTRL. pcie_aspm_pm_state_change() resets link->aspm_capable to link->aspm_support and then calls pcie_config_aspm_path(), which can enable ASPM L1.1/L1.2 substates on the PCIe link. If the device cannot recover the link from L1.2 while in D3hot, subsequent config space reads return 0xFFFF ("device inaccessible") and pci_power_up() fails with messages like: vfio-pci 0000:5d:00.0: Unable to change power state from D3hot to D0, device inaccessible This was observed on NVIDIA H100 SXM5 GPUs bound to vfio-pci when Linux runtime PM suspends them to D3hot: the GPU becomes permanently inaccessible and disappears from the PCIe bus. The call to pcie_aspm_pm_state_change() in pci_set_low_power_state() was restored by f93e71aea6c6 ("Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()""), which reverted 08d0cc5f3426 ("PCI/ASPM: Remove pcie_aspm_pm_state_change()"). The revert was necessary because the removal broke suspend/resume on certain platforms that required ASPM to be reconfigured on D0 entry. However, the revert restored the call in both pci_set_full_power_state() (D0 entry) and pci_set_low_power_state() (low-power entry). Only the D0-entry call is needed to fix the suspend/resume regression. The low-power-entry call is harmful: reconfiguring ASPM immediately after putting a device into D3hot can enable link substates that the device or platform cannot exit while the device is sleeping. Remove the pcie_aspm_pm_state_change() call from pci_set_low_power_state(). ASPM will still be reconfigured correctly when the device returns to D0 via pci_set_full_power_state(). Fixes: f93e71aea6c6 ("Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()"") Signed-off-by: Carlos Bilbao (Lambda) Signed-off-by: Bjorn Helgaas Link: https://patch.msgid.link/20260428040104.78524-1-carlos.bilbao@kernel.org Signed-off-by: Sasha Levin --- drivers/pci/pci.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c index 953646cd759b03..92fa1e9444a99f 100644 --- a/drivers/pci/pci.c +++ b/drivers/pci/pci.c @@ -1488,9 +1488,6 @@ static int pci_set_low_power_state(struct pci_dev *dev, pci_power_t state, bool pci_power_name(dev->current_state), pci_power_name(state)); - if (dev->bus->self) - pcie_aspm_pm_state_change(dev->bus->self, locked); - return 0; } -- 2.53.0