Created attachment 113728 [details] dmesg without drm.debug=14 HW: MacBookPro11,1, Retina display 2 x 27" Thunderbolt displays. Under MacOS X, all 3 displays work. Under Ubuntu 14.10, kernel 3.19, only eDP1 + one other show as active.
Created attachment 113729 [details] dmesg with drm.debug=14
Created attachment 113730 [details] xrander --verbose output.
To add some colour to this report: When the MacOS boots, both the external screens remain blank, the logo and the progress bar only appear on the laptop's internal display. The external screens come alive later. The typical use case is to run the laptop with its lid closed, and just use the 2 x 27" 2560x1440 monitors - there is a lack of desk space which forces this particular setup more than anything else. It does help with the resolution, since the Retina display has a higher resolution than the 27" monitors. This is similar to what I see happening when Linux loads - initially, I see the kernel messages on the laptop's internal screen, then (I suspect) the i915 driver loads, takes over the fbcon, and I get a mirror of what is on the Mac's internal display on one (DP-1) of the two 27" monitors. When Xorg starts, I get a spanned screen between the eDP-1 and DP-1. I have tried to be clever-ish - 'xrandr --output eDP-1 --off', then 'xrandr --output DP-2 --auto'. Am quite willing to play with patches and such.
How do you have the monitors connected?
@Jani: Via the Thunderbolt ports, each monitor in its own Thunderbolt port. I have tried to daisy-chain, too, with the same effect, just in case the Thunderbolt ports on the MacBook were, somehow, competing for resources, though that was just a wild-ass guess on my part, based, rather flimsily, on lines a-la "pci 0000:00:1c.4: can't claim BAR 15 [mem 0xbcc00000-0xc8dfffff 64bit pref]: address conflict with PCI Bus 0000:05 [mem 0xb0b00000-0xbcffffff]" in dmesg's output
For some more background: The monitors don't work at all with hotplugging. Devices plugged into the back work with hotplugging, but the monitors aren't detected. DP2 works if it's the only port plugged in at boot, otherwise DP1 works and DP2 shows up as disconnected. When two thunderbolt displays are connected, the USB devices on the back on either display work, even though DP2 doesn't show up as connected.
Please try kernel v4.4.
Howdy. Not the original reporter, but I have a very similar setup (MacBook 11,1 Retina Intel Only, albeit late 2015), and I'm experiencing the same issue with kernels 4.3 and 4.4-rc8. (I'm compiling 4.4 now, though; maybe it was fixed between rc8 and 4.4.) When monitors are connected while booting, only the one identified as DP1 activates. This is true in both chained and parallel (i.e., each monitor on its own thunderbolt port) configurations. Neither monitor is detected/activated upon hotplug, regardless of the connectedness of the monitors on boot. - Patrick
I've confirmed that on 4.4 proper, thunderbolt displays are not correctly enabled when hotplugged.
Same here. Tried it on 4.6.0 vanilla kernel on a fedora machine, i am having the same issue. Raised a bug here https://bugzilla.kernel.org/show_bug.cgi?id=118591, i was asked to report it here. Bump
Tested it on 4.6.1 and 4.7.0-rc1, still seeing this issue. This bug is annoying every time i disconnect my laptop go into a meeting and come back. I need to reboot it for the apple monitor to work. This bug has been sitting here for more than year. I would be more than happy to show you my hardware if you live in the bay area. I am willing to test any patches too.
Development is targeting to work on thunderbolt related issues on 4.13.
(In reply to Jari Tahvanainen from comment #12) > Development is targeting to work on thunderbolt related issues on 4.13. Good afternoon Regular Guy, Patrick, Arun, 4.13 is available now, any update with mainline or/and latest drm-tip on this case? Thank you. https://cgit.freedesktop.org/drm-tip https://www.kernel.org/
(In reply to Elizabeth from comment #13) > (In reply to Jari Tahvanainen from comment #12) > > Development is targeting to work on thunderbolt related issues on 4.13. > Good afternoon Regular Guy, Patrick, Arun, > 4.13 is available now, any update with mainline or/and latest drm-tip on > this case? > Thank you. > > https://cgit.freedesktop.org/drm-tip > https://www.kernel.org/ Sadly, I no longer have in my possession the MacBook (company took it back), making it difficult to check. Sorry :(
(In reply to Regular Guy from comment #14) > Sadly, I no longer have in my possession the MacBook (company took it back), > making it difficult to check. Sorry :( Thanks for the update Regular Guy, Then I will wait for Patrick or Arun to share status.
Created attachment 133515 [details] Journalctl when unplugging and hotplugging the apple monitor
Still doesn't work, attached the logs. Tested it on 4.13.0-0.rc4.git4.1.vanilla.knurd.1.fc26.x86_64
I mean, i do not see the monitor detected after hotplug. It stays turned off
Apologies for the flurry of comments, i just realized i have not tested the latest drm-tip. Will test it and post the comments. Thanks.
Created attachment 133567 [details] Logs when running drm-tip
The same bug happens in Macbookpro12,1 (Retina 13" early 2015) too.
Please at least run current drm-tip, add drm.debug=14 module parameter, and attach logs all the way from boot to the problem. And I'm not sure what the exact problem is anymore... you all have eDP + one DP working fine, but another DP won't show up? Or what?
Created attachment 134561 [details] dmesg without drm.debug=14 and before/after hotplug thunderbolt dumps I have one eDP-1 and one DP-1. When booted with the monitor plugged in, it works and both /sys/class/drm/card0-eDP-1/enabled and /sys/class/drm/card0-DP-1/enabled show "enabled". After unplugging it and plugging it back in, only /sys/class/drm/card0-eDP-1/enabled shows up, and it's impossible to bring back the external display without rebooting. While examining the thunderbolt dump in dmesg from a booting up event and after replugging it, I noticed that two DP/HDMI ports are missing in the latter dump: [ 28.716581] thunderbolt 0000:07:00.0: Port 11: 8086:156d (Revision: 0, TB Version: 1, Type: DP/HDMI (0xe0101)) [ 28.716582] thunderbolt 0000:07:00.0: Max hop id (in/out): 9/9 [ 28.716583] thunderbolt 0000:07:00.0: Max counters: 2 [ 28.716584] thunderbolt 0000:07:00.0: NFC Credits: 0xf0000b [ 28.716602] thunderbolt 0000:07:00.0: Port 12: 8086:156d (Revision: 0, TB Version: 1, Type: DP/HDMI (0xe0101)) [ 28.716603] thunderbolt 0000:07:00.0: Max hop id (in/out): 9/9 [ 28.716603] thunderbolt 0000:07:00.0: Max counters: 2 [ 28.716604] thunderbolt 0000:07:00.0: NFC Credits: 0xf00000
As for drm-tip, I'll need to recompile my kernel for that so it'll take a while.
Created attachment 134568 [details] dmesg from drm-tip with drm.debug=14 (macbookpro12,1) This dmesg dump was taken from a session where the machine was booted up with the display plugged in, then unplugged at [366.531437], and plugged back in again at [405.015372]. The display doesn't return, but the USB devices and ethernet interface does.
Marking Broadwell as affected as well, and setting it back to REOPENED since I've provided the requested information. Please let me know if you need me to poke around further.
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Closing old bug, please re-open if still occurs.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.