Summary: | [IVB] GPU HANG: ecode 7:0:0x85fffffa, in X [16159], reason: Hang on render ring, action: reset (after resume from hibernation on ThinkPad x230) | ||
---|---|---|---|
Product: | Mesa | Reporter: | Eugene A. Shatokhin <eugene.shatokhin> |
Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | 12.0 | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | IVB | i915 features: | GPU hang |
Attachments: | Gzipped contents of /sys/class/drm/card0/error |
Description
Eugene A. Shatokhin
2016-11-13 13:57:32 UTC
If needed, I can test the patches to the kernel or X11 server. However, I have to stick to X11 server 1.17.4 for another month or two, so I cannot update it as a whole. Still, I can try patches to it. There were improvements pushed in kernel and Mesa (13)that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring: mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. In parallel, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang). Kernel: 4.4.0-rc6-mainline Platform: Ivybridge (pci id: 0x0166, pci revision: 0x09, pci subsystem: 17aa:21fa) Mesa: 12.0.4 From this error dump, hung is happening in render ring batch with active head at 0x00dcf294, with 0x7a000003 (PIPE_CONTROL) as IPEHR. We can note also: ERROR: 0x00000101 TLB page fault error (GTT entry not valid) Cacheline containing a PD was marked as invalid and in render batch: Unloaded PD Fault (PPGTT) Batch extract (around 0x00dcf294): 0x00dcf264: 0x7b000005: 3DPRIMITIVE: 0x00dcf268: 0x00000104: tri list random 0x00dcf26c: 0x00000006: vertex count 0x00dcf270: 0x00000000: start vertex 0x00dcf274: 0x00000001: instance count 0x00dcf278: 0x00000000: start instance 0x00dcf27c: 0x00000000: index bias 0x00dcf280: 0x7a000003: PIPE_CONTROL 0x00dcf284: 0x00101001: no write, cs stall, render target cache flush, depth cache flush, 0x00dcf288: 0x00000000: destination address 0x00dcf28c: 0x00000000: immediate dword low 0x00dcf290: 0x00000000: immediate dword high 0x00dcf294: 0x7a000003: PIPE_CONTROL 0x00dcf298: 0x00000408: no write, texture cache invalidate, constant cache invalidate, 0x00dcf29c: 0x00000000: destination address 0x00dcf2a0: 0x00000000: immediate dword low 0x00dcf2a4: 0x00000000: immediate dword high 0x00dcf2a8: 0x78210000: 3DSTATE_VIEWPORT_STATE_POINTERS_SF_CLIP 0x00dcf2ac: 0x00007dc0: pointer to SF_CLIP viewport (In reply to yann from comment #2) Thanks for a quick reply! > There were improvements pushed in kernel and Mesa (13)that will benefit to > your system, so please re-test with latest kernel & Mesa to see if this > issue is still occurring: mark as REOPENED if you can reproduce and > RESOLVED/* if you cannot reproduce. Yes, I will re-test it with Mesa 13.x and the mainline kernel 4.9 (or, do you suggest another git tree?), hopefully, later this week. > > Kernel: 4.4.0-rc6-mainline It is 4.8.7 on that system, actually. > Platform: Ivybridge (pci id: 0x0166, pci revision: 0x09, pci subsystem: > 17aa:21fa) > Mesa: 12.0.4 (In reply to Eugene A. Shatokhin from comment #3) > (In reply to yann from comment #2) > > Thanks for a quick reply! > > > There were improvements pushed in kernel and Mesa (13)that will benefit to > > your system, so please re-test with latest kernel & Mesa to see if this > > issue is still occurring: mark as REOPENED if you can reproduce and > > RESOLVED/* if you cannot reproduce. > > Yes, I will re-test it with Mesa 13.x and the mainline kernel 4.9 (or, do > you suggest another git tree?), hopefully, later this week. Thanks Eugene, current mainline is fine :) > > > > > Kernel: 4.4.0-rc6-mainline > It is 4.8.7 on that system, actually. > You are right, bad copy'n paste :^(. To be accurate this is : 4.8.7-nrj-desktop-1rosa-x86_64 I have updated Mesa to 13.0.1 and libdrm to 2.4.73 while keeping the kernel the same for now. No problem after resume so far. Will monitor the system for a couple days, let us see if the issue shows up again. OK, several hibernate-resume cycles in 2 days - the problem haven't shown up. Let us assume Mesa 13.0.1 and/or libdrm update fixed it. |
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.