Bug 98291 - [IVB] GPU hang in Weston when coming back from suspend on 4.8.1 on ArchLinux
Summary: [IVB] GPU hang in Weston when coming back from suspend on 4.8.1 on ArchLinux
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: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-17 12:34 UTC by Link Mauve
Modified: 2017-02-10 22:38 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error of the hang (29.75 KB, application/x-xz)
2016-10-17 12:34 UTC, Link Mauve
Details

Description Link Mauve 2016-10-17 12:34:20 UTC
Created attachment 127352 [details]
/sys/class/drm/card0/error of the hang
Comment 1 yann 2016-10-17 14:26:41 UTC
There are constant improvements pushed in Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.

In parallel, assigning to Mesa product.

Kernel: 4.8.1-1-ARCH
Platform: Ivybridge (pci id: 0x0166, PCI Revision: 0x09, PCI Subsystem: 17aa:21fa)
Mesa: [Please confirm your mesa version]

From this error dump, hung is happening in render ring batch with active head at 0x7ede8224, with 0x79000002 (3DSTATE_DRAWING_RECTANGLE) as IPEHR.

We can note also an error
ERROR: 0x00000101
    TLB page fault error (GTT entry not valid)
    Cacheline containing a PD was marked as invalid
(and on render ring we see: Unloaded PD Fault (PPGTT))

Batch extract (around 0x7ede8224):

0x7ede81f8:      0x78200006: 3DSTATE_PS
0x7ede81fc:      0x00000340:    dword 1
0x7ede8200:      0x08080000:    dword 2
0x7ede8204:      0x00000000:    dword 3
0x7ede8208:      0xab000c03:    dword 4
0x7ede820c:      0x00040006:    dword 5
0x7ede8210:      0x00000000:    dword 6
0x7ede8214:      0x000003c0:    dword 7
0x7ede8218:      0x780f0000: 3DSTATE_SCISSOR_POINTERS
0x7ede821c:      0x00007dc0:    scissor rect offset
0x7ede8220:      0x79000002: 3DSTATE_DRAWING_RECTANGLE
0x7ede8224:      0x00000000:    top left: 0,0
0x7ede8228:      0x059f09ff:    bottom right: 2559,1439
0x7ede822c:      0x00000000:    origin: 0,0
0x7ede8230:      0x78080003: 3DSTATE_VERTEX_BUFFERS
0x7ede8234:      0x00014010:    buffer 0: sequential, pitch 16b
0x7ede8238:      0x7edd8000:    buffer address
0x7ede823c:      0x7edd8041:    max index
0x7ede8240:      0x00000000:    mbz
Comment 2 Link Mauve 2016-10-17 16:17:04 UTC
I was indeed using a somewhat-old Mesa, master commit 74b02a744913ffaaf409feb0df30aaa92188e250 from 2016-09-27.

I will also upgrade to the latest linux-git if it can help.
Comment 3 Matt Turner 2016-11-04 00:40:01 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:51 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.