[Bug 1962349] [NEW] Bolt doesn't work with native USB4 hosts
Launchpad Bug Tracker
1962349 at bugs.launchpad.net
Wed Mar 9 08:16:08 UTC 2022
You have been subscribed to a public bug by You-Sheng Yang (vicamo):
[Impact]
* AMD Yellow Carp provides integrated USB4 host controllers
* When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring"
[Test Plan]
* Plug in USB4 device or TBT3 to AMD Yellow Carp host
* Ensure that PCI topology has populated
* Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0"
* Try to run `boltctl enroll $UUID`
[Where problems could occur]
* Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt.
* This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time.
* There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release.
[Other Info]
* This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy.
* It is fixed in bolt 0.9.1 or later release.
* To solve the SRU, will backport 0.9.1 release from Impish.
* I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd".
** Affects: bolt (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: bolt (Ubuntu Focal)
Importance: Undecided
Status: In Progress
** Affects: bolt (Ubuntu Impish)
Importance: Undecided
Status: Fix Released
** Affects: bolt (Ubuntu Jammy)
Importance: Undecided
Status: Fix Released
--
Bolt doesn't work with native USB4 hosts
https://bugs.launchpad.net/bugs/1962349
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list