<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [PNV] S3 /S4 resume cause call trace, and screen failed to light up after resume while X is running." href="https://bugs.freedesktop.org/show_bug.cgi?id=90911#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [PNV] S3 /S4 resume cause call trace, and screen failed to light up after resume while X is running." href="https://bugs.freedesktop.org/show_bug.cgi?id=90911">bug 90911</a> from <a class="email" href="mailto:hengx.ding@intel.com" title="Ding Heng <hengx.ding@intel.com>"> Ding Heng</a> <pre>(In reply to Ander Conselvan de Oliveira from <a href="show_bug.cgi?id=90911#c2">comment #2</a>) > This might be a duplicate of <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [HSW/BDW/BSW] monitors are all black screen after xinit + S3 when the monitors contain eDP and DP." href="show_bug.cgi?id=90396">bug 90396</a>, where the force restore modeset > fails in the atomic checks. Could you reproduce the bug again with > 'drm.debug=0x1e log_buf_len=4M' in the kernel command line and attach dmesg > again? I had tried the bisect commit in <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [HSW/BDW/BSW] monitors are all black screen after xinit + S3 when the monitors contain eDP and DP." href="show_bug.cgi?id=90396">bug 90396</a>, this kernel works well on PNV.</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>