Created attachment 103662 [details] dmesg ==System Environment== -------------------------- Regression: Yes Good commit on drm-next: 008f40451d0e59f220a4fa13aaf75d04303a01a1 Non-working platforms: BDW ==kernel== -------------------------- origin/drm-intel-nightly: 8734408c113bb38234ed03ec51c723b3deff579b(fails) drm-intel-nightly: 2014y-07m-18d-15h-21m-24s integration manifest origin/drm-intel-next-queued: 34548e510657af829032f23128c0c01ebe48ef21(works) drm/i915: Do not unmap object unless no other VMAs reference it origin/drm-intel-fixes: c6930992948adf0f8fc1f6ff1da51c5002a2cf95(works) Revert "drm/i915: reverse dp link param selection, prefer fast over wide again" origin/drm-fixes: 3c169e5629d6bce9aede3907aeb38f1c23f61952(works) Merge branch 'drm-fixes-3.16' of git://people.freedesktop.org/~agd5f/linux into drm-fixes origin/drm-next:b957f457fbce30cc4901dc28f2b56f2b15dfe84a(fails) drm/radeon: use helpers ==Bug detailed description== ----------------------------- One DP monitor was recognized as two DP monitors by mistake. Output : [root@x-bdw01 ~]# xrandr Screen 0: minimum 8 x 8, 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.00*+ 1400x1050 59.98 1280x1024 60.02 1280x960 60.00 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) DP2 connected (normal left inverted right x axis y axis) 1920x2160 59.99 + DP3 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 698mm x 392mm 1920x2160 59.99 + 1920x1200 59.88 1920x1080 59.99* 1600x1200 60.00 1680x1050 59.95 1280x1024 75.02 60.02 1280x800 59.81 1152x864 75.00 1024x768 75.08 60.00 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08 VIRTUAL1 disconnected (normal left inverted right x axis y axis)
==Reproduce steps== ---------------------------- 1. Boot the device with DP monitor 2. ./testdisplay -i
==Bisect results== ---------------------------- Bisect shows: 0e32b39ceed665bfa4a77a4bc307b6652b991632 is the first bad commit commit 0e32b39ceed665bfa4a77a4bc307b6652b991632 Author: Dave Airlie <airlied@redhat.com> AuthorDate: Fri May 2 14:02:48 2014 +1000 Commit: Dave Airlie <airlied@redhat.com> CommitDate: Tue Jul 22 11:20:26 2014 +1000 drm/i915: add DP 1.2 MST support (v0.7) This adds DP 1.2 MST support on Haswell systems. Notes: a) this reworks irq handling for DP MST ports, so that we can avoid the mode config locking in the current hpd handlers, as we need to process up/down msgs at a better time. Changes since v0.1: use PORT_PCH_HOTPLUG to detect short vs long pulses add a workqueue to deal with digital events as they can get blocked on the main workqueue beyong mode_config mutex fix a bunch of modeset checker warnings acks irqs in the driver cleanup the MST encoders Changes since v0.2: check irq status again in work handler move around bring up and tear down to fix DPMS on/off use path properties. Changes since v0.3: updates for mst apis more state checker fixes irq handling improvements fbcon handling support improved reference counting of link - fixes redocking. Changes since v0.4: handle gpu reset hpd reinit without oopsing check link status on HPD irqs fix suspend/resume Changes since v0.5: use proper functions to get max link/lane counts fix another checker backtrace - due to connectors disappearing. set output type in more places fro, unknown->displayport don't talk to devices if no HPD asserted check mst on short irqs only check link status properly rebase onto prepping irq changes. drop unsued force_act Changes since v0.6: cleanup unused struct entry. [airlied: fix some sparse warnings].
bug 81890, bug 81895, bug 81903, and bug 81856 are caused by the same patch.
*** This bug has been marked as a duplicate of bug 81895 ***
Closing verified+duplicate as duplicate of closed+fixed.
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.