[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
From https://www.samsung.com/semiconductor/minisite/ssd/product/portable/t5/ I learn this is a USB 3.1 Gen2 device, not a Thunderbolt device, so authorization isn't relevant (and thunderbolt-tools isn't the relevant package). Still, the fact that you had to force power the controller even when a device is connected (and especially as it works when it's connected on boot) suggests there is some sort of issue between the BIOS / port controller / cable / maybe other parts in the system that take part in the HW detection. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in thunderbolt-tools package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
I guess it worth updating your BIOS to the latest version. According to the details above you have Ver. 02.06.03, while in HP site I can find Ver 02.07.00 The release notes there mention several fixes for the handling of USB-C ports. (I hope there is an easy way to do so on Linux. Hopefully it's available from fwupd :) ) https://support.hp.com/us-en/drivers/selfservice/hp-elitedesk-800-65w-g4 -desktop-mini-pc/21353734 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: New Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761757] Re: use correct path for tbtacl in udev rules
I'm not sure I understand what's going on here, so I'll take the risk
that I'm describing the obvious:
@UDEV_BIN_DIR@ is a cmake parameter that is replaced by cmake with the path it
reads from pkgconfig. See here:
https://github.com/intel/thunderbolt-software-user-space/blob/master/CMakeLists.txt#L10
If this is the wrong location:
1. UDEV_BIN_DIR can be set manually while running cmake (or using
ccmake/cmake-gui).
2. If there is a better way to detect the distro-specific correct location for
udev dirs, I'd like to fix it upstream.
Anyway, copy of the original .rules.in files instead of using the
resulted .rules file seems strange to me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thunderbolt-tools in Ubuntu.
Matching subscriptions: Kernel Packages
https://bugs.launchpad.net/bugs/1761757
Title:
use correct path for tbtacl in udev rules
Status in thunderbolt-tools package in Ubuntu:
Fix Released
Bug description:
./thunderbolt-tools_0.9.3-1_amd64/lib/udev/rules.d/tbtacl.rules:
# Thunderbolt udev rules for ACL (device auto approval)
SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add"
ATTR{authorized}=="0" RUN+="@UDEV_BIN_DIR@/tbtacl add $devpath"
SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change"
ATTR{authorized}!="0" RUN+="@UDEV_BIN_DIR@/tbtacl change $devpath"
should changed to fix up @UDEV_BIN_DIR@ to be:
SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="add"
ATTR{authorized}=="0" RUN+="/lib/udev/tbtacl add$devpath"
SUBSYSTEM=="thunderbolt" ENV{DEVTYPE}=="thunderbolt_device" ACTION=="change"
ATTR{authorized}!="0" RUN+="/lib/udev/tbtacl change $devpath"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1761757/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
Thanks for the review! I'd like to get a bit more details about some of the comments to understand what steps I can take to improve it. Please let me know if you prefer to take this discussion to another medium. > - udev rules -- appear to be configured for works-by-default behaviour, > some examples on how to configure for authorization-required would be > nice I'm not sure I understand what examples and what configuration this comment refers to. > - No tests, a bit unfortunate This is about the package or the upstream project? Upstream we have some tests (using umockdev). See here for CI: https://travis-ci.org/intel/thunderbolt-software-user-space > - File IO done via RAII-C++ classes, not exactly obvious when it happens Any specific question that I can answer (or maybe even document in the code)? > - No PolicyKit My assumption (and is mentioned here and there in the code) is that eventually the tool will be better if it does start using PolicyKit for the privileged actions. It'd be nice to here what do you think about it or if there are guidelines from the distro on where, when and how to use it. > It uses std::random_device for security uses -- I believe this is safe but > direct use of getrandom(2) would not have questions about underlying C++ > library implementation choices. Noted. flags=0 is good enough, yes? (I will may have to make sure first that all the relevant distros include this syscall already.) Thanks again! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Securi
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
My 2 cents: I think bolt and thunderbolt-tools must agree on the ACL (device whitelist for auto-approve on next connection) location and format and then I assume they can co-exist happily without stepping on each other's toes. Even if both try to authorize the same device on connection, it shouldn't matter much as the final result is that the device is authorized and ready to use. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
Seth, It was disabled as the project is now handled at freedesktop's GitLab. I opened an issue there: https://github.com/intel/thunderbolt-software-user-space/issues/60 ** Bug watch added: github.com/intel/thunderbolt-software-user-space/issues #60 https://github.com/intel/thunderbolt-software-user-space/issues/60 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notification
[Kernel-packages] [Bug 1748157] Re: [MIR] thunderbolt-tools
(Sorry, I meant: https://gitlab.freedesktop.org/bolt/bolt/issues/78) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1748157 Title: [MIR] thunderbolt-tools Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: == Overview == Intel Thunderbolt userspace components provides components for using Intel Thunderbolt controllers with security level features. Thunderbolt™ technology is a transformational high-speed, dual protocol I/O that provides unmatched performance with up to 40Gbps bi- directional transfer speeds. It provides flexibility and simplicity by supporting both data (PCIe, USB3.1) and video (DisplayPort) on a single cable connection that can daisy-chain up to six devices. [ See https://github.com/intel/thunderbolt-software-user-space ] == Answers to UbuntuMainInclusionRequirements == = Requirements = 1. Availability Package is in universe: https://launchpad.net/ubuntu/+source/thunderbolt-tools 2. Rationale Package a device enabler for users with Thunderbolt technology 3. Security: No security issues exposed so far. However, the tools have only been in Ubuntu since 2017-12-09, so this currently is less than the 90 days threshold. 4. Quality assurance: * Manual is provided * No debconf questions higher than medium * No major outstanding bugs. I'm also helping Intel fix issues that I'm finding with static analysis tools such as scan-build, cppcheck and CoverityScan Bugs outstanding: #883857 please backport for stretch-backports #882525 thunderbolt-tools: FTBFS on kFreeBSD: _ZN5boost6system15system_categoryEv undefined - I can fix this, but it makes no sense to run on kFreeBSD * Exotic Hardware: Only Thunderbolt supported H/W is required, this is an industry standard and the support for the tools are in the 4.13+ kernels * No Test Suite shipped with the package * Does not rely on obsolete or demoted packages 5. UI standards: * This is a CLI tool. Tool has normal CLI style short help and man pages * No desktop file required as it is a CLI tool. 6. Binary Dependencies: libboost-dev(main) libboost-filesystem-dev (main) libboost-program-options-dev(main) udev(main) 7. Standards compliance: lintian clean and meets the FHS + Debian Policy standards to the best of my knowledge 8. Maintenance * Package owning team: The Ubuntu Kernel Team * Debian package maintained by Colin Ian King (myself from the Kernel Team) 9. Background Information The user-space components implement device approval support: a. Easier interaction with the kernel module for approving connected devices. b. ACL for auto-approving devices white-listed by the user. Tools provided by this package: tbtacl - triggered by udev (see the udev rules in tbtacl.rules). It auto-approves devices that are found in ACL. tbtadm - user-facing CLI tool. It provides operations for device approval, handling the ACL and more. The user-space components operate in coordination with the upstream Thunderbolt kernel driver (found in v4.13) to provide the Thunderbolt functionalities. These components are NOT compatible with the old out-of-tree Thunderbolt kernel module. = Security checks = http://cve.mitre.org/cve/cve.html: Search in the National Vulnerability Database using the package as a keyword * No CVEs found http://secunia.com/advisories/search/: search for the package as a keyword * No security advisories found Ubuntu CVE Tracker http://people.ubuntu.com/~ubuntu-security/cve/main.html * No http://people.ubuntu.com/~ubuntu-security/cve/universe.html * No http://people.ubuntu.com/~ubuntu-security/cve/partner.html * No Check for security relevant binaries. If any are present, this requires a more in-depth security review. Executables which have the suid or sgid bit set. * Not applicable Executables in /sbin, /usr/sbin. * None in these paths Packages which install daemons (/etc/init.d/*) * No Packages which open privileged ports (ports < 1024). * No Add-ons and plugins to security-sensitive software (filters, scanners, UI skins, etc) * This does exec tbtacl from udev with new udev rules, so this needs security checking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbolt-tools/+bug/1748157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Kernel-packages] [Bug 1697395] Re: Thunderbolt devices don't work if connected during boot
FYI, the patches that Mario mentioned above landed Linus' tree for v4.14-rc1 and hopefully will be backported to 4.13. See details here: https://github.com/01org/thunderbolt-software-user-space/issues/24#issuecomment-328011428 ** Bug watch added: github.com/01org/thunderbolt-software-user-space/issues #24 https://github.com/01org/thunderbolt-software-user-space/issues/24 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1697395 Title: Thunderbolt devices don't work if connected during boot Status in linux package in Ubuntu: Triaged Bug description: I am using a Dell XP 15 9550, if my Dockingstation (Dell TB16) is connected during boot time, all the USB devices (like Keyboard, Ethernet, ...) are only working while in grub boot menu. After booting they stop working. The two 4k screens which are connected to the dock, are working properly in boot menu and after booting. If booting into Windows everything is working, only linux is affected. Disconnecting and reconnecting the dock solves this problem. I have created the bug-report directly after boot, where the USB devices are not working and attached "lspci-vnvn_after_reconnect.log" after reconnecting the dock. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic 4.10.0-22.24 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andre_duewel 3163 F pulseaudio CurrentDesktop: X-Cinnamon Date: Mon Jun 12 11:17:26 2017 InstallationDate: Installed on 2017-04-12 (60 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=0ba04b8b-151f-4522-81a8-b6b01352ea35 ro quiet splash nvme_core.default_ps_max_latency_us=6000 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
