Bug 103548 - [kbl] GPU HANG: ecode 9:0:0x86dffffd, in chrome [6769], reason: Hang on rcs0, action: reset
Summary: [kbl] GPU HANG: ecode 9:0:0x86dffffd, in chrome [6769], reason: Hang on rcs0,...
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
Depends on:
Reported: 2017-11-02 16:54 UTC by Sylvain Lamontagne
Modified: 2019-09-25 19:04 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

GPU Crash dump (30.45 KB, text/plain)
2017-11-02 16:54 UTC, Sylvain Lamontagne

Description Sylvain Lamontagne 2017-11-02 16:54:31 UTC
Created attachment 135212 [details]
GPU Crash dump

Problem occured on a Thinkpad T470 connected to a Pro Docking Station and using an external monitor.

Creating this bug as instructed by the error message from 'dmesg'

[236451.402515] [drm] GPU HANG: ecode 9:0:0x86dffffd, in chrome [6769], reason: Hang on rcs0, action: reset
[236451.402516] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[236451.402517] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[236451.402517] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[236451.402532] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[236451.402533] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[236451.402570] drm/i915: Resetting chip after gpu hang
[236451.403024] [drm] RC6 on
Comment 1 Sylvain Lamontagne 2017-11-02 16:55:45 UTC
Kernel information
Linux lams-t470 4.13.10-041310-generic #201710270531 SMP Fri Oct 27 09:33:21 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Comment 2 Elizabeth 2017-12-08 22:36:34 UTC
Hello Sylvain,
Is this reproducible? Could you please share your Mesa and Xorg version, distro, desktop, if SNA or modesetting, and if reproducible, steps to reproduce.
Thank you.
Comment 3 GitLab Migration User 2019-09-25 19:04:54 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/1643.

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.