Public bug reported: [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. [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. ** Affects: bolt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: bolt (Ubuntu Focal) Importance: Undecided Status: New ** Affects: bolt (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Affects: bolt (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Also affects: bolt (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: bolt (Ubuntu Jammy) Status: New => Fix Released ** Description changed: [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" + * 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` + * 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. + * 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. [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.2 release from Jammy. + * 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. ** Changed in: bolt (Ubuntu Impish) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. 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 bolt source package in Focal: New Status in bolt source package in Impish: Fix Released Status in bolt source package in Jammy: Fix Released 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. [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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp