<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [GM45] boot-up broken in kernel 3.4.10 - screen stays blank (bad patch identified)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54575#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - [GM45] boot-up broken in kernel 3.4.10 - screen stays blank (bad patch identified)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54575">bug 54575</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=54575#c13">comment #13</a>) > Anyway, with the change to drm.debug=6 I can't seem to be able to reproduce > the blank screen - is it possible that additional latencies through that > option are influencing ring init? Yes. No idea why, the posting reads seemed to be the most sensible attempt to introduce some delays along with the write barriers. What you can try is to just put the entire init in a loop and repeat say 10 times until it works.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>