Bug 103704 - [kbl] GPU hang using chrome
Summary: [kbl] GPU hang using chrome
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2017-11-13 07:54 UTC by Dario Corti
Modified: 2019-09-25 19:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

crash dump (31.83 KB, text/plain)
2017-11-13 07:54 UTC, Dario Corti

Description Dario Corti 2017-11-13 07:54:11 UTC
Created attachment 135433 [details]
crash dump

As stated in dmesg, I'm reporting a gpu hang while using chrome. Kernel is 4.13.0-16-generic on Mint 18.2. Crash dump is attached. It's not a recurring issue, at the moment.

[  345.828099] [drm] GPU HANG: ecode 9:0:0x86dffffd, in chrome [3277], reason: Hang on rcs0, action: reset
[  345.828100] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  345.828100] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  345.828100] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  345.828101] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  345.828101] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  345.828141] drm/i915: Resetting chip after gpu hang
[  345.828290] [drm] RC6 on
[  353.821233] drm/i915: Resetting chip after gpu hang
[  353.821371] [drm] RC6 on
Comment 1 Dario Corti 2017-11-13 07:57:06 UTC
I forgot, mesa version is 17.0.7-0ubuntu0.16.04.2.
Comment 2 Elizabeth 2017-12-04 23:40:56 UTC
Hello Dario, thanks for you time. Is this reproducible with Mesa 17.2 and up?? Is there any specific step that triggers this issue??
Comment 3 Dario Corti 2017-12-05 12:17:05 UTC
Sorry, this happened only once, so I wouldn't know how to induce it and test with 17.2.
Comment 4 Elizabeth 2017-12-13 23:24:46 UTC
Thanks for the information Dario, I'll leave this as NEEDINFO while waiting for more sights of this issue.
Comment 5 GitLab Migration User 2019-09-25 19:05:35 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/1650.

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.