<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [HSW] trying to runtime suspend with power well enabled on 3.15" href="https://bugs.freedesktop.org/show_bug.cgi?id=80203#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [HSW] trying to runtime suspend with power well enabled on 3.15" href="https://bugs.freedesktop.org/show_bug.cgi?id=80203">bug 80203</a> from <a class="email" href="mailto:imre.deak@gmail.com" title="Imre Deak <imre.deak@gmail.com>"> Imre Deak</a> <pre>(In reply to <a href="show_bug.cgi?id=80203#c4">comment #4</a>) > I've since upgraded to 3.16.0 and turned on drm.debug and I think I have the > same problem but the stack differs. > > I intend to upgrade to the latest 3.17 RC next time I reboot. > > I've concatenated /var/log/dmesg and dmesg. Let me know if you want the > missing pieces from kern.log. Thanks. One possibility is that it's the locking issue fixed by: commit e39b999a6f229386ea6c58cb1c10ce9dc912869b Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>> Date: Thu Sep 4 14:53:14 2014 +0300 drm/i915: Fix edp vdd locking It would need backporting to 3.17-rc, so could you also try the git://anongit.freedesktop.org/drm-intel drm-intel-nightly branch which includes the above fix? If you can reproduce the problem with that too, could you attach the dmesg log starting from boot? You can increase the log buf size with the log_buf_len kernel parameter. I would need it at least until the first intel_display_power_get/put() warning shows up.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>