[Bug 112119] New: GPU HANG: ecode 11:1:0xfffffffe, in Xorg [955], hang on rcs0
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Oct 24 10:05:58 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=112119
Bug ID: 112119
Summary: GPU HANG: ecode 11:1:0xfffffffe, in Xorg [955], hang
on rcs0
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: not set
Priority: not set
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: xznqwe at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 145806
--> https://bugs.freedesktop.org/attachment.cgi?id=145806&action=edit
/sys/class/drm/card0/error
My laptop hangs and I find this in dmesg:
[ 5754.466689] i915 0000:00:02.0: GPU HANG: ecode 11:1:0xfffffffe, in Xorg
[955], hang on rcs0
[ 5754.466691] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 5754.466691] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 5754.466691] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 5754.466692] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 5754.466692] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 5754.467852] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 5757.656644] Asynchronous wait on fence i915:kwin_x11[1288]:4625a timed out
(hint:intel_atomic_commit_ready+0x0/0x50 [i915])
[ 5762.564500] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
My laptop is Lenovo Yoga C940 with I5-1035G4 running archlinux and kde. The
linux kernel is 5.3.7-arch1-1-ARCH.
Thanks in advance.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191024/e9bfd327/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list