[Bug 111699] [CI][BAT][iommu]igt at gem_exec_suspend@basic-s4-devices - fail - DMAR write fault 7 + Failed assertion: !"GPU hung"
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Sep 17 09:29:55 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111699
--- Comment #5 from Lakshmi <lakshminarayana.vudum at intel.com> ---
(In reply to Chris Wilson from comment #2)
> 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.
(In reply to CI Bug Log from comment #4)
> A CI Bug Log filter associated to this bug has been updated:
>
> {- ICL: igt at gem_exec_suspend@basic-s4-devices - fail - Failed assertion:
> !"GPU hung" -}
> {+ ICL: igt at gem_exec_suspend@basic-s4-devices - fail - Failed assertion:
> !"GPU hung" +}
>
> New failures caught by the filter:
>
> *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6903/shard-iclb6/
> igt at gem_exec_suspend@basic.html
One more instance, but on shards.
<3> [209.832569] DMAR: DRHD: handling fault status reg 2
<3> [209.832629] DMAR: [DMA Write] Request device [00:02.0] fault addr 41000
[fault reason 07] Next page table ptr is invalid
DMA_FADDR: 0x00000000_007f8b78
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190917/8ba22545/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list