<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@gem_sync@basic-many-each - fail - Failed assertion: !"GPU hung"" href="https://bugs.freedesktop.org/show_bug.cgi?id=107715#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@gem_sync@basic-many-each - fail - Failed assertion: !"GPU hung"" href="https://bugs.freedesktop.org/show_bug.cgi?id=107715">bug 107715</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Something odd I spotted here: <7>[ 232.791376] missed_breadcrumb [head 149a8, postfix 149f8, tail 14a20, batch 0x00000000_00002000]: <7>[ 232.791404] missed_breadcrumb [0000] 13244001 00000104 00000000 00000000 11000001 00022220 ffffffff 11000001 <7>[ 232.791412] missed_breadcrumb [0020] 00022228 00470000 12400001 00022228 7fffc000 00000000 18800100 00002000 <7>[ 232.791420] missed_breadcrumb [0040] 13204001 00000104 00000000 00000000 11000001 00002044 00000001 11000001 <7>[ 232.791426] missed_breadcrumb [0060] 00012040 00000001 10800001 000000c0 00000001 01000000 There's only one MI_FLUSH_DW for the invalidate at the start of the request, but in emit_mi_flush_dw(), there's the comment: /* * Not only do we need a full barrier (post-sync write) after * invalidating the TLBs, but we need to wait a little bit * longer. Whether this is merely delaying us, or the * subsequent flush is a key part of serialising with the * post-sync op, this extra pass appears vital before a * mm switch! */ Hmm.</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> <li>You are on the CC list for the bug.</li> </ul> </body> </html>