From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218795] USB4 / Thunderbolt + AMD: unstable and slow link (many uncorrectable errors)
Date: Thu, 07 Nov 2024 17:30:29 +0000 [thread overview]
Message-ID: <bug-218795-208809-Z787QjxHh8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218795-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218795
--- Comment #4 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> pci 0000:35:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s
> PCIe x1 link at 0000:00:04.1 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4
> link)
It's worth mentioning that this message is meaningless in the context of USB4.
There were various discussions on the mailing lists about changing this, but it
never landed anywhere.
https://lore.kernel.org/linux-usb/20231103190758.82911-1-mario.limonciello@amd.com/
See specifically patch 8 for more context and the specs that indicate why it
behaves this way.
At least with AMD dGPUs put in eGPU enclosures this was causing problems for
amdgpu because if used pcie_bandwidth_available(). We've changed this in
amdgpu to look at the link partner to exclude this causing issues.
https://github.com/torvalds/linux/blob/v6.12-rc5/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c#L5903
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-11-07 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 11:41 [Bug 218795] New: USB4 / Thunderbolt + AMD: unstable and slow link (many uncorrectable errors) bugzilla-daemon
2024-11-05 17:17 ` [Bug 218795] " bugzilla-daemon
2024-11-05 17:36 ` bugzilla-daemon
2024-11-06 10:29 ` bugzilla-daemon
2024-11-07 17:30 ` bugzilla-daemon [this message]
2024-11-07 17:45 ` bugzilla-daemon
2024-11-08 8:43 ` bugzilla-daemon
2024-11-08 15:41 ` bugzilla-daemon
2024-11-08 19:19 ` bugzilla-daemon
2024-11-20 11:11 ` bugzilla-daemon
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=bug-218795-208809-Z787QjxHh8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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 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).