[Bug 93579] drm_intel_gem_bo_context_exec() failed: Input/output error
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 15 16:10:08 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=93579
yann <yann.argotti at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|intel-gfx-bugs at lists.freede |idr at freedesktop.org
|sktop.org |
Component|DRM/Intel |Drivers/DRI/i915
Product|DRI |Mesa
QA Contact|intel-gfx-bugs at lists.freede |
|sktop.org |
--- Comment #1 from yann <yann.argotti at intel.com> ---
There are improvements pushed in kernel and Mesa that will benefit to your
system, so please re-test with latest kernel & Mesa to see if this issue is
still occurring (you may update / upgrade to a more recent version of Fedora).
In the meantime, assigning to Mesa product (please let me know if I am mistaken
with this GPU Hang).
>From this error dump, hung is happening in render ring batch with active head
at 0x7c79f140, with 0x7a000003 (PIPE_CONTROL) as IPEHR.
Batch extract (around 0x7c79f140):
0x7c79f11c: 0x0000007f: MI_NOOP
0x7c79f120: 0xffffffff: UNKNOWN
0x7c79f124: 0x70040000: 3D UNKNOWN: 3d_965 opcode = 0x7004
0x7c79f128: 0x00000000: MI_NOOP
0x7c79f12c: 0x7a000003: PIPE_CONTROL
0x7c79f130: 0x00100020: no write, cs stall, DC flush,
0x7c79f134: 0x00000000: destination address
0x7c79f138: 0x00000000: immediate dword low
0x7c79f13c: 0x00000000: immediate dword high
0x7c79f140: 0x7a000003: PIPE_CONTROL
0x7c79f144: 0x00101400: no write, cs stall, render target cache flush,
texture cache invalidate,
0x7c79f148: 0x00000000: destination address
0x7c79f14c: 0x00000000: immediate dword low
0x7c79f150: 0x00000000: immediate dword high
--
You are receiving this mail because:
You are on the CC list for the bug.
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-gfx-bugs/attachments/20160915/a69d69ab/attachment.html>
More information about the intel-gfx-bugs
mailing list