[Bug 99329] New: GPU HANG: ecode 6:-1:0x00000000

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 9 13:36:29 UTC 2017


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

            Bug ID: 99329
           Summary: GPU HANG: ecode 6:-1:0x00000000
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: sheepdestroyer at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 128828
  --> https://bugs.freedesktop.org/attachment.cgi?id=128828&action=edit
GPU crash dump

Bonjour,

I run Fedora 25 on a Lenovo X220 (i7 SandyBridge), my kernel is
4.9.0-1.fc26.x86_64.

I got the following lines in dmesg today :

janv. 09 10:10:07 sheepora kernel: [drm] GPU HANG: ecode 6:-1:0x00000000,
reason: Kicking stuck semaphore on render ring, action: continue
janv. 09 10:10:07 sheepora kernel: [drm] GPU hangs can indicate a bug anywhere
in the entire gfx stack, including userspace.
janv. 09 10:10:07 sheepora kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
janv. 09 10:10:07 sheepora kernel: [drm] drm/i915 developers can then reassign
to the right component if it's not a kernel issue.
janv. 09 10:10:07 sheepora kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
janv. 09 10:10:07 sheepora kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error

Crash dump attached to this issue.

Best regards.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170109/496ebc7e/attachment-0001.html>


More information about the intel-gfx-bugs mailing list