From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Andrew <andreasx0@protonmail.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
Matthew W Carlis <mattc@purestorage.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Fix link speed calculation on retrain failure
Date: Tue, 24 Jun 2025 14:23:33 +0300 (EEST) [thread overview]
Message-ID: <78b87a33-3e46-aabd-3f88-db5c1130c20c@linux.intel.com> (raw)
In-Reply-To: <1c92ef6bcb314ee6977839b46b393282e4f52e74.1750684771.git.lukas@wunner.de>
[-- Attachment #1: Type: text/plain, Size: 2759 bytes --]
On Mon, 23 Jun 2025, Lukas Wunner wrote:
> When pcie_failed_link_retrain() fails to retrain, it tries to revert to
> the previous link speed. However it calculates that speed from the Link
> Control 2 register without masking out non-speed bits first.
>
> PCIE_LNKCTL2_TLS2SPEED() converts such incorrect values to
> PCI_SPEED_UNKNOWN, which in turn causes a WARN splat in
> pcie_set_target_speed():
>
> pci 0000:00:01.1: [1022:14ed] type 01 class 0x060400 PCIe Root Port
> pci 0000:00:01.1: broken device, retraining non-functional downstream link at 2.5GT/s
> pci 0000:00:01.1: retraining failed
> WARNING: CPU: 1 PID: 1 at drivers/pci/pcie/bwctrl.c:168 pcie_set_target_speed
> RDX: 0000000000000001 RSI: 00000000000000ff RDI: ffff9acd82efa000
> pcie_failed_link_retrain
> pci_device_add
> pci_scan_single_device
> pci_scan_slot
> pci_scan_child_bus_extend
> acpi_pci_root_create
> pci_acpi_scan_root
> acpi_pci_root_add
> acpi_bus_attach
> device_for_each_child
> acpi_dev_for_each_child
> acpi_bus_attach
> device_for_each_child
> acpi_dev_for_each_child
> acpi_bus_attach
> acpi_bus_scan
> acpi_scan_init
> acpi_init
>
> Per the calling convention of the System V AMD64 ABI, the arguments to
> pcie_set_target_speed(struct pci_dev *, enum pci_bus_speed, bool) are
> stored in RDI, RSI, RDX. As visible above, RSI contains 0xff, i.e.
> PCI_SPEED_UNKNOWN.
>
> Fixes: f68dea13405c ("PCI: Revert to the original speed after PCIe failed link retraining")
> Reported-by: Andrew <andreasx0@protonmail.com>
> Closes: https://lore.kernel.org/r/7iNzXbCGpf8yUMJZBQjLdbjPcXrEJqBxy5-bHfppz0ek-h4_-G93b1KUrm106r2VNF2FV_sSq0nENv4RsRIUGnlYZMlQr2ZD2NyB5sdj5aU=@protonmail.com/
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
> Cc: stable@vger.kernel.org # v6.12+
> ---
> drivers/pci/quirks.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index d7f4ee6..deaaf4f 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -108,7 +108,7 @@ int pcie_failed_link_retrain(struct pci_dev *dev)
> pcie_capability_read_word(dev, PCI_EXP_LNKCTL2, &lnkctl2);
> pcie_capability_read_word(dev, PCI_EXP_LNKSTA, &lnksta);
> if (!(lnksta & PCI_EXP_LNKSTA_DLLLA) && pcie_lbms_seen(dev, lnksta)) {
> - u16 oldlnkctl2 = lnkctl2;
> + u16 oldlnkctl2 = lnkctl2 & PCI_EXP_LNKCTL2_TLS;
>
> pci_info(dev, "broken device, retraining non-functional downstream link at 2.5GT/s\n");
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
IIRC, there was a patch from somebody else which fixed this a bit
differently but never got applied (many months ago by now).
--
i.
next prev parent reply other threads:[~2025-06-24 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:22 [PATCH] PCI: Fix link speed calculation on retrain failure Lukas Wunner
2025-06-23 13:49 ` Sathyanarayanan Kuppuswamy
2025-06-24 11:23 ` Ilpo Järvinen [this message]
2025-06-24 12:19 ` Lukas Wunner
2025-06-24 12:28 ` Ilpo Järvinen
2025-06-24 16:48 ` Bjorn Helgaas
2025-06-24 18:13 ` Sathyanarayanan Kuppuswamy
2025-06-25 16:06 ` andreasx0
2025-06-25 17:46 ` Bjorn Helgaas
2025-06-26 22:33 ` andreasx0
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=78b87a33-3e46-aabd-3f88-db5c1130c20c@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andreasx0@protonmail.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=macro@orcam.me.uk \
--cc=mattc@purestorage.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;
as well as URLs for NNTP newsgroup(s).