Bug 94064 - [SKL] GPU hang ecode 9:0:0x85dffffb, in plasmashell
Summary: [SKL] GPU hang ecode 9:0:0x85dffffb, in plasmashell
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
: 94082 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-02-09 15:27 UTC by Markus Schauler
Modified: 2017-02-10 22:39 UTC (History)
2 users (show)

See Also:
i915 platform: SKL
i915 features: GPU hang


Attachments
GPU crash dump (40.86 KB, text/plain)
2016-02-09 15:27 UTC, Markus Schauler
Details

Description Markus Schauler 2016-02-09 15:27:39 UTC
Created attachment 121622 [details]
GPU crash dump

In KDE plasmashell, opening the K-Application menue hangs the GPU, crashes plasmashell

Error is :
Feb 09 16:17:07 linux.suse kernel: [drm] stuck on render ring
Feb 09 16:17:07 linux.suse kernel: [drm] GPU HANG: ecode 9:0:0x85dffffb, in plasmashell [1676], reason: Ring hung, action
Feb 09 16:17:07 linux.suse kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspa
Feb 09 16:17:07 linux.suse kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Feb 09 16:17:07 linux.suse kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kerne
Feb 09 16:17:07 linux.suse kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Feb 09 16:17:07 linux.suse kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Feb 09 16:17:07 linux.suse kernel: drm/i915: Resetting chip after gpu hang
Feb 09 16:17:09 linux.suse kernel: [drm] RC6 on
Feb 09 16:17:13 linux.suse kernel: [drm] stuck on render ring
Feb 09 16:17:13 linux.suse kernel: [drm] GPU HANG: ecode 9:0:0x85dfffff, in plasmashell [1676], reason: Ring hung, action
Feb 09 16:17:13 linux.suse kernel: drm/i915: Resetting chip after gpu hang
Feb 09 16:17:14 linux.suse kernel: fuse init (API version 7.23)
Feb 09 16:17:14 linux.suse kernel: [drm] RC6 on


Hardware: Intel NUC6i5
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 78
model name      : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz
stepping        : 3
microcode       : 0x6a
cpu MHz         : 645.468
cache size      : 4096 KB

kernel: 4.4.0-8.g9f68b90-default
Distribution: opensuse leap
KDE/Plasmashell  5.4.3
Comment 1 yann 2016-05-18 15:28:38 UTC
*** Bug 94082 has been marked as a duplicate of this bug. ***
Comment 2 yann 2016-09-12 12:47:20 UTC
There were workarounds on SKL pushed in kernel, so please re-test with latest kernel to see if it has some benefits on that work.

In parallel, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang).

From this error dump, hung is happening in render ring batch with active head at 0xffff86a8, with 0x7a000004 (PIPE_CONTROL) as IPEHR.

Batch extract (around 0xffff86a8):

0xffff8658:      0x784e0002: 3D UNKNOWN: 3d_965 opcode = 0x784e
0xffff865c:      0x00000042: MI_NOOP
0xffff8660:      0x00000000: MI_NOOP
0xffff8664:      0x00000000: MI_NOOP
0xffff8668:      0x78140000: 3D UNKNOWN: 3d_965 opcode = 0x7814
0xffff866c:      0x80000844: UNKNOWN
0xffff8670:      0x780f0000: 3DSTATE_SCISSOR_POINTERS
0xffff8674:      0x00007c20:    scissor rect offset
Bad count in PIPE_CONTROL
0xffff8678:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC write flush, no inst flush
0xffff867c:      0x00000000:    destination address
0xffff8680:      0x00000000:    immediate dword low
0xffff8684:      0x00000000:    immediate dword high
Bad count in PIPE_CONTROL
0xffff8690:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC write flush, no inst flush
0xffff8694:      0x00101c11:    destination address
0xffff8698:      0x00000000:    immediate dword low
0xffff869c:      0x00000000:    immediate dword high
Bad count in PIPE_CONTROL
0xffff86a8:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC write flush, no inst flush
0xffff86ac:      0x00002000:    destination address
0xffff86b0:      0x00000000:    immediate dword low
0xffff86b4:      0x00000000:    immediate dword high
Comment 3 Matt Turner 2016-11-04 00:19:08 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:39:10 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.