<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@drv_selftest@live_execlists - dmesg-warn - *ERROR* MMIO: GuC action 0x2 failed with error -5 0xf000f000" href="https://bugs.freedesktop.org/show_bug.cgi?id=108622#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI][BAT] igt@drv_selftest@live_execlists - dmesg-warn - *ERROR* MMIO: GuC action 0x2 failed with error -5 0xf000f000" href="https://bugs.freedesktop.org/show_bug.cgi?id=108622">bug 108622</a> from <a class="email" href="mailto:jon.ewins@intel.com" title="Jon Ewins <jon.ewins@intel.com>"> Jon Ewins</a> <pre>Agreed, this was too generic an update for this particular bug. We are about to upstream new patches for Gen9 and Gen11 that support a changed unified interface to the GuC along with the corresponding firmware and so are deferring further actions on current guc issues. In this specific case, the existing Gen9 guc preemption paths are no longer required and GuC submission on gen9 will not be supported. The imminent new guc code patches will initially disable preemption with guc, but not touch/remove this code. Follow up patches will reinstate GuC based preemption for Gen11+, at which time this code will be cleaned up. Certainly some of the current code can be cleaned up now, but How the new preemption implementation will be staged in terms of H2G interactions is tbd.</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>