|Summary:||GPU hang on v4.20-rc5 on thinkpad x220|
|Component:||DRM/Intel||Assignee:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|Status:||CLOSED WORKSFORME||QA Contact:||Intel GFX Bugs mailing list <intel-gfx-bugs>|
|i915 platform:||SNB||i915 features:||GPU hang|
Description zblabunk 2018-12-29 20:14:50 UTC
Created attachment 142916 [details] dmesg Another problem on X220. Chromium was running with youtube video playing. [31850.666274] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [31850.666277] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [31850.666279] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [31850.666282] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [31850.666285] [drm] GPU crash dump saved to /sys/class/drm/card0/error [31850.666394] i915 0000:00:02.0: Resetting chip for hang on rcs0 [31850.668474] WARNING: CPU: 0 PID: 13675 at /data/fast/l/k/include/linux/dma-fence.h:503 i915_request_skip+0x71/0x80 [31850.668478] Modules linked in: [31850.668484] CPU: 0 PID: 13675 Comm: kworker/0:3 Not tainted 4.20.0-rc5+ #5 [31850.668487] Hardware name: LENOVO 42872WU/42872WU, BIOS 8DET74WW (1.44 ) 03/13/2018 Dmesg and /sys/class/drm/card0/error are attached.
Comment 1 zblabunk 2018-12-29 20:15:37 UTC
Created attachment 142917 [details] /sys/class/drm/card0/error
Comment 2 Chris Wilson 2018-12-29 20:47:48 UTC
blt commands on the rcs; more than likely a secondary effect of the list bogons.
Comment 3 Lakshmi 2019-02-13 11:45:40 UTC
Reporter, how often you see GPU hang if not random? Are there any specific steps to reproduce this issue?
Comment 5 Lakshmi 2019-04-12 08:47:17 UTC
No feedback from more than 2 months. Closing this bug as WORKSFORME. If this issue happens with latest drmtip, please attach dmesg from boot and error file. ALso, following information would be useful: How often it occurs the hang? Any particular way to reproduce this issue? What is the impact of this bug? Needs a force reboot after hang or system recovers after hang?