[Bug 78751] New: [IVB GT1] GPU hang

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu May 15 11:01:47 PDT 2014


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

          Priority: medium
            Bug ID: 78751
                CC: bb at knacknuss.de
          Assignee: kenneth at whitecape.org
           Summary: [IVB GT1] GPU hang
        QA Contact: intel-3d-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: kenneth at whitecape.org
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/DRI/i965
           Product: Mesa

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

+++ Split separate issue out of Bug #77207.  Actual reporter is Benjamin
Baumgärtner <bb at knacknuss.de> +++

I upgraded my Ubuntu trusty to today's state of the xorg-edgers PPA:

xserver-xorg-core    2:1.15.1-0ubuntu2
xserver-xorg-video-intel   
2:2.99.911+git20140507.18416b51-0ubuntu0ricotz~trusty
libegl1-mesa:amd64    10.3.0~git20140514.8a9f5ecd-0ubuntu0sarvatt~trusty
libgl1-mesa-dri:amd64    10.3.0~git20140514.8a9f5ecd-0ubuntu0sarvatt~trusty

$ glxinfo | grep Mesa
client glx vendor string: Mesa Project and SGI
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.0-devel
OpenGL version string: 3.0 Mesa 10.3.0-devel

I'm still experiencing problems. Garbage screen output disappeared, but the
screen is stuck for 5-20 secs every 1-3 minutes.

The kernel ring buffer says:
[  333.738942] [drm] stuck on render ring
[  333.738951] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  333.738952] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[  333.738953] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[  333.738954] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[  333.738955] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[  339.736311] [drm] stuck on render ring
[  339.736354] [drm:i915_context_is_banned] *ERROR* context hanging too fast,
declaring banned!
[  348.720483] [drm] stuck on render ring
[  354.729941] [drm] stuck on render ring
[  360.727429] [drm] stuck on render ring
[  360.727558] [drm:i915_context_is_banned] *ERROR* context hanging too fast,
declaring banned!
[  439.102608] init: tty1 main process ended, respawning
[  468.674648] [drm] stuck on render ring
[  647.707294] [drm] stuck on render ring
[  716.739191] [drm] stuck on render ring

So I'm still having trouble, even with xserver 1.15.1 and a recent mesa
version.

Regards,
Benjamin

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20140515/0ea8ef19/attachment.html>


More information about the intel-3d-bugs mailing list