Created attachment 115680 [details] dmesg log ==System Environment== -------------------------- HDMI monitor: Samsung LS24C570 DP monitor: Dell U2311Hb BIOS: V59 Regression: Yes, don't see this issue on drm-intel-testing-2015-04-23 Non-working platforms: BSW ==kernel== -------------------------- -testing: drm-intel-testing-2015-05-08 (fails) ==Bug detailed description== ----------------------------- 3 monitors are all black screen after xinit + S3. 3 monitors show text console if running "pkill X" ==Reproduce steps== ---------------------------- 1. Reboot with 3 monitors connected 2. xinit & 3. echo mem > /sys/power/state 4. Resume by clicking the keyboard
Created attachment 115681 [details] "xrandr --prop" before S3
Created attachment 115682 [details] "xrandr --verbose" before S3
Created attachment 115683 [details] "xrandr --prop" after S3
Created attachment 115684 [details] "xrandr --verbose" after S3
This issue also exists on eDP + HDMI.
Bisect to commit 6c373ca89399c5a3f7ef210ad8f63dc3437da345 but booting fails with huge messages on console.
Created attachment 115799 [details] dmesg on HSW On HSW, when connect to DP monitor, xinit + S3 will also fail.
exists on drm-intel-testing-2015-05-22 with BSW
Created attachment 116109 [details] dmesg on BDW
This issue still exists on BDW with drm-intel-testing-2015-05-22 kernel
Created attachment 116146 [details] [review] Debug patch The "CRTC fixup failed" line in the HSW log indicates intel_crtc_compute_config() fails after resume. And that means the modeset is aborted before the new pipe config is dumped to the log, which would give us a clue as to why it failed. Can you run the test again on HSW with this patch applied, and also with "drm.debug=0x1e log_buf_len=4M" in the kernel command line?
Created attachment 116194 [details] run the test again on HSW with patch applied
Created attachment 116198 [details] [review] Possible fix Could you try if the attached patch fixes the issue?
Test with the patch,connect with three monitor(DP,eDP,HDMI),except eDP,the other two can't display.
(In reply to xubin from comment #14) > Test with the patch,connect with three monitor(DP,eDP,HDMI),except eDP,the > other two can't display. Can you add dmesg (with debug information) for this failure?
I retry on x-hswm24 with HDMI monitor connected. With drm-intel-testing-2015-05-22, after S3, eDP shows X and HDMI is black screen. system is alive. With drm-intel-testing-2015-05-22 + patch, after S3, eDP shows X and HDMI is black screen too. And system hangs. Unfortunately the test machine does not have serial port so there is no dmesg captured.
The fix I wrote is superseded by Maarten's latest atomic patch series that has been just merged. Could you test with latest -nightly?
Created attachment 116295 [details] dmesg log with eDP and HDMI connected I retry latest nightly (commit 0761e2d5d55e8311950514fda1ec414838525985) on x-hswm24 with eDP/HDMI connected, after resuming from S3, both eDP and HDMI are fine.
(In reply to Jeff Zheng from comment #18) > Created attachment 116295 [details] > dmesg log with eDP and HDMI connected > > I retry latest nightly (commit 0761e2d5d55e8311950514fda1ec414838525985) on > x-hswm24 with eDP/HDMI connected, after resuming from S3, both eDP and HDMI > are fine. So that's fixed in nightly, good. But I'm afraid the issue might exist with the drm-intel-next branch. Could you verify?
Not yet. I need to double check with BSW. And we find that latest nightly might have a big regression. When boot BSW with both eDP and DP connected, both monitors are black screen. We're double checking to report an new bug. When that issue got fixed, I will check on BSW again.
Will update after Bug 90861 got fixed.
(In reply to Ander Conselvan de Oliveira from comment #19) > But I'm afraid the issue might exist with the drm-intel-next branch. That should have been drm-intel-next-fixes.
*** Bug 90911 has been marked as a duplicate of this bug. ***
I tried on BSW for several commits: exist in drm-intel-next-fixes commit bf546f8158e2df2656494a475e6235634121c87c exists in drm-intel-testing-2015-05-22 Fail to boot in latest nightly because of bug 90929 exist in drm-intel-nightly commit d57981d00ed80a859c24fe937c70959dd646e439 (the commit before 3bae26eb2991c00670df377cf6c3bc2b0577e82a)
Please retest on current drm-intel-nightly.
Created attachment 116571 [details] dmesg of hsw Test with the latest drm-intel-nightly kernel(commit 2a36ab374449e3794b4be6be01f1a47cb6ee5b83) on HSW platform with 3 monitor (two DP,one VGA),only one DP can resume normally. Then pkill x ,the three monitor show text mode.
Created attachment 116572 [details] dmesg of bsw Test with the latest drm-intel-nightly kernel(commit 2a36ab374449e3794b4be6be01f1a47cb6ee5b83) on BSW platform with 3 monitor (one DP,one eDP,one VGA),only eDP can resume normally. Then pkill x ,the three monitor come to text console.
The fix we have in -next-fixes for this will conflict with Maarten's next series of atomic modesetting patches which should also fix this.
Test it on BDW with latest drm-intel-next-fixes_4ed9fb_20150618+ kernel, S3 will automatic back, 3 monitors can light up.
Has Maarten's fix for this landed?
Not yet, it's on the mailing list.
Maarten's patches that fix this are in -nightly now.
Closing resolved+fixed after 1.5 years of silence.
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.