Summary: | [hsw DP] Haswell Iris 5100 DisplayPort stops working when USB3 device is connected | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Andrzej Pronobis <a.pronobis> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED INVALID | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs, przanoni | ||||
Version: | unspecified | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Andrzej Pronobis
2014-10-31 02:10:24 UTC
I would like to add that everything works as expected in Windows on the same hardware. Does it make a difference what kind of USB device is connected to the port? In particular, I'm interested in the power consumption of the device. Does a regular USB memory stick (presumably that draws very little current) also reproduce the issue? Oh, and does the USB device work fine even if the DP stops working? Also, can you reproduce the problem if you connect something to an USB port that is "distant" from the DP port? > Does it make a difference what kind of USB device is connected to the port? There is a difference, but it is related to the use of USB 3.0. If I use a USB stick using 2.0, things work fine. Then, even a usb stick that is capable of using USB 3.0 will trigger the issue. > Oh, and does the USB device work fine even if the DP stops working? So far, yes. Although I did not test very extensively. It is detected and I can successfully mount the USB stick or use the USB ethernet card. > Also, can you reproduce the problem if you connect something to an USB port that is "distant" from the DP port? I cannot. The other USB 3.0 port works fine and does not trigger the issue. (In reply to Andrzej Pronobis from comment #0) > however, if the external monitor is > configured after the USB device is plugged in, then the following backtrace > appears in dmesg: > > [ 57.685383] ------------[ cut here ]------------ > [ 57.685396] WARNING: CPU: 0 PID: 1879 at > /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_dp.c:3122 > intel_dp_link_down+0x1a9/0x230 [i915]() > [ 57.685397] Modules linked in: cdc_ether usbnet r8152 mii pci_stub ... > [ 57.688050] [drm:intel_dp_complete_link_train] *ERROR* failed to train > DP, aborting Please attach dmesg with drm.debug=14 module parameter set, from boot to this problem, i.e. plug a problematic USB3 device in first, then the DP cable. Created attachment 109817 [details]
Dmesg output with drm.debug=14
The dmesg output was generated for the following events:
- clean boot with usb/dp disconnected with drm.debug=14 set
- usb 3.0 device is connected first
- DP monitor is connected second
- after some time, xrandr is used to enable the external display
I'm afraid I don't have any further clues here. I can only ask you to give newer kernels a try. Oh, and does it make a difference if the laptop is operating on batter power vs. mains? Hoping this was resolved and you forgot about it, otherwise please re-open. I wonder if there's some electrical interference with the port you're using. You said the other one works fine, so that could definitely be a problem. Or as Jani is implying, it could be that the power draw from those two ports on that side of the machine is simply too much for the board design to handle. The issue was not resolved, but it disappears when USB 3.0 is disabled as described in this post: http://askubuntu.com/questions/396021/what-is-causing-my-intel-7260-bluetooth-device-to-disconnect-when-i-unblock-it-w using the bios XHCI PRE-BOOT MODE option. |
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.