Bug 72834 - [BDW]DP monitor unable to detected by hot-plug
Summary: [BDW]DP monitor unable to detected by hot-plug
Status: CLOSED DUPLICATE of bug 72833
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high major
Assignee: Paulo Zanoni
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-18 11:45 UTC by Guo Jinxian
Modified: 2017-10-06 14:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (94.75 KB, text/plain)
2013-12-18 11:45 UTC, Guo Jinxian
no flags Details

Description Guo Jinxian 2013-12-18 11:45:52 UTC
Created attachment 90921 [details]
dmesg

Environment:
--------------------------
Platform: Broadwell
Kernel: (drm-intel-nightly) 22dd82bce1840fe48d683a29cccc443281b10248


Bug detailed description:
-----------------------------
DP monitor unable to detected by hot-plug

We tested hot-plug first time, and didn't find good point.

Steps:
---------------------------
1. boot OS only with eDP
2. Hot-plug DP cable, the monitor will show "Display NO SIGNAL"
3. If boot with DP, unplug then plug, DP monitor is able to detected.
Comment 1 Daniel Vetter 2014-01-09 08:24:27 UTC
What happens when you manually run xrandr in the failing case? Do we detect a monitor (i.e. is only the hotplug event not working) or do we completely fail to detect the screen?
Comment 2 Daniel Vetter 2014-01-09 08:28:25 UTC
Ỳang Guang said that booting with HDMI, unplug and then plugging in DP also doesn't work. Is that correct?
Comment 3 Guo Jinxian 2014-01-09 08:51:19 UTC
(In reply to comment #1)
> What happens when you manually run xrandr in the failing case? Do we detect
> a monitor (i.e. is only the hotplug event not working) or do we completely
> fail to detect the screen?

The DP is able to detect by xrandr, but the monitor shows "There is no signal coming from your computer". 

[root@x-bdw01 ~]# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 282mm x 165mm
   1920x1080      60.0*+   40.0
   1400x1050      60.0
   1280x1024      60.0
   1280x960       60.0
   1024x768       60.0
   800x600        60.3     56.2
   640x480        59.9
DP1 connected (normal left inverted right x axis y axis)
   2560x1600      60.0 +
   1920x1440      60.0
   1920x1200      59.9
   1920x1080      60.0     50.0     59.9     24.0     24.0
   1920x1080i     60.1     50.0     60.0
   1600x1200      60.0
   1280x1024      75.0     60.0
   1280x800       59.8
   1152x864       75.0
   1280x720       60.0     50.0     59.9
   1024x768       75.1     60.0
   800x600        75.0     60.3
   720x576        50.0
   720x480        60.0     59.9
   640x480        75.0     60.0     59.9
   720x400        70.1
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
You have new mail in /var/spool/mail/root
Comment 4 Guo Jinxian 2014-01-09 09:02:15 UTC
(In reply to comment #2)
> Ỳang Guang said that booting with HDMI, unplug and then plugging in DP also
> doesn't work. Is that correct?

Yes, Guang is right.
Comment 5 Daniel Vetter 2014-01-10 07:55:54 UTC
Sounds very much like we fail to set up some DDI state between HDMI/DP switching. Paulo?
Comment 6 Jesse Barnes 2014-01-10 20:18:52 UTC
So the display can come up if you set a mode on it explicitly.  But I see what look to be DP timeouts, or at least really slow mode enumeration and mode setting.  Still looking.
Comment 7 Jesse Barnes 2014-01-10 21:07:25 UTC
Please try this:

http://lists.freedesktop.org/archives/intel-gfx/2014-January/038161.html
Comment 8 Daniel Vetter 2014-01-14 13:44:10 UTC
This should be fixed with

commit 09f2344d0896eb458a639b922224c7a202c11599
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Fri Jan 10 13:13:09 2014 -0800

    drm/i915/bdw: make sure south port interrupts are enabled properly v2

*** This bug has been marked as a duplicate of bug 72833 ***
Comment 9 Guo Jinxian 2014-01-15 01:28:22 UTC
Our Broadwell doesn't work now, we are repairing it. And I will verify this bug when the Broadwell had repaired. Thanks.
Comment 10 Guo Jinxian 2014-01-15 03:02:50 UTC
Verified on latest -fixes (9f2344d0896eb458a639b922224c7a202c11599), this bug had fixed, thanks.
Comment 11 Elizabeth 2017-10-06 14:41:12 UTC
Closing old verified.


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.