[Bug 1962349] Re: Bolt doesn't work with native USB4 hosts

[You-Sheng Yang]

One of the proposed kernel fix affects kernels >= 4.19, but we don't
have tbt support plan on the affected AMD platforms then.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Focal)
       Status: New => Won't Fix

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Jammy)
       Status: New => Triaged

** Changed in: linux (Ubuntu Jammy)
     Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux (Ubuntu Impish)
       Status: New => Won't Fix

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: linux-oem-5.14 (Ubuntu Focal)
       Status: New => Triaged

** Changed in: linux-oem-5.14 (Ubuntu Focal)
     Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-oem-5.14 (Ubuntu Impish)
       Status: New => Invalid

** Changed in: linux-oem-5.14 (Ubuntu Jammy)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1962349

Title:
  Bolt doesn't work with native USB4 hosts

Status in bolt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in bolt source package in Focal:
  In Progress
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Triaged
Status in bolt source package in Impish:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in bolt source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Triaged
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [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".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1962349/+subscriptions