[Bug 75268] New: i915 hangs during video output/decoding and ends up stuck on render ring

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Feb 20 08:34:46 PST 2014


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

          Priority: medium
            Bug ID: 75268
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: i915 hangs during video output/decoding and ends up
                    stuck on render ring
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: winrootkit at gmail.com
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Intel
           Product: DRI

I encounter this error when playing Video (h264) via VLC, mplayer and XBMC but
not all the time

The driver hangs and does not recover, only a full reboot fixes it, the kernel
module cannot be unloaded and even restarting the xserver does not help.

The CPU+GPU is a first gen. Intel(R) Core(TM) i3 CPU U 330.


Feb 20 17:14:13 doomtravel kernel: [   83.887666] [drm] stuck on render ring
Feb 20 17:14:13 doomtravel kernel: [   83.887682] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Feb 20 17:14:13 doomtravel kernel: [   83.887687] [drm] GPU hangs can indicate
a bug anywhere in the entire gfx stack, including userspace.
Feb 20 17:14:13 doomtravel kernel: [   83.887691] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Feb 20 17:14:13 doomtravel kernel: [   83.887694] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Feb 20 17:14:13 doomtravel kernel: [   83.887698] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Feb 20 17:14:17 doomtravel kernel: [   87.848297] [drm] stuck on render ring
Feb 20 17:14:21 doomtravel kernel: [   91.868850] [drm] stuck on render ring
Feb 20 17:14:25 doomtravel kernel: [   95.865461] [drm] stuck on render ring
Feb 20 17:14:29 doomtravel kernel: [   99.862068] [drm] stuck on render ring
Feb 20 17:14:33 doomtravel kernel: [  103.834699] [drm] stuck on render ring
Feb 20 17:14:39 doomtravel kernel: [  109.829469] [drm] stuck on render ring
Feb 20 17:14:44 doomtravel kernel: [  114.825177] [drm] stuck on render ring
Feb 20 17:14:48 doomtravel kernel: [  118.821836] [drm] stuck on render ring
Feb 20 17:14:52 doomtravel kernel: [  122.818401] [drm] stuck on render ring
Feb 20 17:14:56 doomtravel kernel: [  126.838955] [drm] stuck on render ring
Feb 20 17:15:00 doomtravel kernel: [  130.823596] [drm] stuck on render ring
Feb 20 17:15:04 doomtravel kernel: [  134.832165] [drm] stuck on render ring
Feb 20 17:15:08 doomtravel kernel: [  138.828685] [drm] stuck on render ring
Feb 20 17:15:12 doomtravel kernel: [  142.813311] [drm] stuck on render ring
Feb 20 17:15:16 doomtravel kernel: [  146.809885] [drm] stuck on render ring
Feb 20 17:15:20 doomtravel kernel: [  150.818437] [drm] stuck on render ring
Feb 20 17:15:24 doomtravel kernel: [  154.826959] [drm] stuck on render ring
Feb 20 17:15:28 doomtravel kernel: [  158.823599] [drm] stuck on render ring
Feb 20 17:15:32 doomtravel kernel: [  162.784218] [drm] stuck on render ring
Feb 20 17:15:40 doomtravel kernel: [  170.813366] [drm] stuck on render ring
Feb 20 17:15:44 doomtravel kernel: [  174.809930] [drm] stuck on render ring
Feb 20 17:15:48 doomtravel kernel: [  178.806509] [drm] stuck on render ring
Feb 20 17:15:52 doomtravel kernel: [  182.803110] [drm] stuck on render ring
Feb 20 17:15:56 doomtravel kernel: [  186.799676] [drm] stuck on render ring
Feb 20 17:16:00 doomtravel kernel: [  190.796227] [drm] stuck on render ring
Feb 20 17:16:04 doomtravel kernel: [  194.780817] [drm] stuck on render ring
Feb 20 17:16:08 doomtravel kernel: [  198.765399] [drm] stuck on render ring
Feb 20 17:16:12 doomtravel kernel: [  202.778033] [drm] stuck on render ring
Feb 20 17:16:16 doomtravel kernel: [  206.770633] [drm] stuck on render ring
Feb 20 17:16:20 doomtravel kernel: [  210.743204] [drm] stuck on render ring
Feb 20 17:16:24 doomtravel kernel: [  214.739760] [drm] stuck on render ring
Feb 20 17:16:28 doomtravel kernel: [  218.772333] [drm] stuck on render ring
Feb 20 17:16:32 doomtravel kernel: [  222.744923] [drm] stuck on render ring
Feb 20 17:16:36 doomtravel kernel: [  226.745531] [drm] stuck on render ring
Feb 20 17:16:40 doomtravel kernel: [  230.750145] [drm] stuck on render ring
Feb 20 17:16:44 doomtravel kernel: [  234.746692] [drm] stuck on render ring
Feb 20 17:16:48 doomtravel kernel: [  238.731290] [drm] stuck on render ring
Feb 20 17:16:52 doomtravel kernel: [  242.739794] [drm] stuck on render ring
Feb 20 17:16:56 doomtravel kernel: [  246.736407] [drm] stuck on render ring
Feb 20 17:17:00 doomtravel kernel: [  250.721014] [drm] stuck on render ring

-- 
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/20140220/4a0e1e20/attachment.html>


More information about the intel-gfx-bugs mailing list