<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [IGT] gpu couldn't recovery after running drv_hangman in dom0" href="https://bugs.freedesktop.org/show_bug.cgi?id=101403#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [IGT] gpu couldn't recovery after running drv_hangman in dom0" href="https://bugs.freedesktop.org/show_bug.cgi?id=101403">bug 101403</a> from <a class="email" href="mailto:xiong.y.zhang@intel.com" title="XiongZhang <xiong.y.zhang@intel.com>"> XiongZhang</a> <pre>I just install an upstream xen 4.9 and upstream 4.11 kernel, then use xen to boot 4.11 kernel. Both of them don't contain any xen-gvt related code and I don't boot a guest, so there is no vgpu emulation. In this case, i915 driver access hw directly and doesn't trap into vgpu. I bisect the upstream 4.11 kernel through checking gpu recovery and found the above commit. Then I tried drm-intel-nightly and found it has the same issue. Just now, I boot drm-intel-nightly kernel to text mode using xen, then run drv_hangman, but GPU still couldn't recovery. And through the dmesg, it is in full-ppgtt mode as dmesg output "[i915_driver_load[i915]] ppgtt mode: 3" (In reply to Chris Wilson from <a href="show_bug.cgi?id=101403#c4">comment #4</a>) > What did you bisect? The failure of drv_hangman is quite normal for > !full-ppgtt, which I presume is the result of the vgpu emulation. The hang > of X is another issue unconnected to reset. You should not be running igt > while anything else is accessing the gpu as most of the tests assume > exclusive ownership of the device.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>