<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=106342#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=106342">bug 106342</a> from <a class="email" href="mailto:thiago@kde.org" title="Thiago Macieira <thiago@kde.org>"> Thiago Macieira</a> <pre>(In reply to Jani Saarinen from <a href="show_bug.cgi?id=106342#c6">comment #6</a>) > Thiago, what do you mean with reopen? What bug specifically? This bug is in NEEDINFO state. That means you're expecting more information from me. If it's not the drm.debug=0x1e for 3 days, then what is it? (In reply to Chris Wilson from <a href="show_bug.cgi?id=106342#c5">comment #5</a>) > One bit of information that would be useful here is > <a href="https://patchwork.freedesktop.org/series/42550/">https://patchwork.freedesktop.org/series/42550/</a> to differentiate between > whether the new ELSP submission was loaded and the seqno write went astray > or if it died without seeing the new request. Applying patches to the kernel means disabling secure boot. I'd rather not, but can do if nothing else solves it.</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 assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>