Summary: | [APL] GPU hang after resume while executing - gem_softpin@noreloc-s4 | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Jairo Miramontes <jairo.daniel.miramontes.caton> | ||||
Component: | DRM/Intel | Assignee: | Jairo Miramontes <jairo.daniel.miramontes.caton> | ||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | DRI git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | BXT | i915 features: | GPU hang, power/suspend-resume | ||||
Attachments: |
|
Description
Jairo Miramontes
2016-07-22 22:23:59 UTC
From this error dump, in render ring HEAD: 0x00200d38 head = 0x00000d38, wraps = 1 TAIL: 0x00000d38 ACTHD: 0x00000000 00200d38 at ring: 0x00000000 IPEIR: 0x00000000 IPEHR: 0x00000000 ... seqno: 0x000000b0 last_seqno: 0x000000b1 and in the trace render ring --- 1 requests seqno 0x000000b1, emitted 4294963764, tail 0x00000d18 render ring --- 1 waiters seqno 0x000000b1 for gem_softpin [1548] ring buffer (render ring) at 0x00000000_00912000; HEAD points to: 0x00000000_00912d38 0x00912000: 0x383b6b0a: UNKNOWN 0x00912004: 0x789b6dba: 3D UNKNOWN: 3d_965 opcode = 0x789b 0x00912008: 0x482b6b2a: 2D UNKNOWN 0x0091200c: 0x6b2e4d2a: 3D UNKNOWN: 3d_965 opcode = 0x6b2e Could it be a synchronization issue seqno is gt last_seqno in render ring? Jairo, can you replay with latest kernel and attached dmesg and new dump if it occurs again? Jairo, ping (see comments above: please try to reproduce and attached new logs if it occurs again) (In reply to yann from comment #2) > Jairo, ping (see comments above: please try to reproduce and attached new > logs if it occurs again) Closing this bug as fixed (see reference also to closed bug 96526). If it occurs again with latest kernel & mesa, please reopen and attach both kernel log & gpu crash dump. |
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.