Bug 118591 - Macbook Pro 11,1 thunderbolt Hotplug doesn't work
Summary: Macbook Pro 11,1 thunderbolt Hotplug doesn't work
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: HotPlug (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-20 07:18 UTC by Arun S A G
Modified: 2016-05-24 03:28 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.6.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Dmesg (46.90 KB, text/plain)
2016-05-20 07:18 UTC, Arun S A G
Details

Description Arun S A G 2016-05-20 07:18:41 UTC
Created attachment 216951 [details]
Dmesg

Linux 4.6.0-1.vanilla.knurd.1.fc23.x86_64 #1 SMP Mon May 16 16:25:29 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


/proc/cmdline 

BOOT_IMAGE=/vmlinuz-4.6.0-1.vanilla.knurd.1.fc23.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.luks.uuid=luks-6395ab7e-afbf-42d9-8966-e0c0e7af36fa rd.lvm.lv=fedora/swap rhgb quiet video.use_native_backlight=1 acpi_osi=Darwin LANG=en_US.UTF-8
Comment 1 Greg Kroah-Hartman 2016-05-20 18:13:27 UTC
On Fri, May 20, 2016 at 07:18:41AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=118591
> 
>             Bug ID: 118591
>            Summary: Macbook Pro 11,1  thunderbolt Hotplug doesn't work
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 4.6.0

Please send to the linux-pci@vger.kernel.org mailing list.
Comment 2 Lukas Wunner 2016-05-21 19:14:52 UTC
The bug report appears to be incomplete:

(1) Is this a regression in 4.6?

(2) This bugzilla entry only says "doesn't work", your e-mail to linux-pci@ contains slightly more information.

(3) There's only one dmesg output. Is this when the device is plugged in at boot or when it's hotplugged after boot? All the devices seem to have been recognized, so where's the problem?
Comment 3 Arun S A G 2016-05-21 20:03:52 UTC
(1) I wouldn't call this a regression in 4.6. It didn't work on 4.4.8 before that, it showed the same behaviour.

(2) (repasting, from eamil) When i boot the laptop connected to thunderbolt apple display, everything works fine. However, if i unplug the display and
re-plug linux doesn't detects the monitor. Seems like a device
hotplug problem

(3) The dmesg output is from hotplugging after boot. Even though everything seem to be recognized, i do not see anything on the apple display (monitor). I could however open 'cheese' and use the webcam attached to the apple display, But nothing on the display. xrandr doesn't show the second monitor attached and the display never turns on on hotplug after boot.
Comment 4 Lukas Wunner 2016-05-21 20:57:31 UTC
The Thunderbolt controller in your MacBook Pro has two DisplayPort sink ports which are connected to the Intel Iris 5100 graphics card. If a Thunderbolt display is plugged in, the graphics card should see an additional DisplayPort display.

If it doesn't then this is either an issue with the i915 driver for the graphics card, or it's an issue in the thunderbolt driver. The Thunderbolt driver only takes care of connecting downstream PCI devices, I'm not aware it does anything special for downstream DisplayPort devices. In this case, there's a DP device on Port 11 of the Thunderbolt switch in the display.

There's no public documentation on Thunderbolt, we have to reverse-engineer everything. It would be good if you could bug the i915 developers with this, they have their own mailing list and bug tracker:
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
https://bugs.freedesktop.org/

They won't be happy of course because they're swamped with work like everyone else, but they have in-depth knowledge of their graphics driver and access to internal Thunderbolt documentation and engineers, so they're in the best position to fix this.
Comment 5 Arun S A G 2016-05-24 03:28:58 UTC
Thanks for the pointer to intel-gfx. There is already a bug exists https://bugs.freedesktop.org/show_bug.cgi?id=89271

Note You need to log in before you can comment on or make changes to this bug.