Summary: | [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [30991], reason: Hang on render ring, action: reset | ||
---|---|---|---|
Product: | Mesa | Reporter: | phaoost |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED DUPLICATE | 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: | SKL | i915 features: | GPU hang |
Attachments: | GPU crash dump |
Please test a new version of Mesa (12 or 13). Kernel: 4.8.0-1-amd64 Platform: Skylake (pci id: 0x1916, pci revision: 0x07, pci subsystem: 17aa:504a) Mesa: [Please confirm your mesa version] From this error dump, hung is happening in render ring batch with active head at 0xfd07a9b8, with 0x7b000005 (3DPRIMITIVE) as IPEHR. Batch extract (around 0xfd07a9b8): 0xfd07a998: 0x78090005: 3DSTATE_VERTEX_ELEMENTS 0xfd07a99c: 0x02000000: buffer 0: invalid, type 0x0000, src offset 0x0000 bytes 0xfd07a9a0: 0x22220000: (0.0, 0.0, 0.0, 0.0), dst offset 0x00 bytes 0xfd07a9a4: 0x02f60000: buffer 0: invalid, type 0x00f6, src offset 0x0000 bytes 0xfd07a9a8: 0x11230000: (X, Y, 0.0, 1.0), dst offset 0x00 bytes 0xfd07a9ac: 0x02f60004: buffer 0: invalid, type 0x00f6, src offset 0x0004 bytes 0xfd07a9b0: 0x11230000: (X, Y, 0.0, 1.0), dst offset 0x00 bytes Bad length 7 in (null), expected 6-6 0xfd07a9b4: 0x7b000005: 3DPRIMITIVE: fail sequential 0xfd07a9b8: 0x00000000: vertex count 0xfd07a9bc: 0x00000003: start vertex 0xfd07a9c0: 0x00000046: instance count 0xfd07a9c4: 0x00000001: start instance 0xfd07a9c8: 0x00000000: index bias 0xfd07a9cc: 0x00000000: MI_NOOP *** This bug has been marked as a duplicate of bug 98539 *** I have version 12. It shows the latest in repository for my OS (debian) |
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 127750 [details] GPU crash dump root@warp:~# dmesg |grep drm [ 11.680861] [drm] Initialized drm 1.1.0 20060810 [ 11.776123] [drm] Memory usable by graphics device = 4096M [ 11.776126] fb: switching to inteldrmfb from simple [ 11.776361] [drm] Replacing VGA console driver [ 11.781713] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 11.781714] [drm] Driver supports precise vblank timestamp query. [ 11.792582] [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26) [ 11.798532] [drm] GuC firmware load skipped [ 12.123848] [drm] Initialized i915 1.6.0 20160711 for 0000:00:02.0 on minor 0 [ 12.443995] fbcon: inteldrmfb (fb0) is primary device [ 13.824240] [drm] RC6 on [ 13.868256] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [49937.122420] [drm:gen8_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [87881.085685] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [30991], reason: Hang on render ring, action: reset [87881.085689] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [87881.085690] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [87881.085692] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [87881.085694] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [87881.085696] [drm] GPU crash dump saved to /sys/class/drm/card0/error [87881.085844] drm/i915: Resetting chip after gpu hang [87881.086180] [drm] GuC firmware load skipped [87883.098500] [drm] RC6 on