Bug 109942 - [ilk] GPU HANG: ecode 5:0:0xfcefffdf, in chromium -- https://www.android.com/versions/go-edition/
Summary: [ilk] GPU HANG: ecode 5:0:0xfcefffdf, in chromium -- https://www.android.com...
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 18.3
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2019-03-08 11:53 UTC by kbt
Modified: 2019-09-25 20:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

GPU crash dump saved to /sys/class/drm/card0/error (22.83 KB, text/plain)
2019-03-08 11:53 UTC, kbt
glxinfo (18.64 KB, text/plain)
2019-03-08 13:10 UTC, kbt

Description kbt 2019-03-08 11:53:13 UTC
Created attachment 143588 [details]
GPU crash dump saved to /sys/class/drm/card0/error

I have a reproducible bug here. I'm on Arch/Linux, and I use chromium as a Web browser. If I visit https://www.android.com/versions/go-edition/ with it, the screen freezes for many seconds and dmesg gives me this message:

[drm] GPU HANG: ecode 5:0:0xfcefffdf, in chromium [2461], reason: hang on rcs0, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
Comment 1 Tapani Pälli 2019-03-08 12:30:23 UTC
please include glxinfo output too
Comment 2 kbt 2019-03-08 13:10:05 UTC
Created attachment 143594 [details]
Comment 3 Denis 2019-03-11 11:08:59 UTC
just a side note, I checked this issue on SNB, mesa-18.3.4 (built from git) and couldn't reproduce it. So looks like it is actual only on ILK
Comment 4 GitLab Migration User 2019-09-25 20:32:25 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/1796.

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.