[Bug 111395] GPU HANG: ecode 9:0:0x86dfbff9, in Map-GL [6016], reason: Hang on render ring, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 12 05:17:22 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111395
--- Comment #29 from Kenneth Graunke <kenneth at whitecape.org> ---
(In reply to yugang from comment #28)
> just quick checked kernel in customer side, has no
> d2b4b97933f5adacfba42dc3b9200d0e21fbe2c4.
>
> do you know if only backporting this commit is useful for 0x84df7cfc? or
> still need mesa and media side changes? thank you
It certainly couldn't hurt. Better protecting contexts from one another is
definitely helpful for system stability, otherwise all components on the
systems need to agree on common values for everything.
If you don't actually have that commit in the kernel, then everybody using the
GPU (mesa, media, opencl, etc) must agree on the value of
CS_DEBUG_MODE2::Constant Buffer Address Offset Disable. If a driver starts up
and inherits the wrong value from another context, it will absolutely crash the
GPU. You can get lucky if you start your processes in the right order, I
suppose...
I am really curious why your Mesa thinks it can use absolute pointers for
constant buffers. It's supposed to query the kernel and only enable that
functionality (!compiler->constant_buffer_0_is_relative) if the
I915_PARAM_HAS_CONTEXT_ISOLATION getparam is present. Perhaps you don't have
that kernel sha, but you do have the getparam? For a while, Mesa was broken
and didn't check, but that was in the 17.x era.
For reference, the broken Mesa commit that introduced this without checking was
8ec5a4e4a4a32f4de351c5fc2bf0eb615b6eef1b. But it was reverted in
013d33122028f2492da90a03ae4bc1dab84c3ee9. Proper support was re-added in
fa8a764b62588420ac789df79ec0ab858b38639f.
If it is easier, rather than porting the kernel change, you can disable
absolute constant addressing in Mesa. It's not really critical to have it.
--
You are receiving this mail because:
You are the assignee 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-3d-bugs/attachments/20190912/09e34bb8/attachment.html>
More information about the intel-3d-bugs
mailing list