[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
All kernel patches available in v5.19-rc1 or newer. ** Changed in: linux (Ubuntu) Status: In Progress => 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 OEM Priority Project: Fix Released Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid 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 linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in bolt source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [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". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: bolt (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Kinetic) Status: New => Invalid -- 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 OEM Priority Project: Fix Released Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid 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 linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in bolt source package in Kinetic: New Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [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". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Changed in: oem-priority 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 OEM Priority Project: Fix Released Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid 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 linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [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". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Changed in: linux-oem-5.17 (Ubuntu) Status: Fix Committed => Invalid -- 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 OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid 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 linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [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". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1004.4 --- linux-oem-5.17 (5.17.0-1004.4) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1004.4 -proposed tracker (LP: #1970584) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md * alsa: enable the cirrus-logic side-codec to make the speaker output sound (LP: #1965496) - spi: Make spi_alloc_device and spi_add_device public again - spi: Create helper API to lookup ACPI info for spi device - spi: Support selection of the index of the ACPI Spi Resource before alloc - spi: Add API to count spi acpi resources - platform/x86: i2c-multi-instantiate: Rename it for a generic serial driver name - platform/x86: serial-multi-instantiate: Reorganize I2C functions - platform/x86: serial-multi-instantiate: Add SPI support - ACPI / scan: Create platform device for CS35L41 - [Config]: enable SERIAL_MULTI_INSTANTIATE * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform (LP: #1969407) - drm/amd/display: Only set PSR version when valid * Micmute LED support for Zbook Fury 16 G9 (LP: #1968892) - ALSA: hda/realtek: Add support for HP Laptops - ALSA: hda/realtek: Add mute and micmut LED support for Zbook Fury 17 G9 * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms (LP: #1942160) - SAUCE: PCI/ASPM: Enable ASPM for links under VMD domain - SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD - SAUCE: vmd: fixup bridge ASPM by driver name instead * Support AMD P-State cpufreq control mechanism (LP: #1956509) - [Config] enable X86_AMD_PSTATE as built-in on amd64 * Use kernel-testing repo from launchpad for ADT tests (LP: #1968016) - [Debian] Use kernel-testing repo from launchpad * Fix beacon loss for rtl8821ce on certain platforms (LP: #1969771) - SAUCE: rtw88: pci: 8821c: Disable 21ce completion timeout * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Miscellaneous Ubuntu changes - [Config] update configs and annotations after stable updates [ Ubuntu: 5.17.0-8.8~22.04.2 ] * jammy/linux-hwe-5.17: 5.17.0-8.8~22.04.2 -proposed tracker (LP: #1969219) * Packaging resync (LP: #1786013) - [Packaging] update Ubuntu.md - [Packaging] update update.conf [ Ubuntu: 5.17.0-8.8~22.04.1 ] * Empty entry [ Ubuntu: 5.17.0-8.8 ] * jammy/linux-unstable: 5.17.0-8.8 -proposed tracker (LP: #1969016) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) [ Ubuntu: 5.17.0-7.7 ] * jammy/linux-unstable: 5.17.0-7.7 -proposed tracker (LP: #1968988) * zfcpdump-kernel update to v5.15 (LP: #1965766) - SAUCE: Audit: Fix incorrect static inline function declration. * intel_iommu breaks Intel IPU6 camera: isys port open ready failed -16 (LP: #1958004) - SAUCE: iommu: intel-ipu: use IOMMU passthrough mode for Intel IPUs * Jammy update: v5.17.3 upstream stable release (LP: #1968986) - lib/logic_iomem: correct fallback config references - um: fix and optimize xor select template for CONFIG64 and timetravel mode - rtc: wm8350: Handle error for wm8350_register_irq - net: dsa: felix: fix possible NULL pointer dereference - mm: kfence: fix objcgs vector allocation - KVM: x86/pmu: Use different raw event masks for AMD and Intel - KVM: SVM: Fix kvm_cache_regs.h inclusions for is_guest_mode() - KVM: x86/svm: Clear reserved bits written to PerfEvtSeln MSRs - KVM: x86/pmu: Fix and isolate TSX-specific performance event logic - KVM: x86/emulator: Emulate RDPID only if it is enabled in guest - drm: Add orientation quirk for GPD Win Max - Bluetooth: hci_sync: Fix compilation warning - ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 - Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt - drm/amd/display: Add signal type check when verify stream backends same - drm/amdkfd: enable heavy-weight TLB flush on Arcturus - drm/edid: remove non_desktop quirk for HPN-3515 and LEN-B800. - drm/edid: improve non-desktop quirk logging - Bluetooth: hci_event: Ignore multiple conn complete events - drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj - drm/amd/display: Fix memory leak - drm/amd/display: Use PSR version selected during set_psr_caps - usb: gadget: tegra-xudc:
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36 --- linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP: #1967397) * Bolt doesn't work with native USB4 hosts (LP: #1962349) - thunderbolt: Retry DROM reads for more failure scenarios - thunderbolt: Do not resume routers if UID is not set - thunderbolt: Do not make DROM read success compulsory - PCI/ACPI: Allow D3 only if Root Port can signal and wake from D3 * Fix non-working MT7921 BT after reboot (LP: #1966497) - Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921) * alsa/sdw: Fix the audio issue on a Dell machine without internal mic (LP: #1966841) - ASoC: Intel: soc-acpi: add entries in ADL match table * Enable headset mic on Lenovo P360 (LP: #1967069) - ALSA: hda/realtek: Enable headset mic on Lenovo P360 * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067) - Bluetooth: btusb: Improve stability for QCA devices * Focal update: upstream stable patchset 2022-03-21 (LP: #1965737) - mm/filemap: Fix handling of THPs in generic_file_buffered_read() - cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug - cgroup-v1: Correct privileges check in release_agent writes - x86/ptrace: Fix xfpregs_set()'s incorrect xmm clearing - btrfs: tree-checker: check item_size for inode_item - btrfs: tree-checker: check item_size for dev_item - clk: jz4725b: fix mmc0 clock gating - io_uring: don't convert to jiffies for waiting on timeouts - io_uring: disallow modification of rsrc_data during quiesce - selinux: fix misuse of mutex_is_locked() - vhost/vsock: don't check owner in vhost_vsock_stop() while releasing - parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel - parisc/unaligned: Fix ldw() and stw() unalignment handlers - KVM: x86/mmu: make apf token non-zero to fix bug - drm/amd/display: Protect update_bw_bounding_box FPU code. - drm/amd/pm: fix some OEM SKU specific stability issues - drm/amdgpu: disable MMHUB PG for Picasso - drm/amdgpu: do not enable asic reset for raven2 - drm/i915: Widen the QGV point mask - drm/i915: Correctly populate use_sagv_wm for all pipes - drm/i915: Fix bw atomic check when switching between SAGV vs. no SAGV - sr9700: sanity check for packet length - USB: zaurus: support another broken Zaurus - CDC-NCM: avoid overflow in sanity checking - netfilter: xt_socket: fix a typo in socket_mt_destroy() - netfilter: xt_socket: missing ifdef CONFIG_IP6_NF_IPTABLES dependency - tee: export teedev_open() and teedev_close_context() - optee: use driver internal tee_context for some rpc - ping: remove pr_err from ping_lookup - Revert "i40e: Fix reset bw limit when DCB enabled with 1 TC" - gpu: host1x: Always return syncpoint value when waiting - perf data: Fix double free in perf_session__delete() - mptcp: fix race in incoming ADD_ADDR option processing - mptcp: add mibs counter for ignored incoming options - selftests: mptcp: fix diag instability - selftests: mptcp: be more conservative with cookie MPJ limits - bnx2x: fix driver load from initrd - bnxt_en: Fix active FEC reporting to ethtool - bnxt_en: Fix offline ethtool selftest with RDMA enabled - bnxt_en: Fix incorrect multicast rx mask setting when not requested - hwmon: Handle failure to register sensor with thermal zone correctly - net/mlx5: Fix tc max supported prio for nic mode - ice: check the return of ice_ptp_gettimex64 - ice: initialize local variable 'tlv' - net/mlx5: Update the list of the PCI supported devices - bpf: Do not try bpf_msg_push_data with len 0 - selftests: bpf: Check bpf_msg_push_data return value - bpf: Add schedule points in batch ops - io_uring: add a schedule point in io_add_buffers() - net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends - tipc: Fix end of loop tests for list_for_each_entry() - gso: do not skip outer ip header in case of ipip and net_failover - net: mv643xx_eth: process retval from of_get_mac_address - openvswitch: Fix setting ipv6 fields causing hw csum failure - drm/edid: Always set RGB444 - net/mlx5e: Fix wrong return value on ioctl EEPROM query failure - drm/vc4: crtc: Fix runtime_pm reference counting - net/sched: act_ct: Fix flow table lookup after ct clear or switching zones - net: ll_temac: check the return value of devm_kmalloc() - net: Force inlining of checksum functions in net/checksum.h - netfilter: nf_tables: unregister flowtable hooks on netns exit - nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac() - netfilter: nf_tables: fix memory leak during stateful obj update - net/smc: Use a mutex for locking "struct smc_pnettable" - surface: surface3_power:
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
This bug was fixed in the package bolt - 0.9.1-2~ubuntu20.04.1 --- bolt (0.9.1-2~ubuntu20.04.1) focal; urgency=medium * SRU into Ubuntu 20.04. - Add support for integrated USB4 controllers (LP: #1962349) -- Mario Limonciello Fri, 25 Feb 2022 16:20:33 -0600 ** Changed in: bolt (Ubuntu Focal) Status: Fix Committed => 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 OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid 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 linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress 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] 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". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Triaged => In Progress -- 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 OEM Priority Project: New Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress 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: In Progress Status in linux-oem-5.17 source package in Focal: Invalid 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 linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress 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/oem-priority/+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
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
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 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 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 -- 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