| Summary: | [BDW] GPU HANG: ecode 0:0x86cd3cff, in Civ5XP [24060], reason: Ring hung, action: reset | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | helenelizabethwilliamson |
| Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | BDW | i915 features: | GPU hang |
| Attachments: | GPU crash dump | ||
We seem to have neglected the bug a bit, apologies. There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring. (you may also collect and attach logs collected thanks to apitrace: http://apitrace.github.io/) In parallel, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang). Kernel: 3.13.0-62-generic Platform: Broadwell-U (pci id: 0x1616) Mesa: [Please confirm your mesa version] From this error dump, hung is happening in render ring batch with active head at 0x314c251c, with 0x79120000 (3DSTATE_PUSH_CONSTANT_ALLOC_VS) as IPEHR. Batch extract (around 0x314c251c): Bad length 7 in (null), expected 6-6 0x314c24ec: 0x7b000005: 3DPRIMITIVE: fail sequential 0x314c24f0: 0x00000104: vertex count 0x314c24f4: 0x00000816: start vertex 0x314c24f8: 0x00006a92: instance count 0x314c24fc: 0x00000001: start instance 0x314c2500: 0x00000000: index bias 0x314c2504: 0x00000000: MI_NOOP 0x314c2508: 0x78230000: 3D UNKNOWN: 3d_965 opcode = 0x7823 0x314c250c: 0x00005840: MI_NOOP 0x314c2510: 0x78210000: 3D UNKNOWN: 3d_965 opcode = 0x7821 0x314c2514: 0x00005440: MI_NOOP 0x314c2518: 0x79120000: 3DSTATE_PUSH_CONSTANT_ALLOC_VS 0x314c251c: 0x0000000a: dword 1 0x314c2520: 0x79150000: 3DSTATE_PUSH_CONSTANT_ALLOC_GS 0x314c2524: 0x000a000a: dword 1 0x314c2528: 0x79160000: 3DSTATE_PUSH_CONSTANT_ALLOC_PS 0x314c252c: 0x0014000c: dword 1 Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. If you can reproduce, please capture and upload an apitrace (https://github.com/apitrace/apitrace) so that we can easily reproduce as well. Dear Reporter, This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested. Thank you. |
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 117769 [details] GPU crash dump On launching Civ5 from Steam, the application crashes with the following in syslog: Aug 18 16:21:04 helen kernel: [ 5483.109470] [drm] stuck on render ring Aug 18 16:21:04 helen kernel: [ 5483.112619] [drm] GPU HANG: ecode 0:0x86cd3cff, in Civ5XP [24060], reason: Ring hung, action: reset Aug 18 16:21:04 helen kernel: [ 5483.112627] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Aug 18 16:21:04 helen kernel: [ 5483.112630] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel Aug 18 16:21:04 helen kernel: [ 5483.112633] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. Aug 18 16:21:04 helen kernel: [ 5483.112645] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. Aug 18 16:21:04 helen kernel: [ 5483.112651] [drm] GPU crash dump saved to /sys/class/drm/card0/error Aug 18 16:21:04 helen kernel: [ 5483.156383] Civ5XP[24062]: segfault at c ip 00000000f7306036 sp 00000000f470cbf0 error 4 in libpthread-2.19.so[f72fd000+18000]