Bug 112420 - i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00210a0b, in X [10174], no progress on rcs0
Summary: i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00210a0b, in X [10174], no progress ...
Status: RESOLVED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-28 20:23 UTC by Gary E. Miller
Modified: 2019-11-29 07:23 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
/sys/class/drm/card0/error (31.63 KB, text/plain)
2019-11-28 20:23 UTC, Gary E. Miller 		no flags Details
View All

Description Gary E. Miller 2019-11-28 20:23:45 UTC 
Created attachment 146041 [details]
/sys/class/drm/card0/error

[ 1857.068191] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00210a0b, in X [10174], no progress on rcs0
[ 1857.068192] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1857.068192] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1857.068192] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1857.068193] The GPU crash dump is required to analyze GPU hangs, so please always attach it.
[ 1857.068193] GPU crash dump saved to /sys/class/drm/card0/error
[ 1857.068198] i915 0000:00:02.0: Resetting rcs0 for no progress on rcs0
[ 2269.032198] i915 0000:00:02.0: Resetting rcs0 for no progress on rcs0
Comment 1 Chris Wilson 2019-11-28 20:56:11 UTC 
Pixel data in the batch buffer:

IPEHR: 0xfff6f5f4

Most likely userspace (mesa/i965).
Comment 2 Lakshmi 2019-11-29 07:23:03 UTC 
Mesa issues can be reported here https://gitlab.freedesktop.org/mesa/mesa/issues

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.