Bug 96515

Summary: [SKL] GPU HANG: ecode 9:0:0x87f9ffff, in hoi4 [4578], reason: Ring hung, action: reset
Product: Mesa Reporter: sjh
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED INVALID QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium CC: gary.c.wang, intel-gfx-bugs, mboquien
Version: 11.0   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: SKL i915 features: GPU hang
Attachments: /sys/class/drm/card0/error

Description sjh 2016-06-13 22:16:29 UTC 
Running the game "Hearts of Iron IV" (hoi4) I consistently get a hang, and often a crash once the game gets going and there are many units moving on the screen.

Crash message: (full text in attachment)

[  246.873851] [drm] stuck on render ring
[  246.875281] [drm] GPU HANG: ecode 9:0:0x87f9ffff, in hoi4 [4578], reason: Rin
g hung, action: reset
[  246.875285] [drm] GPU hangs can indicate a bug anywhere in the entire gfx sta
ck, including userspace.
[  246.875287] [drm] Please file a _new_ bug report on bugs.freedesktop.org agai
nst DRI -> DRM/Intel
[  246.875289] [drm] drm/i915 developers can then reassign to the right componen
t if it's not a kernel issue.
[  246.875291] [drm] The gpu crash dump is required to analyze gpu hangs, so ple
ase always attach it.
[  246.875294] [drm] GPU crash dump saved to /sys/class/drm/card0/error



System info:

System:    Host: sjh-glaptop2 Kernel: 4.2.0-36-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: Cinnamon 2.6.13  Distro: Ubuntu 14.04 trusty
Machine:   System: LENOVO product: 20FCS12V03 version: ThinkPad X1 Carbon 4th
           Mobo: LENOVO model: 20FCS12V03 Bios: LENOVO version: N1FET38W (1.12 ) date: 03/30/2016
CPU:       Dual core Intel Core i7-6600U CPU (-HT-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11232.3 
           Clock Speeds: 1: 499.515 MHz 2: 500.062 MHz 3: 499.953 MHz 4: 1833.671 MHz
Graphics:  Card: Intel Sky Lake Integrated Graphics bus-ID: 00:02.0 
           X.Org: 1.17.2 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz 
           GLX Renderer: Mesa DRI Intel Skylake ULT GT2 GLX Version: 3.0 Mesa 11.0.2 Direct Rendering: Yes
Audio:     Card: Intel Device 9d70 driver: snd_hda_intel bus-ID: 00:1f.3 Sound: ALSA ver: k4.2.0-36-generic


I have not tried a nightly kernel, but I may have time this weekend if you think that will help.
Comment 1 sjh 2016-06-13 22:17:31 UTC 
Created attachment 124517 [details]
/sys/class/drm/card0/error
Comment 2 yann 2016-09-01 12:16:03 UTC 
Assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head
at 0xf6135698, with 0x78260000 (3DSTATE_BINDING_TABLE_POINTERS_VS) as IPEHR.

Batch extract (around 0xf6135698):

0xf6135664:      0x78170009: 3D UNKNOWN: 3d_965 opcode = 0x7817
0xf6135668:      0x00000000: MI_NOOP
0xf613566c:      0x00000001: MI_NOOP
0xf6135670:      0x00000000: MI_NOOP
0xf6135674:      0x00000000: MI_NOOP
0xf6135678:      0x00000000: MI_NOOP
0xf613567c:      0x00000000: MI_NOOP
0xf6135680:      0xf6138f60: UNKNOWN
0xf6135684:      0x00000000: MI_NOOP
0xf6135688:      0x00000000: MI_NOOP
0xf613568c:      0x00000000: MI_NOOP
0xf6135690:      0x78260000: 3DSTATE_BINDING_TABLE_POINTERS_VS
0xf6135694:      0x00000000:    dword 1
0xf6135698:      0x782a0000: 3DSTATE_BINDING_TABLE_POINTERS_PS
0xf613569c:      0x00005ee0:    dword 1
0xf61356a0:      0x782f0000: 3DSTATE_SAMPLER_STATE_POINTERS_PS
Comment 3 Matt Turner 2016-11-04 00:41:49 UTC 
Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 4 Annie 2017-02-10 22:38:53 UTC 
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.