<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 - GPU hang when decoding MJPEGs via VA-API"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112198">112198</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>GPU hang when decoding MJPEGs via VA-API
</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>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>not set
</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>sgunderson@bigfoot.com
</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=145878" name="attach_145878" title="Dump of /sys/class/drm/card0/error">attachment 145878</a> <a href="attachment.cgi?id=145878&action=edit" title="Dump of /sys/class/drm/card0/error">[details]</a></span>
Dump of /sys/class/drm/card0/error
Hi,
I've got a desktop and a laptop (both Haswell) that use VA-API to decode JPEGs
as part of a larger video pipeline. This used to work fine around March-April
or so, but recently (November), I've started seeing GPU hangs on both. The
kernel says:
[515715.657023] DMAR: DRHD: handling fault status reg 3
[515715.657030] DMAR: [DMA Write] Request device [00:02.0] fault addr f72e5000
[fault reason 05] PTE Write access is not set
[515789.233234] DMAR: DRHD: handling fault status reg 3
[515789.233240] DMAR: [DMA Write] Request device [00:02.0] fault addr ed5df000
[fault reason 05] PTE Write access is not set
[515809.358568] i915 0000:00:02.0: Resetting chip for hang on rcs0
[515817.358404] i915 0000:00:02.0: Resetting chip for hang on rcs0
[515825.358428] i915 0000:00:02.0: Resetting chip for hang on rcs0
I rebooted with intel_iommu=igfx_off, and ran the program again. After ~10
minutes of running, it hung again, with:
[ 792.028358] i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe, in futatabi
[2319], hang on rcs0
[ 792.028361] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 792.028361] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 792.028362] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 792.028363] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 792.028364] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 792.028654] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 799.996625] i915 0000:00:02.0: Resetting chip for hang on rcs0
[ 807.996604] i915 0000:00:02.0: Resetting chip for hang on rcs0
If it's interesting, you can find the decoder source at
<a href="https://git.sesse.net/?p=nageru;a=blob;f=futatabi/vaapi_jpeg_decoder.cpp;h=d18a8735c11a23853ea6109b340c031dfee2a19c;hb=HEAD">https://git.sesse.net/?p=nageru;a=blob;f=futatabi/vaapi_jpeg_decoder.cpp;h=d18a8735c11a23853ea6109b340c031dfee2a19c;hb=HEAD</a>
.
I'll be filing a copy of /sys/class/drm/card0/error as an attachment.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>