<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT]igt@gem_exec_suspend@basic-s4-devices - fail - Failed assertion: !"GPU hung""
href="https://bugs.freedesktop.org/show_bug.cgi?id=111699#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT]igt@gem_exec_suspend@basic-s4-devices - fail - Failed assertion: !"GPU hung""
href="https://bugs.freedesktop.org/show_bug.cgi?id=111699">bug 111699</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>Correlates with
<3> [90.027305] DMAR: DRHD: handling fault status reg 2
<3> [90.027363] DMAR: [DMA Write] Request device [00:02.0] fault addr 43000
[fault reason 07] Next page table ptr is invalid
In the GPU hang, it dies on MI_BATCH_BUFFER_END and doesn't return execution to
the ring. I presume that's when the lookup failed.
DMA_FADDR: 0x00000000_00013870
didn't cross a page so what it was looking up that failed is a mystery.
"fault addr 43000" looks to be a reference to BBADDR: 0x00000000_00042fd4
But write? gem_exec_suspend does use a scratch page to verify HW works across
suspend (using MI_STORE_DWORD_IMM), so probably that's the page that is absent.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>