[Bug 98325] New: GPU HANG: ecode 9:0:0x85dffffb

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Oct 19 17:43:58 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=98325

            Bug ID: 98325
           Summary: GPU HANG: ecode 9:0:0x85dffffb
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Driver/intel
          Assignee: chris at chris-wilson.co.uk
          Reporter: nalimilan at club.fr
        QA Contact: intel-gfx-bugs at lists.freedesktop.org

I'm using Fedora 24 with kernel 4.7.5-200, GPU Intel Corporation HD Graphics
520 (rev 07). Today I've been forcefully logged out of my X session, and I've
spotted this in the system logs:

oct. 19 19:34:32 mob01772 kernel: [drm] stuck on render ring
oct. 19 19:34:32 mob01772 kernel: [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
[12939], reason: Engine(s) hung, action: reset
oct. 19 19:34:32 mob01772 kernel: [drm] GPU hangs can indicate a bug anywhere
in the entire gfx stack, including userspace.
oct. 19 19:34:32 mob01772 kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
oct. 19 19:34:32 mob01772 kernel: [drm] drm/i915 developers can then reassign
to the right component if it's not a kernel issue.
oct. 19 19:34:32 mob01772 kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
oct. 19 19:34:32 mob01772 kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
oct. 19 19:34:32 mob01772 kernel: drm/i915: Resetting chip after gpu hang
[...]
oct. 19 19:34:34 mob01772 kernel: [drm] RC6 on
oct. 19 19:34:44 mob01772 kernel: [drm] stuck on render ring
oct. 19 19:34:44 mob01772 kernel: [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
[12939], reason: Engine(s) hung, action: reset
oct. 19 19:34:44 mob01772 kernel: drm/i915: Resetting chip after gpu hang

FWIW, this happened right after starting an I/O intensive operation, which
might be related to the hang.

-- 
You are receiving this mail because:
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/20161019/0f8dfc1e/attachment.html>


More information about the intel-gfx-bugs mailing list