From: Bjorn Helgaas <helgaas@kernel.org>
To: Max Lee <max.lee@canonical.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, acelan.kao@canonical.com,
mani@kernel.org, kaihengf@nvidia.com, victorshihgli@gmail.com,
lukas@wunner.de, pandoh@google.com, stable@vger.kernel.org
Subject: Re: [PATCH v4] PCI: Disable ASPM L0s for Realtek RTS525A
Date: Tue, 11 Aug 2026 04:39:44 -0500 [thread overview]
Message-ID: <20260811093944.GA605422@bhelgaas> (raw)
In-Reply-To: <20260707021527.639611-1-max.lee@canonical.com>
On Tue, Jul 07, 2026 at 10:15:27AM +0800, Max Lee wrote:
> The Realtek RTS525A PCIe card reader reports an AER Correctable Replay
> Timer Timeout storm when ASPM L0s is enabled on its link. On an affected
> HP ZBook Power 16 inch G11, the Root Port received tens of millions of
> AER interrupts from the RTS525A even when the rtsx_pci driver was
> blacklisted and the endpoint was not enabled by a driver.
>
> For example:
>
> pcieport 0000:00:1c.6: AER: Multiple Correctable error message received from 0000:58:00.0
> rtsx_pci 0000:58:00.0: PCIe Bus Error: severity=Correctable, type=Data Link Layer, (Transmitter ID)
> rtsx_pci 0000:58:00.0: device [10ec:525a] error status/mask=00001000/00006000
> rtsx_pci 0000:58:00.0: [12] Timeout
> pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:58:00.0
>
> Testing with OS-native AER control showed that disabling only L0s on the
> RTS525A link stops new AER interrupt and counter growth while leaving L1
> enabled. Disabling L1, L1 substates, or Clock PM alone did not stop the
> storm.
>
> Prevent the broken L0s configuration by removing L0s from the RTS525A
> advertised ASPM capability. This avoids enabling the non-working ASPM
> state instead of masking the resulting AER Replay Timer Timeout reports.
>
> Reviewed-by: Lukas Wunner <lukas@wunner.de>
> Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
> Cc: stable@vger.kernel.org
> Signed-off-by: Max Lee <max.lee@canonical.com>
Applied to pci/aspm for v7.3, thanks!
> ---
> Changes in v4:
> - Add an AER log snippet to make the quirk easier to find.
> - Reword the RTS525A comment to describe this as a Replay Timer Timeout storm.
> - Add Reviewed-by tags from Lukas Wunner and Manivannan Sadhasivam.
> - Add Cc stable tag as suggested by Lukas Wunner.
>
> drivers/pci/quirks.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index caaed1a01dc0..ab94bd7f3a34 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -2520,6 +2520,9 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x10f1, quirk_disable_aspm_l0s);
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x10f4, quirk_disable_aspm_l0s);
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1508, quirk_disable_aspm_l0s);
>
> +/* Realtek RTS525A generates a Replay Timer Timeout storm when L0s is enabled. */
> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_REALTEK, 0x525a, quirk_disable_aspm_l0s);
> +
> static void quirk_disable_aspm_l0s_l1(struct pci_dev *dev)
> {
> pcie_aspm_remove_cap(dev,
> --
> 2.43.0
>
prev parent reply other threads:[~2026-08-11 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 3:23 [PATCH] PCI: Mask Replay Timer Timeout " Max Lee
2026-06-10 2:47 ` [PATCH v2] " Max Lee
2026-07-01 6:27 ` Manivannan Sadhasivam
2026-07-01 20:42 ` Bjorn Helgaas
2026-07-02 5:10 ` Lukas Wunner
2026-07-02 7:06 ` Max Lee
2026-07-02 14:42 ` Lukas Wunner
2026-07-06 2:34 ` Max Lee
2026-07-02 8:08 ` Manivannan Sadhasivam
2026-07-06 2:53 ` [PATCH v3] PCI: Disable ASPM L0s " Max Lee
2026-07-06 9:41 ` Lukas Wunner
2026-07-06 10:20 ` Manivannan Sadhasivam
2026-08-07 8:07 ` Lukas Wunner
2026-08-11 5:33 ` Manivannan Sadhasivam
2026-07-07 2:15 ` [PATCH v4] " Max Lee
2026-08-11 9:39 ` Bjorn Helgaas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260811093944.GA605422@bhelgaas \
--to=helgaas@kernel.org \
--cc=acelan.kao@canonical.com \
--cc=bhelgaas@google.com \
--cc=kaihengf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mani@kernel.org \
--cc=max.lee@canonical.com \
--cc=pandoh@google.com \
--cc=stable@vger.kernel.org \
--cc=victorshihgli@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®