Created attachment 135338 [details] crashdump file [92117.407928] [drm] GPU HANG: ecode 9:0:0x8fdfbffe, in code [5307], reason: Hang on rcs0, action: reset [92117.407932] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [92117.407934] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [92117.407936] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [92117.407937] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [92117.407939] [drm] GPU crash dump saved to /sys/class/drm/card0/error [92117.408021] drm/i915: Resetting chip after gpu hang [92118.114873] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout [92118.114906] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5
This can be reproduced when the computer stays idle for, say, 30 minutes or so.
(In reply to mcku from comment #1) > This can be reproduced when the computer stays idle for, say, 30 minutes or > so. If reproducible, could you please try to get a dmesg or/and kern.log with debug information: drm.debug=0x1e log_bug_len=2M parameters on grub. Also could you try: commit 1d033beb20d6d5885587a02a393b6598d766a382 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Oct 31 10:36:07 2017 +0000 drm/i915: Check incoming alignment for unfenced buffers (on i915gm) From error state: render command stream: ... seqno: 0x00665f5d last_seqno: 0x00665f5f waiting: yes ring->head: 0x00000000 ring->tail: 0x00000080 hangcheck stall: yes hangcheck action: dead hangcheck action timestamp: 4322511296, 303163 ms ago ELSP[0]: pid 5307, ban score 0, seqno 1e:00665f5e, emitted 305276ms ago, head 00000000, tail 00000080 ELSP[1]: pid 5307, ban score 0, seqno 1b:00665f5f, emitted 305180ms ago, head 00000000, tail 00000078 Active context: code[5307] user_handle 5 hw_id 30, ban score 0 guilty 0 active 0 ... 00000000_00880000 8388608 7e 00 [ 00 00 00 00 00 ] 00 X dirty uncached (fence: 5)
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
(In reply to Jani Saarinen from comment #3) The buggy environment has changed a lot, therefore can't be reproduced anymore. I think it is safe to close this.
OK,thanks for the feedback.
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.