[Bug 85327] New: GPU hang on HSW Celeron when doing 16 VA-API decodes and compositing
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Oct 22 04:30:54 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=85327
Bug ID: 85327
Summary: GPU hang on HSW Celeron when doing 16 VA-API decodes
and compositing
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: simon at farnz.org.uk
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
I'm using the kernel described in bug 83677 - basically #requests backported to
3.17.0. This may turn out to be a duplicate of that bug.
While it's now harder to get a GPU hang, I've had one with lots of VA-API video
decodes. dmesg gives:
[ 2327.073906] [drm] stuck on render ring
[ 2327.082270] [drm] GPU HANG: ecode 0:0x8fdffff8, in screen_manager [903],
reason: Ring hung, action: reset
[ 2327.082273] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 2327.082274] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 2327.082275] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 2327.082276] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 2327.082277] [drm] GPU crash dump saved to /sys/class/drm/card0/error
I'll attach the gzip'd error state.
--
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/20141022/bf21a393/attachment.html>
More information about the intel-gfx-bugs
mailing list