mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomasz Bojanowski <tomasz@bojanowski.me>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org
Cc: "Maciej W. Rozycki" <macro@orcam.me.uk>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Andreas Wild" <andiwild@gmail.com>,
	linux-kernel@vger.kernel.org,
	"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: PCI: failed link retraining quirk costs 1 s per empty AMD Promontory 21 port
Date: Tue, 6 Oct 2026 00:21:37 +0200 (CEST)	[thread overview]
Message-ID: <1140966133.1231391.1791238897910@app.mailbox.org> (raw)
In-Reply-To: <22e0563e-afcd-44f5-9d87-f0b2a637038e@leemhuis.info>


> 04.10.2026 17:29 CEST Thorsten Leemhuis <regressions@leemhuis.info> napisał(a):
> Hmm, nobody replied afaics (or did I miss something), so it seems nobody
> has an idea what's wrong here. So I guess you need to perform a git
> bisection.

Thanks for following up.  You did not miss anything, there were no
replies so far.

I am not sure a bisection is possible though: I do not know of any
kernel where this does not happen.  I see the same 2 s delay on 7.1.x
(openSUSE) and on 7.2.x (Fedora), and I believe it was already there
on 6.19 and 7.0 as well, so I did not mean to report it as a
regression, sorry if the report read that way.  As far as I can tell
the quirk simply behaves as written: LBMS is set on a port with no
link, so the "broken device" branch is taken and the retrain times out.

I would be grateful for a hint from the PCI folks on whether this is
expected on empty ports.

Thanks,
Tomasz

      reply	other threads:[~2026-10-05 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 19:13 Tomasz Bojanowski
2026-10-04 15:29 ` Thorsten Leemhuis
2026-10-05 22:21   ` Tomasz Bojanowski [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=1140966133.1231391.1791238897910@app.mailbox.org \
    --to=tomasz@bojanowski.me \
    --cc=andiwild@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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®