<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [i965] "stuck on render ring" during video playback"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90272">90272</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[i965] "stuck on render ring" during video playback
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>blocker
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>bedin.aleksei@yandex.ru
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=115502" name="attach_115502" title="/sys/class/drm/card0/error (GPU crash dump)">attachment 115502</a> <a href="attachment.cgi?id=115502&action=edit" title="/sys/class/drm/card0/error (GPU crash dump)">[details]</a></span>
/sys/class/drm/card0/error (GPU crash dump)
Appeared after turning on a va-api hardware acceleration.
Dmesg:
[ 904.206843] [drm] stuck on render ring
[ 904.206866] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 904.206872] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 904.206876] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 904.206896] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 904.206902] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
vainfo:
libva info: VA-API version 0.35.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.35 (libva 1.3.0)
vainfo: Driver version: Intel i965 driver - 1.3.0
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
hardware:
VGA compatible controller: Intel Corporation 2nd Generation Core Processor
Family Integrated Graphics Controller (rev 09)
(Intel HD3000 SandyBridge integrated)
Linux Mint 17.1, linux kernel 3.13.0-37, XOrg 1:7.7, Mesa 10.1.3,
libva-intel-vaapi-driver 1.3.0, xserver-xorg-video-intel 2:2.99.910
Ask for additional details if needed.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>