Bug 111752 - i915 0000:00:02.0: GPU HANG: ecode 9:1:0xfffffffe, in chromium [2089], hang on rcs0
Summary: i915 0000:00:02.0: GPU HANG: ecode 9:1:0xfffffffe, in chromium [2089], hang o...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: not set not set
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-19 13:41 UTC by Nathan Baker
Modified: 2019-09-25 20:35 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Crash dump file (62.24 KB, text/plain)
2019-09-19 13:41 UTC, Nathan Baker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Baker 2019-09-19 13:41:46 UTC
Created attachment 145435 [details]
Crash dump file

[1455951.508638] i915 0000:00:02.0: GPU HANG: ecode 9:1:0xfffffffe, in chromium [2089], hang on rcs0
[1455951.508639] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[1455951.508640] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[1455951.508640] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[1455951.508641] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[1455951.508643] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[1455951.509663] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0

I have attached the crash dump.
Comment 1 Chris Wilson 2019-09-19 14:46:52 UTC
Nothing suspicious in the execlists state, so the hang inside the batch is first point of inspection.
Comment 2 GitLab Migration User 2019-09-25 20:35:47 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1837.


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.