[Bug 96499] New: GPU Hang

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jun 12 20:07:13 UTC 2016


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

            Bug ID: 96499
           Summary: GPU Hang
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: guenther at unix-ag.uni-kl.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 124487
  --> https://bugs.freedesktop.org/attachment.cgi?id=124487&action=edit
/sys/class/drm/card0/error

Hardware:
Zotac ZBOX CI323 Nano

User visible symptoms:
After boot up and graphical log in, I can work for about half a minute, and
then the screen freezes.

Switching to text mode with Ctrl+Alt+F2 is possible, but it takes a very long
time until the screen actually shows the text mode.  (Maybe one or two
minutes.)  In text mode things are fluent again.  Switching back to the logged
in session, it's still hanging.

This bug is reproducable on this machine and makes graphical log in infeasible.

Software:
Antergos Linux (Arch-based, rolling release).  Ran into the bug for the first
time on 2016-06-10, so the corresponding software update probably came in
roughly in that week.  (Not using the machine every day.)

Kernel: Linux limbo 4.6.2-1-ARCH #1 SMP PREEMPT Wed Jun 8 08:40:59 CEST 2016
x86_64 GNU/Linux

from dmesg:

[  195.338739] [drm] stuck on render ring
[  195.344643] [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [710], reason:
Ring hung, action: reset
[  195.344648] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[  195.344650] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[  195.344652] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[  195.344654] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[  195.344656] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  195.348200] drm/i915: Resetting chip after gpu hang
[  201.338938] [drm] stuck on blitter ring
[  201.345565] [drm] GPU HANG: ecode 8:1:0xfffffffe, in Xorg [710], reason:
Ring hung, action: reset
[  201.346064] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast,
banning!
[  201.348448] drm/i915: Resetting chip after gpu hang

/sys/class/drm/card0/error is attached to the bug.

*After* the actual screen freeze, there is a longer list of stack traces in
dmesg.
(vblank wait timeout, WARN_ON(!lret), ...)

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


More information about the intel-gfx-bugs mailing list