<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW] linux next-20170407+ boots to a blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=100755#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW] linux next-20170407+ boots to a blank screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=100755">bug 100755</a> from <a class="email" href="mailto:dhinakaran.pandiyan@intel.com" title="Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>"> Dhinakaran Pandiyan</a> <pre>(In reply to Rafael Ristovski from <a href="show_bug.cgi?id=100755#c0">comment #0</a>) > Created <a href="attachment.cgi?id=130972" name="attach_130972" title="next-20170324 with fastboot=1, shows suspend/resume, works fine">attachment 130972</a> <a href="attachment.cgi?id=130972&action=edit" title="next-20170324 with fastboot=1, shows suspend/resume, works fine">[details]</a> > next-20170324 with fastboot=1, shows suspend/resume, works fine > > Ever since next-20170407 (last good next-20170324, versions in-between not > tested) my laptops screen stopped turning on after resuming. > Upon removing i915.fastboot=1 from cmdline, the display now turns off > immediately after boot, which means enabling fastboot only covered up the > real issue. > > HW: > i7-4500U Haswell with HD 4400 I think you are right, fastboot adjusts the m_n values, which might explain why it worked with fastboot=1. I have attached the revert for you test. Please let me know if that works.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>