| 2022-02-25 22:15:09 |
Mario Limonciello |
bug |
|
|
added bug |
| 2022-02-25 22:15:23 |
Mario Limonciello |
nominated for series |
|
Ubuntu Impish |
|
| 2022-02-25 22:15:23 |
Mario Limonciello |
bug task added |
|
bolt (Ubuntu Impish) |
|
| 2022-02-25 22:15:23 |
Mario Limonciello |
nominated for series |
|
Ubuntu Focal |
|
| 2022-02-25 22:15:23 |
Mario Limonciello |
bug task added |
|
bolt (Ubuntu Focal) |
|
| 2022-02-25 22:15:36 |
Mario Limonciello |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-02-25 22:15:36 |
Mario Limonciello |
bug task added |
|
bolt (Ubuntu Jammy) |
|
| 2022-02-25 22:15:43 |
Mario Limonciello |
bolt (Ubuntu Jammy): status |
New |
Fix Released |
|
| 2022-02-25 22:20:00 |
Mario Limonciello |
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.2 release from Jammy. |
[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. |
|
| 2022-02-25 22:20:04 |
Mario Limonciello |
bolt (Ubuntu Impish): status |
New |
Fix Released |
|
| 2022-02-25 22:25:27 |
Mario Limonciello |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-02-26 14:25:24 |
Mario Limonciello |
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. |
[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". |
|
| 2022-02-26 14:26:37 |
Mario Limonciello |
bolt (Ubuntu Focal): status |
New |
In Progress |
|
| 2022-03-09 08:14:31 |
You-Sheng Yang |
attachment added |
|
bolt_0.9.1-2ubuntu0~20.04.1.debdiff https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1962349/+attachment/5567287/+files/bolt_0.9.1-2ubuntu0~20.04.1.debdiff |
|
| 2022-03-09 08:16:08 |
You-Sheng Yang |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2022-03-10 06:11:36 |
You-Sheng Yang |
bug task added |
|
linux (Ubuntu) |
|
| 2022-03-10 06:11:52 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.14 (Ubuntu) |
|
| 2022-03-10 06:13:11 |
You-Sheng Yang |
linux (Ubuntu Focal): status |
New |
Won't Fix |
|
| 2022-03-10 06:13:43 |
You-Sheng Yang |
linux (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-03-10 06:13:43 |
You-Sheng Yang |
linux (Ubuntu Jammy): status |
New |
Triaged |
|
| 2022-03-10 06:13:43 |
You-Sheng Yang |
linux (Ubuntu Jammy): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2022-03-10 06:14:14 |
You-Sheng Yang |
linux (Ubuntu Impish): status |
New |
Won't Fix |
|
| 2022-03-10 06:14:32 |
You-Sheng Yang |
linux-oem-5.14 (Ubuntu Focal): importance |
Undecided |
High |
|
| 2022-03-10 06:14:32 |
You-Sheng Yang |
linux-oem-5.14 (Ubuntu Focal): status |
New |
Triaged |
|
| 2022-03-10 06:14:32 |
You-Sheng Yang |
linux-oem-5.14 (Ubuntu Focal): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2022-03-10 06:15:48 |
You-Sheng Yang |
linux-oem-5.14 (Ubuntu Impish): status |
New |
Invalid |
|
| 2022-03-10 06:16:06 |
You-Sheng Yang |
linux-oem-5.14 (Ubuntu Jammy): status |
New |
Invalid |
|
| 2022-03-10 07:11:27 |
Bin Li |
bug |
|
|
added subscriber Bin Li |
| 2022-03-10 23:30:25 |
Brian Murray |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2022-03-11 06:30:44 |
Kai-Chuan Hsieh |
tags |
|
oem-priority |
|
| 2022-03-11 13:26:42 |
Bin Li |
bug |
|
|
added subscriber OEM Solutions Group: Engineers |
| 2022-03-11 13:26:44 |
Bin Li |
tags |
oem-priority |
oem-priority originate-from-1964599 sutton |
|
| 2022-03-11 14:01:48 |
Bin Li |
attachment added |
|
tbt3-9027-oem.log https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1962349/+attachment/5567977/+files/tbt3-9027-oem.log |
|
| 2022-03-16 06:55:31 |
You-Sheng Yang |
bug task added |
|
linux-oem-5.17 (Ubuntu) |
|
| 2022-03-16 06:55:44 |
You-Sheng Yang |
linux-oem-5.17 (Ubuntu Impish): status |
New |
Invalid |
|
| 2022-03-16 06:55:56 |
You-Sheng Yang |
linux-oem-5.17 (Ubuntu Focal): status |
New |
Invalid |
|
| 2022-03-16 06:56:12 |
You-Sheng Yang |
linux-oem-5.17 (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-03-16 06:56:12 |
You-Sheng Yang |
linux-oem-5.17 (Ubuntu Jammy): status |
New |
In Progress |
|
| 2022-03-16 06:56:12 |
You-Sheng Yang |
linux-oem-5.17 (Ubuntu Jammy): assignee |
|
You-Sheng Yang (vicamo) |
|
| 2022-03-16 06:56:26 |
You-Sheng Yang |
linux-oem-5.14 (Ubuntu Focal): status |
Triaged |
In Progress |
|
| 2022-03-16 06:56:38 |
You-Sheng Yang |
linux (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2022-03-16 16:35:35 |
Łukasz Zemczak |
bolt (Ubuntu Focal): status |
In Progress |
Incomplete |
|
| 2022-03-16 17:15:46 |
Mario Limonciello |
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". |
[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]
AMD Yellow Carp Host (issue this bug is about)
----------------------------------------------
* 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`
Alpine Ridge / Titan Ridge host (discrete controller)
------------------------------------------------------
Start out on a host with discrete controller (Alpine Ridge or Titan Ridge)
1. sudo boltctl forget -a
2. Plug in dock
3. Make sure 'boltctl list' enumerates dock.
4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host)
- If 0; try to manually enroll using 'boltctl enroll $UUID'
- If 1; ensure that device automatically enrolled with bolt.
GUI Check
---------
Ensure that devices show up in the Settings GUI and are now able to authorize.
Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization".
[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". |
|
| 2022-03-16 17:15:55 |
Mario Limonciello |
bolt (Ubuntu Focal): status |
Incomplete |
In Progress |
|
| 2022-03-24 14:59:32 |
Stéphane Verdy |
bug |
|
|
added subscriber Stéphane Verdy |
| 2022-03-25 14:29:04 |
Timo Aaltonen |
bolt (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-03-25 14:29:09 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2022-03-25 14:29:11 |
Timo Aaltonen |
tags |
oem-priority originate-from-1964599 sutton |
oem-priority originate-from-1964599 sutton verification-needed verification-needed-focal |
|
| 2022-03-25 16:18:13 |
Anson Tsao |
tags |
oem-priority originate-from-1964599 sutton verification-needed verification-needed-focal |
oem-priority originate-from-1964599 sutton verification-done verification-needed-focal |
|
| 2022-03-28 07:35:50 |
Anson Tsao |
tags |
oem-priority originate-from-1964599 sutton verification-done verification-needed-focal |
oem-priority originate-from-1964599 sutton verification-done verification-done-focal |
|
| 2022-04-04 08:00:00 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-04-04 08:15:41 |
Launchpad Janitor |
bolt (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-04-04 15:16:28 |
Timo Aaltonen |
linux-oem-5.14 (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-04-05 15:21:55 |
Timo Aaltonen |
tags |
oem-priority originate-from-1964599 sutton verification-done verification-done-focal |
oem-priority originate-from-1964599 sutton verification-done verification-needed-focal |
|
| 2022-04-07 17:18:30 |
You-Sheng Yang |
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]
AMD Yellow Carp Host (issue this bug is about)
----------------------------------------------
* 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`
Alpine Ridge / Titan Ridge host (discrete controller)
------------------------------------------------------
Start out on a host with discrete controller (Alpine Ridge or Titan Ridge)
1. sudo boltctl forget -a
2. Plug in dock
3. Make sure 'boltctl list' enumerates dock.
4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host)
- If 0; try to manually enroll using 'boltctl enroll $UUID'
- If 1; ensure that device automatically enrolled with bolt.
GUI Check
---------
Ensure that devices show up in the Settings GUI and are now able to authorize.
Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization".
[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". |
[SRU Justification]
[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]
AMD Yellow Carp Host (issue this bug is about)
----------------------------------------------
* 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`
Alpine Ridge / Titan Ridge host (discrete controller)
------------------------------------------------------
Start out on a host with discrete controller (Alpine Ridge or Titan Ridge)
1. sudo boltctl forget -a
2. Plug in dock
3. Make sure 'boltctl list' enumerates dock.
4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host)
- If 0; try to manually enroll using 'boltctl enroll $UUID'
- If 1; ensure that device automatically enrolled with bolt.
GUI Check
---------
Ensure that devices show up in the Settings GUI and are now able to authorize.
Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization".
[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". |
|
| 2022-04-14 07:32:55 |
Anson Tsao |
tags |
oem-priority originate-from-1964599 sutton verification-done verification-needed-focal |
oem-priority originate-from-1964599 sutton verification-done verification-done-focal |
|
| 2022-04-14 09:12:33 |
Bin Li |
attachment added |
|
tbt3.hp800.log https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1962349/+attachment/5580634/+files/tbt3.hp800.log |
|
| 2022-04-19 11:43:38 |
Launchpad Janitor |
linux-oem-5.14 (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-04-22 08:24:22 |
Timo Aaltonen |
linux-oem-5.17 (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-04-28 11:14:23 |
Ubuntu Kernel Bot |
tags |
oem-priority originate-from-1964599 sutton verification-done verification-done-focal |
oem-priority originate-from-1964599 sutton verification-done verification-done-focal verification-needed-jammy |
|
| 2022-05-16 10:40:33 |
Launchpad Janitor |
linux-oem-5.17 (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-05-31 23:50:51 |
Mario Limonciello |
linux-oem-5.17 (Ubuntu): status |
Fix Committed |
Invalid |
|
| 2022-06-03 07:50:01 |
Launchpad Janitor |
linux (Ubuntu Jammy): status |
In Progress |
Fix Released |
|
| 2022-06-03 07:50:01 |
Launchpad Janitor |
cve linked |
|
2022-21499 |
|
| 2022-06-12 06:39:50 |
Yuan-Chen Cheng |
oem-priority: status |
New |
Fix Released |
|
| 2023-01-17 10:15:00 |
Anthony Wong |
nominated for series |
|
Ubuntu Kinetic |
|
| 2023-01-17 10:15:00 |
Anthony Wong |
bug task added |
|
linux (Ubuntu Kinetic) |
|
| 2023-01-17 10:15:00 |
Anthony Wong |
bug task added |
|
bolt (Ubuntu Kinetic) |
|
| 2023-01-17 10:15:00 |
Anthony Wong |
bug task added |
|
linux-oem-5.14 (Ubuntu Kinetic) |
|
| 2023-01-17 10:15:00 |
Anthony Wong |
bug task added |
|
linux-oem-5.17 (Ubuntu Kinetic) |
|
| 2023-01-17 10:15:51 |
Anthony Wong |
linux (Ubuntu Kinetic): status |
New |
Fix Released |
|
| 2023-01-17 10:16:03 |
Anthony Wong |
linux-oem-5.17 (Ubuntu Kinetic): status |
New |
Invalid |
|
| 2023-01-17 10:16:16 |
Anthony Wong |
linux-oem-5.14 (Ubuntu Kinetic): status |
New |
Invalid |
|
| 2023-08-10 18:01:16 |
Utkarsh Gupta |
bolt (Ubuntu Kinetic): status |
New |
Won't Fix |
|
| 2023-08-10 20:14:48 |
Ubuntu Foundations Team Bug Bot |
tags |
oem-priority originate-from-1964599 sutton verification-done verification-done-focal verification-needed-jammy |
oem-priority originate-from-1964599 patch sutton verification-done verification-done-focal verification-needed-jammy |
|
| 2023-08-10 20:14:48 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Terry Rudd |
| 2024-01-08 08:53:37 |
You-Sheng Yang |
linux (Ubuntu): status |
In Progress |
Fix Released |
|
