public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: "Matthew W Carlis" <mattc@purestorage.com>,
	ahuang12@lenovo.com, alok.a.tiwari@oracle.com,
	ashishk@purestorage.com, "Bjorn Helgaas" <bhelgaas@google.com>,
	guojinhui.liam@bytedance.com,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	jiwei.sun.bj@qq.com, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, "Lukas Wunner" <lukas@wunner.de>,
	msaggi@purestorage.com, sconnor@purestorage.com,
	sunjw10@lenovo.com
Subject: Re: [PATCH] PCI: Always lift 2.5GT/s restriction in PCIe failed link retraining
Date: Mon, 23 Feb 2026 11:36:03 -0600	[thread overview]
Message-ID: <20260223173603.GA3698515@bhelgaas> (raw)
In-Reply-To: <alpine.DEB.2.21.2602200124060.61446@angie.orcam.me.uk>

On Fri, Feb 20, 2026 at 12:03:17PM +0000, Maciej W. Rozycki wrote:
> On Thu, 19 Feb 2026, Bjorn Helgaas wrote:
> 
> > > Can we reconsider my patch that restricts the link retrain mechanism
> > > to the specific device that created the work-around?
> > > https://lore.kernel.org/all/20250702052430.13716-1-mattc@purestorage.com/
> > 
> > I think we already at least potentially meddle with the link on every
> > device, and it definitely makes me nervous.  I would like it much
> > better if it's possible to limit it to devices with known defects.
> > 
> > I'll defer these for now and we can see if a consensus emerges.
> 
> As I say it's logically impossible to figure out whether or not to
> apply such a workaround where the culprit is the downstream device,
> because until you've succeeded establishing a link you have no way
> to figure out what the downstream device actually is.

IIUC Matthew [1] and Alok [2] have reported issues that only happen
when we run pcie_failed_link_retrain().  The issues seem to be with
NVMe devices, but I don't see a root cause or a solution (other than
skipping pcie_failed_link_retrain()).

[1] https://lore.kernel.org/all/20250702052430.13716-2-mattc@purestorage.com/
[2] https://lore.kernel.org/all/c296df33-f9c0-42f7-8add-6966d89d00c4@oracle.com/

  reply	other threads:[~2026-02-23 17:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 19:24 [PATCH v2 0/3] PCI: Always lift 2.5GT/s restriction in PCIe failed link retraining Maciej W. Rozycki
2025-12-08 19:24 ` [PATCH v2 1/3] " Maciej W. Rozycki
2026-02-05 11:00   ` [External] : " ALOK TIWARI
2025-12-08 19:24 ` [PATCH v2 2/3] PCI: Use pcie_get_speed_cap() " Maciej W. Rozycki
2026-02-05 10:59   ` [External] : " ALOK TIWARI
2025-12-08 19:24 ` [PATCH v2 3/3] PCI: Bail out early for 2.5GT/s devices " Maciej W. Rozycki
2026-02-05 10:57   ` [External] : " ALOK TIWARI
2026-02-04 17:12 ` [PING][PATCH v2 0/3] PCI: Always lift 2.5GT/s restriction " Maciej W. Rozycki
2026-02-19  3:42   ` ALOK TIWARI
2026-03-09 15:45     ` ALOK TIWARI
2026-02-19 21:26 ` [PATCH " Bjorn Helgaas
2026-02-19 22:09   ` [PATCH] " Matthew W Carlis
2026-02-19 22:53     ` Bjorn Helgaas
2026-02-20 12:03       ` Maciej W. Rozycki
2026-02-23 17:36         ` Bjorn Helgaas [this message]
2026-02-23 22:49           ` Matthew W Carlis
2026-02-23 23:14           ` Maciej W. Rozycki
2026-02-25  1:41             ` Matthew W Carlis
2026-02-26 22:02               ` Maciej W. Rozycki
2026-03-26 19:52                 ` ALOK TIWARI
  -- strict thread matches above, loose matches on Subject: below --
2025-12-01  3:52 Maciej W. Rozycki
2025-12-01  9:45 ` Ilpo Järvinen
2025-12-01 13:55   ` Maciej W. Rozycki
2025-12-01 16:48     ` Ilpo Järvinen
2025-12-08 19:24     ` Maciej W. Rozycki
2025-12-04 18:30 ` Matthew W Carlis
2025-12-08 19:25   ` Maciej W. Rozycki

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=20260223173603.GA3698515@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=ahuang12@lenovo.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=ashishk@purestorage.com \
    --cc=bhelgaas@google.com \
    --cc=guojinhui.liam@bytedance.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jiwei.sun.bj@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=macro@orcam.me.uk \
    --cc=mattc@purestorage.com \
    --cc=msaggi@purestorage.com \
    --cc=sconnor@purestorage.com \
    --cc=sunjw10@lenovo.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