==System Environment== -------------------------- Regression: Yes. Good commit on -next-queued: 1cf0ba14740d96fbf6f58a201f000a34b74f4725 Non-working platforms: BYT-M ==kernel== -------------------------- origin/drm-intel-nightly: c95053d599112ec3b8c27a632e3c1544558891a4(fails) drm-intel-nightly: 2014y-07m-30d-22h-36m-53s integration manifest origin/drm-intel-next-queued: 5193109cd669c7990b043a7187548546c16f8af3(fails) drm/i915: Align intel_dsi*.c files a bit origin/drm-intel-fixes: f4be89cecea437aaddd7700d05c6bdb5678041f7(works) drm/i915: Fix crash when failing to parse MIPI VBT ==Bug detailed description== System unable resume from S3/S4 ==Reproduce steps== ---------------------------- 1. echo mem >/sys/power/state 2. Press power button
Created attachment 104089 [details] fix mst hpd suspend Could you try the attached 4 patches on latest -nightly?
Created attachment 104133 [details] dmesg (In reply to comment #1) > Created attachment 104089 [details] > fix mst hpd suspend > > Could you try the attached 4 patches on latest -nightly? S3/S4 works well withe these patches on latest -nightly(79e44bfa10063ee529140e88fdc401c4ce07d644)
The fix for this is merged now. Note that there are some WARNs remaining about eDP VDD state checking after resume, but those are independent and fixed by Ville's VDD locking fixes under review.
(In reply to comment #3) > The fix for this is merged now. Note that there are some WARNs remaining > about eDP VDD state checking after resume, but those are independent and > fixed by Ville's VDD locking fixes under review. Resume works well, but here has another two bugs about S3 and S4, which tracked by bug 82841 and bug 82842. Verify this one.
Fixed by commit 1a125d8a2c22b11741fc47d4ffcf7a5ffa044dd3 Author: Imre Deak <imre.deak@intel.com> Date: Mon Aug 18 14:42:46 2014 +0300 drm/i915: don't try to retrain a DP link on an inactive CRTC
Closing verified+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.