Bug 1531929
| Summary: | can't connect to Apple Thunderbolt Display | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter F. Patel-Schneider <pfpschneider> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 27 | CC: | airlied, bskeggs, ckellner, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, kolya, linville, mchehab, mjg59, steved | ||||||||||
| Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2018-08-29 15:18:30 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 1377918 [details]
system log and boltctl monitor output
I'm still experiencing problems with kernel 4.15.3-300.fc27.x86_64+debug. I've attached the systems messages at startup with the hub connected and lspci -vv output for the thunderbolt devices in the laptop itself. Created attachment 1397969 [details]
boot messages with hub attached
Created attachment 1397971 [details]
lspci -vv for thunderbolt devices
Just as a suggestion, have you tried "boltctl authorize" on your device? (The command takes as an argument the device ID, which is listed as the UUID in "boltctl list".) Yes, I've tried to do that. The device isn't visible at all in bolt. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. |
Created attachment 1377917 [details] new PCI devices after hotplug Description of problem: I have a Lenovo Yoga 920 with two thunderbolt-capable USB-C ports run by an Intel Corporation JHL6540. When I plug in an Apple Thunderbolt Display attached to a Thunderbolt-3-to-2 adapter I see some Thunderbolt activity, but the display and devices attached to it remain inactive. Version-Release number of selected component (if applicable): Linux idefix 4.14.11-300.fc27.x86_64 #1 How reproducible: Always Steps to Reproduce: 1. Plug thunderbolt adapter with display attached in to a Thunderbolt-capable port. 2. 3. Actual results: The thunderbolt chip becomes visible, and is in thunderbolt mode. The display and devices attached to it remain inactive and do not show up as devices. Expected results: The display becomes active and is available for use. The devices attached to the display (currently only USB disks) become active and are available for use. Additional info: Thunderbolt Devices after hotplug idefix thunderbolt> ls -l /sys/bus/thunderbolt/devices/ total 0 lrwxrwxrwx. 1 root root 0 Jan 2 12:05 0-0 -> ../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:00.0/0000:03:00.0/domain0/0-0/ lrwxrwxrwx. 1 root root 0 Jan 2 12:05 domain0 -> ../../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:00.0/0000:03:00.0/domain0/ lspci new devices on hotplug 01:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 02:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 02:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 02:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 02:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 03:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] (rev 02) 05:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] (rev 02) I'm attaching lspci -vv for these devices and the system log (separately)