[Bug 77043] New: [drm] stuck on render ring

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 77043
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [drm] stuck on render ring
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: shuber at sthu.org
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Intel
           Product: DRI

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

By filing this bug, I follow the instructions below:

[26922.904349] [drm] stuck on render ring
[26922.904350] [drm] stuck on blitter ring
[26922.904351] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[26922.904352] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[26922.904352] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[26922.904352] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[26922.904352] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.

I was running a program of myself that uses vtk-5.10.1 to visualize data. I am
running a Gentoo linux on a Thinkpad X220 with

  sys-kernel/gentoo-sources-3.13.7
  x11-drivers/xf86-video-intel-2.99.910
  media-libs/mesa-10.1.0
  x11-libs/libdrm-2.4.52
  x11-base/xorg-server-1.15.0

installed. I observed these hangs over different kernel versions and versions
of xf86-video-intel.

-- 
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: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140404/857d78b2/attachment.html>