<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB/IVB/HSW Bisected]I-G-T gem_wait_render_timeout Aborted" href="https://bugs.freedesktop.org/show_bug.cgi?id=64270#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB/IVB/HSW Bisected]I-G-T gem_wait_render_timeout Aborted" href="https://bugs.freedesktop.org/show_bug.cgi?id=64270">bug 64270</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=64270#c2">comment #2</a>) > (In reply to <a href="show_bug.cgi?id=64270#c1">comment #1</a>) > > Created <a href="attachment.cgi?id=78931" name="attach_78931" title="fix gem_wait_ioctl remaining time when timeout">attachment 78931</a> <a href="attachment.cgi?id=78931&action=edit" title="fix gem_wait_ioctl remaining time when timeout">[details]</a> <a href='page.cgi?id=splinter.html&bug=64270&attachment=78931'>[review]</a> [review] [review] > > fix gem_wait_ioctl remaining time when timeout > > > > I'm guessing the bug is a bit random, I can't see how it can relate to the > > bisected commit. I noticed that for timeouts from gem_wait_ioctl we don't > > always return 0, so that can trigger the assert. Attached is a fix that > > should make sure we always return 0 remaining time for timeouts. > > Test with this patch, System boot fail. On what platform? Is it 100% reproducible? Could you attach logs about the boot failure? On IVB/drm-intel-nightly I can easily reproduce the original problem and with the fix applied I can boot okay and can't reproduce the problem. So based on this I think the boot failure is an independent issue, or something revealed by the fix.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>