Summary: | [HSW] GPU error state gathered while decoding 4K video with VA-API and displaying via an OpenGL compositor | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Simon Farnsworth <simon> | ||||
Component: | DRM/Intel | Assignee: | Mika Kuoppala <mika.kuoppala> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | unspecified | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Simon Farnsworth
2014-07-02 11:04:41 UTC
Created attachment 102128 [details]
Compressed error state
This is the error state; dmesg to go with it says:
[ 2964.222067] [drm] stuck on render ring
[ 2964.222090] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2964.222102] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 2964.222114] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 2964.222119] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 2964.222125] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
|
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.