Bug 95515 - [ILK] GPU HANG: ecode 5:0:0xb5cefffc, in compiz [3365], reason: Ring hung, action: reset
Summary: [ILK] GPU HANG: ecode 5:0:0xb5cefffc, in compiz [3365], reason: Ring hung, ac...
Status: CLOSED FIXED
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-05-21 03:34 UTC by Sanjeev Gupta
Modified: 2017-01-30 10:01 UTC (History)
2 users (show)

See Also:
i915 platform: ILK
i915 features: GPU hang, power/suspend-resume


Attachments
dmesg from boot (20.76 KB, application/x-bzip)
2016-05-21 03:34 UTC, Sanjeev Gupta
Details
/sys/class/drm/card0/error (142.68 KB, application/x-bzip)
2016-05-21 03:35 UTC, Sanjeev Gupta
Details

Description Sanjeev Gupta 2016-05-21 03:34:40 UTC
Created attachment 123953 [details]
dmesg from boot

Upon unsuspend, (but only once in a dozen times), the X login display freezes.  Ctrl-Alt-F1 also does not work.

After 10 to 15 secs, display continues normally.

In the attached logs, freeze was at 50722
Comment 1 Sanjeev Gupta 2016-05-21 03:35:34 UTC
Created attachment 123954 [details]
/sys/class/drm/card0/error
Comment 2 yann 2016-09-01 13:53:38 UTC
Assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head
at 0x06133130, with 0x79010003 (3DSTATE_CONSTANT_COLOR) as IPEHR.

Batch extract (around 0x06133130):

0x061330fc:      0x7b001004: 3DPRIMITIVE: tri list sequential
0x06133100:      0x00000006:    vertex count
0x06133104:      0x00000000:    start vertex
0x06133108:      0x00000001:    instance count
0x0613310c:      0x00000000:    start instance
0x06133110:      0x00000000:    index bias
0x06133114:      0x78010004: 3DSTATE_BINDING_TABLE_POINTERS
0x06133118:      0x00000000:    VS binding table
0x0613311c:      0x00000000:    GS binding table
0x06133120:      0x00000000:    Clip binding table
0x06133124:      0x00000000:    SF binding table
0x06133128:      0x00007da0:    WM binding table
0x0613312c:      0x79010003: 3DSTATE_CONSTANT_COLOR
0x06133130:      0x00000000:    dword 1
0x06133134:      0x00000000:    dword 2
0x06133138:      0x00000000:    dword 3
0x0613313c:      0x00000000:    dword 4
0x06133140:      0x02000000: MI_FLUSH
0x06133144:      0x78000005: 3DSTATE_PIPELINED_POINTERS
0x06133148:      0x0613ace0:    VS state
0x0613314c:      0x00000000:    GS state
0x06133150:      0x0613ae41:    Clip state
0x06133154:      0x0613ad00:    SF state
0x06133158:      0x0613ad40:    WM state
0x0613315c:      0x0613ae00:    CC state
Comment 3 yann 2016-11-04 15:14:25 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 yann 2017-01-30 10:01:24 UTC
(In reply to yann from comment #3)
> Please test a new version of Mesa (12 or 13) and mark as REOPENED
> if you can reproduce and RESOLVED/* if you cannot reproduce.


Timeout, so assuming this is fixed by now. If this is not the case, please re-test with latest kernel, xf86-video-intel & Mesa to see if this issue is still occurring since there were improvements pushed in these components that will benefit to your system, and fill a new bug.


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.