| Summary: | [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x374e000 ctx 0) at 0x374e1bc | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | egrumbach |
| Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
| Status: | RESOLVED INVALID | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | major | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
error state
dmesg output |
||
Created attachment 94606 [details]
dmesg output
This is Ubuntu 12.04 fully updated with kernel 3.13.5 (self compiled). I can happily provide any other input you might need. I can apply test patches and run tracing if that helps. I upgraded to Ubuntu 13.10 and with 3.13.5 it seems to work |
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 94605 [details] error state from dmesg: ----------- [ 97.988212] [drm] stuck on render ring [ 97.988221] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 97.988224] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 97.988226] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 97.988228] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 97.988230] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 97.992479] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x374e000 ctx 0) at 0x374e1bc [ 104.012485] [drm] stuck on render ring From error state: ----------------- IPEHR: 0x00000000