<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB/IVB/HSW]I-G-T gem_wait_render_timeout Aborted" href="https://bugs.freedesktop.org/show_bug.cgi?id=64270#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB/IVB/HSW]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#c8">comment #8</a>) > Sorry, the 1st patch doesn't cases system boot fail and the bisect result is > invalid. > System boot fail because of commit 14134f6584212d585b310ce95428014b653dfaf6, > revert this commit, this issue goes away(<a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [ILK Bisected]System boot fail with -queued kernel" href="show_bug.cgi?id=63628">Bug 63628</a>). > > As you said this bug is a bit random, run ./gem_wait_render_timeout 10 > times, It fails 6 times. I test the 2nd patch, the result is also unstable. Ok. The original 'gem_wait_render_timeout: gem_wait_render_timeout.c:211: main: Assertion `timeout == 0' failed.' assertion should be solved by the first patch 'fix gem_wait_ioctl remaining time when timeout'. There is another gem_wait_render_timeout assertion, that is also random, but unrelated: '1 iters is enough work gem_wait_render_timeout: gem_wait_render_timeout.c:181: main: Assertion 'gem_bo_busy(fd, dst2->handle) == 1' failed.' Where the calibration for the number of iterations was obviously wrong. Could you verify if you have the same results?</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>