Bug 105605 - GPU HANG: ecode 9:0:0xfffffffe, in Xorg [8100], reason: Hang on rcs0, action: reset
Summary: GPU HANG: ecode 9:0:0xfffffffe, in Xorg [8100], reason: Hang on rcs0, action:...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-19 14:29 UTC by shaleen.jain95
Modified: 2018-03-28 16:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (35.25 KB, text/plain)
2018-03-19 14:29 UTC, shaleen.jain95
no flags Details
dmesg (84.46 KB, text/plain)
2018-03-19 14:36 UTC, shaleen.jain95
no flags Details
attachment-32737-0.html (1.76 KB, text/html)
2018-03-28 16:07 UTC, shaleen.jain95
no flags Details

Description shaleen.jain95 2018-03-19 14:29:50 UTC
Created attachment 138197 [details]
/sys/class/drm/card0/error

Random hangs with gnome shell. This one occured after resuming from suspend. The gpu resets multiple times after hang.

dmesg snippet: 
[ 2859.759266] [drm] GPU HANG: ecode 9:0:0xfffffffe, in Xorg [8100], reason: Hang on rcs0, action: reset
[ 2859.759267] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 2859.759268] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 2859.759268] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 2859.759268] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 2859.759269] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2859.759311] i915 0000:00:02.0: Resetting chip after gpu hang
[ 2859.759416] [drm] RC6 on
[ 2859.761278] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
[ 2859.763373] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_14.bin (version 9.14)
[ 2859.763502] i915 0000:00:02.0: GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin [version 9.14])
[ 2861.031928] asynchronous wait on fence i915:Xorg[8100]/1:1483a timed out
[ 2867.752043] i915 0000:00:02.0: Resetting chip after gpu hang
[ 2868.253989] [drm] RC6 on
[ 2868.256300] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
[ 2868.258398] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_14.bin (version 9.14)
[ 2868.258618] i915 0000:00:02.0: GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin [version 9.14])
[ 2875.752075] i915 0000:00:02.0: Resetting chip after gpu hang
[ 2876.255255] [drm] RC6 on
[ 2876.257565] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
[ 2876.259664] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_14.bin (version 9.14)
[ 2876.259903] i915 0000:00:02.0: GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin [version 9.14])
[ 2883.752051] i915 0000:00:02.0: Resetting chip after gpu hang
[ 2884.254033] [drm] RC6 on
[ 2884.256313] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
[ 2884.258415] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_14.bin (version 9.14)
[ 2884.258634] i915 0000:00:02.0: GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin [version 9.14])
[ 2891.752099] i915 0000:00:02.0: Resetting chip after gpu hang
[ 2892.255510] [drm] RC6 on
[ 2892.257823] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0)
[ 2892.259922] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_14.bin (version 9.14)
[ 2892.260142] i915 0000:00:02.0: GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin [version 9.14])
Comment 1 shaleen.jain95 2018-03-19 14:36:04 UTC
Created attachment 138198 [details]
dmesg

Arch Linux
4.15.10-1-ARCH
mesa: 17.3.6-1
Comment 2 Chris Wilson 2018-03-19 15:46:46 UTC
Enable unsafe, performance detrimental parameters at your peril: i915.enable_guc_loading=1 i915.enable_guc_submission=1
Comment 3 Jani Saarinen 2018-03-28 16:03:08 UTC
Hi, reporter do you agree this as invalid and issue can be closed?
Comment 4 shaleen.jain95 2018-03-28 16:07:31 UTC
Created attachment 138395 [details]
attachment-32737-0.html

Yes

On Wed, Mar 28, 2018, 9:33 PM <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=105605#c3> on
> bug 105605 <https://bugs.freedesktop.org/show_bug.cgi?id=105605> from Jani
> Saarinen <jani.saarinen@intel.com> *
>
> Hi, reporter do you agree this as invalid and issue can be closed?
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
> --

Regards,

Shaleen Jain


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.