Bug 112119 - GPU HANG: ecode 11:1:0xfffffffe, in Xorg [955], hang on rcs0
Summary: GPU HANG: ecode 11:1:0xfffffffe, in Xorg [955], hang on rcs0
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2019-10-24 10:05 UTC by xznqwe
Modified: 2019-10-30 11:33 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

/sys/class/drm/card0/error (31.97 KB, text/plain)
2019-10-24 10:05 UTC, xznqwe
no flags Details

Description xznqwe 2019-10-24 10:05:58 UTC
Created attachment 145806 [details]

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.
Comment 1 Lakshmi 2019-10-30 11:30:42 UTC
rcs0 command stream:
  IDLE?: no
  START: 0x001aa000
  HEAD:  0x002026c0 [0x00002680]
  TAIL:  0x00002790 [0x000026c8, 0x00002700]
  CTL:   0x00003001
  MODE:  0x00000000
  HWS:   0xfedfe000
  ACTHD: 0x0000fffe ec085890
  IPEIR: 0x00000000
  IPEHR: 0x7a000004

The execution is inside the as head!=acthd, closing this issue as NOTOURBUG.
Comment 2 Lakshmi 2019-10-30 11:33:57 UTC
Likely Mesa issue. Please create an issue here

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.