Summary: |
SandyBridge/IvyBridge: stuck on render ring / stuck on blitter ring |
Product: |
DRI
|
Reporter: |
Reindl Harald <h.reindl> |
Component: |
DRM/Intel | Assignee: |
Antti Koskipaa <antti.koskipaa> |
Status: |
CLOSED
DUPLICATE
|
QA Contact: |
Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: |
normal
|
|
|
Priority: |
medium
|
CC: |
intel-gfx-bugs, vmerlet
|
Version: |
unspecified | |
|
Hardware: |
Other | |
|
OS: |
All | |
|
Whiteboard: |
|
i915 platform:
|
|
i915 features:
|
|
Attachments: |
|
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.
Created attachment 94293 [details] content of /sys/class/drm/card0/error xorg-x11-drv-intel-2.21.15-5.fc20.x86_64 xorg-x11-server-Xorg-1.14.4-6.fc20.x86_64 that happens randomly in both, SnadyBridge and IvyBridge for a longer time with several kernel releases [16688.095803] [drm] stuck on render ring [16688.095810] [drm] stuck on blitter ring [16688.095812] [drm] GPU crash dump saved to /sys/class/drm/card0/error [16688.095823] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [16688.095824] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [16688.095825] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [16688.095826] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.