Bug 93960 - [HSW] GPU HANG: ecode 7:0:0x87df7c12, in Xorg [1199], reason: Ring hung, action: reset
Summary: [HSW] GPU HANG: ecode 7:0:0x87df7c12, in Xorg [1199], reason: Ring hung, acti...
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 normal
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-02 04:59 UTC by Douglas Bagnall
Modified: 2017-02-10 22:39 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (3.32 MB, text/plain)
2016-02-02 04:59 UTC, Douglas Bagnall
Details

Description Douglas Bagnall 2016-02-02 04:59:35 UTC
Created attachment 121451 [details]
/sys/class/drm/card0/error

This is Ubuntu 15.10 with xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4, kernel 4.2.0-25-generic.
The GPU calls itself "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller".

dmesg:

[  103.762219] [drm] stuck on render ring
[  103.764101] [drm] GPU HANG: ecode 7:0:0x87df7c12, in Xorg [1199], reason: Ring hung, action: reset
[  103.764103] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  103.764103] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  103.764104] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  103.764104] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  103.764105] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  103.766155] drm/i915: Resetting chip after gpu hang

gdm and xdm can't start X but lightdm can.
Comment 1 yann 2016-09-13 14:07:02 UTC
Assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head at 0x0380c29c, with 0x78080003 (3DSTATE_VERTEX_BUFFERS) as IPEHR.

Batch extract (around 0x0380c29c):

0x0380c27c:      0x7b000005: 3DPRIMITIVE:
0x0380c280:      0x0000000f:    rect list sequential
0x0380c284:      0x000069d8:    vertex count
0x0380c288:      0x00001626:    start vertex
0x0380c28c:      0x00000001:    instance count
0x0380c290:      0x00000000:    start instance
0x0380c294:      0x00000000:    index bias
0x0380c298:      0x78080003: 3DSTATE_VERTEX_BUFFERS
0x0380c29c:      0x00004008:    buffer 0: sequential, pitch 8b
0x0380c2a0:      0x0385c000:    buffer address
0x0380c2a4:      0xffffffff:    max index
0x0380c2a8:      0x00000000:    mbz
0x0380c2ac:      0x7b000005: 3DPRIMITIVE:
0x0380c2b0:      0x0000000f:    rect list sequential
0x0380c2b4:      0x00000ef7:    vertex count
0x0380c2b8:      0x00000000:    start vertex
0x0380c2bc:      0x00000001:    instance count
0x0380c2c0:      0x00000000:    start instance
0x0380c2c4:      0x00000000:    index bias

Moreover interestingly we have an error also in the dump:
ERROR: 0x00000105
    TLB page fault error (GTT entry not valid)
    Invalid page directory entry error
    Cacheline containing a PD was marked as invalid
Comment 2 yann 2016-11-04 15:34:31 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 3 Annie 2017-02-10 22:39:00 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.