From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Smita Koralahalli" <Smita.KoralahalliChannabasappa@amd.com>,
linux-pci@vger.kernel.org
Subject: Re: [bugzilla-daemon@kernel.org: [Bug 218765] New: broken device, retraining non-functional downstream link at 2.5GT/s]
Date: Wed, 24 Apr 2024 12:58:24 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2404241240530.9972@angie.orcam.me.uk> (raw)
In-Reply-To: <20240423152330.GA441398@bhelgaas>
On Tue, 23 Apr 2024, Bjorn Helgaas wrote:
> FYI. The retraining was added by a89c82249c37 ("PCI: Work around PCIe
> link training failures").
>
> Paul, is this a regression? a89c82249c37 appeared in v6.5. I
> *assume* whatever is below bus 01 did actually work before v6.5, in
> spite of the fact that apparently PCI_EXP_LNKSTA_DLLLA was not set
> when we enumerated the 00:1c.0 Root Port?
Bjorn,
Has <https://patchwork.kernel.org/project/linux-pci/list/?series=824858>
gone anywhere? I believe this would've addressed the issue of the delay.
Over the last couple of months Ilpo and myself have been discussing the
issue of clearing leftover LBMS state and Smita has literally just posted
a proposed solution for that, which I haven't yet had time to go through.
The combination of a new day job, overall shortage of time, and hardware
playing tricks with me has contributed to me not having made anything in
this area recently. I haven't lost interest though and I'll see what I
can do.
Maciej
prev parent reply other threads:[~2024-04-24 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 15:23 [bugzilla-daemon@kernel.org: [Bug 218765] New: broken device, retraining non-functional downstream link at 2.5GT/s] Bjorn Helgaas
2024-04-23 15:40 ` Paul Menzel
2024-04-24 11:58 ` Maciej W. Rozycki [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=alpine.DEB.2.21.2404241240530.9972@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.