Created attachment 64010 [details] dmesg after booting System Environment: -------------------------- Platform: Ivybridge Kernel: (drm-intel-next-queued)dab92e08895537c7260c811f8e93cbf749f0b727 Bug detailed description: ------------------------- On IVB platform ,booting only with HDMI monitor.it can't show the correctly prefer mode,while starting X and run command "xrandr",it shows this: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 HDMI1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 519mm x 324mm 1920x1200 60.0 + 1920x1080 60.0 30.0 1600x1200 60.0 1680x1050 60.0 59.9 1680x945 60.0 1400x1050 74.9 60.0 59.9 1600x900 60.0 1280x1024 75.0 60.0 1440x900 75.0 59.9 59.9 1280x960 60.0 1366x768 60.0 1360x768 60.0 1280x800 74.9 59.8 59.9 1152x864 75.0 1280x768 74.9 59.9 60.0 1280x720 60.0 1440x576 25.0 1024x768 75.1 75.0 70.1 60.0* 1440x480 30.0 1024x576 60.0 800x600 72.2 75.0 60.3 56.2 848x480 60.0 720x480 59.9 640x480 75.0 72.8 60.0 59.9 59.9 720x400 70.1 DP1 disconnected (normal left inverted right x axis y axis) I'm confused it can find unconnected monitor VGA.
Crappy hardware returning all zeros rather than a NAK. Is this an SDV?
(In reply to comment #1) > Crappy hardware returning all zeros rather than a NAK. Is this an SDV? No,it's not a SDV.
Can you please test whether reverting aaa377302b2994fcc2c6 works around the issue?
(In reply to comment #3) > Can you please test whether reverting aaa377302b2994fcc2c6 works around the > issue? Ok ,I revert the commit aaa377302b2994fcc2c66741b47da33feb489dca, the issue is gone.
Please attach the dmesg with drm.debug=0xe added to the kernel cmdline for a broken kernel. Generally, _always_ attach the dmesg with drm.debug=0xe for output issues (i.e. wrong detection, black screen and all such issues).
Created attachment 64076 [details] [review] sanity check the edid when probing outputs Also please test this patch.
Created attachment 64087 [details] dmesg info with drm.debug=0xe (In reply to comment #5) > Please attach the dmesg with drm.debug=0xe added to the kernel cmdline for a > broken kernel. > > Generally, _always_ attach the dmesg with drm.debug=0xe for output issues (i.e. > wrong detection, black screen and all such issues). Here is the new dmesg of issue with drm.debug=0xe.
Created attachment 64088 [details] dmesg info with patch (In reply to comment #6) > Created attachment 64076 [details] [review] [review] > sanity check the edid when probing outputs > > Also please test this patch. I try this patch,the issue is gone, and I attach the dmesg info.
Created attachment 64098 [details] [review] new patch Chris pointed out an issue with my previous patch, can you please test again with this new version?
Created attachment 64099 [details] with new patch's dmesg info (In reply to comment #9) > Created attachment 64098 [details] [review] [review] > new patch > > Chris pointed out an issue with my previous patch, can you please test again > with this new version? I try the new version of patch and attach the dmesg, and can't reproduce this issue.
Fix merged to -queued as commit 390bd1fd276c7c86bb7d658d7ac8a4ce6af6a21e Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Wed Jul 11 12:31:52 2012 +0200 drm/i915: check whether we actually received an edid in detect_ddc
(In reply to comment #11) > Fix merged to -queued as > > commit 390bd1fd276c7c86bb7d658d7ac8a4ce6af6a21e > Author: Daniel Vetter <daniel.vetter@ffwll.ch> > Date: Wed Jul 11 12:31:52 2012 +0200 > > drm/i915: check whether we actually received an edid in detect_ddc confirmed, -queued including this commit.
A patch referencing this bug report has been merged in Linux v3.6-rc1: commit a2bd1f541f1990dda7dd62f190342c9a964ceb4f Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Wed Jul 11 12:31:52 2012 +0200 drm/i915: check whether we actually received an edid in detect_ddc
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.