<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - set-to-domain returned EIO" href="https://bugs.freedesktop.org/show_bug.cgi?id=74007#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - set-to-domain returned EIO" href="https://bugs.freedesktop.org/show_bug.cgi?id=74007">bug 74007</a> from <a class="email" href="mailto:mika.kuoppala@intel.com" title="Mika Kuoppala <mika.kuoppala@intel.com>"> Mika Kuoppala</a> <pre>(In reply to <a href="show_bug.cgi?id=74007#c2">comment #2</a>) > Repeat after me, the driver is never, ever, allowed to return EIO through > set-to-domain (or i915_gem_fault() and friends). > > If that i-g-t assert is reliable, that is just what happened here. There are multiple problems currently with resets in nightly, but what is happening here is that gem_reset_stats (btw fixed in most recent master) will stop all rings after injecting hang. In nightly, this results in same context being claimed twice for the same hang, and gets banned. Then comes the set_domain() for that context and well, it has been, errorneously, banned.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>