Bug 105373 - [kbl-h] GPU HANG: ecode 9:0:0xfedffffa, in Xorg [1345], reason: Hang on rcs0, action: reset
Summary: [kbl-h] GPU HANG: ecode 9:0:0xfedffffa, in Xorg [1345], reason: Hang on rcs0,...
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Whiteboard: ReadyForDev
Depends on:
Reported: 2018-03-06 22:44 UTC by Vasil Kolev
Modified: 2018-04-26 10:27 UTC (History)
4 users (show)

See Also:
i915 platform: KBL
i915 features: GPU hang

/sys/class/drm/card0/error (16.83 KB, application/x-bzip)
2018-03-06 22:44 UTC, Vasil Kolev
no flags Details
dmesg (57.19 KB, text/plain)
2018-03-06 22:45 UTC, Vasil Kolev
no flags Details
/sys/class/drm/card0/error with 1.04 (4.16 KB, application/x-bzip)
2018-03-07 16:20 UTC, Vasil Kolev
no flags Details
dmesg with 1.04 (56.72 KB, text/plain)
2018-03-07 16:20 UTC, Vasil Kolev
no flags Details
dmesg with drim.debug (97.48 KB, text/plain)
2018-03-07 18:15 UTC, Vasil Kolev
no flags Details
/sys/class/drm/card0/error with drm-tip (26.33 KB, application/x-bzip)
2018-03-29 13:43 UTC, Vasil Kolev
no flags Details
dmesg with drm-tip (117.97 KB, text/plain)
2018-03-29 13:43 UTC, Vasil Kolev
no flags Details
dmesg with drm-tip 4.17.0-rc2 (d04fd4f6d93cea918521059db8358ff9e7a4a03b) (118.07 KB, text/plain)
2018-04-24 15:54 UTC, Vasil Kolev
no flags Details
/sys/class/drm/card0/error with drm-tip 4.17.0-rc2 (d04fd4f6d93cea918521059db8358ff9e7a4a03b) (26.39 KB, application/x-bzip)
2018-04-24 15:55 UTC, Vasil Kolev
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vasil Kolev 2018-03-06 22:44:46 UTC
Created attachment 137844 [details]

issue: GPU doesn't even start working

On every boot, as soon as I login and compiz tries to start, the above message shows up in dmesg.
Comment 1 Vasil Kolev 2018-03-06 22:45:39 UTC
Created attachment 137845 [details]
Comment 2 Chris Wilson 2018-03-07 08:45:31 UTC
You need to update the dmc firmware:

commit 4f0aa1fa3e3849caee450ee5d14fcc289cf16703
Author: Anusha Srivatsa <anusha.srivatsa@intel.com>
Date:   Thu Nov 9 10:51:43 2017 -0800

    drm/i915/dmc: DMC 1.04 for Kabylake
    There is a new version of DMC available for KBL.
    The release notes mentions:
    1. Fix for the issue where DC_STATE was getting enabled even
    when disabled by driver causing data corruption.
    v2: Remove pull request from commit message (Rodrigo).
    Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
    Signed-off-by: Jani Nikula <jani.nikula@intel.com>
    Link: https://patchwork.freedesktop.org/patch/msgid/1510253503-12634-1-git-send-email-anusha.srivatsa@intel.com
Comment 3 Vasil Kolev 2018-03-07 16:19:22 UTC
Same happens with 1.04. Attaching dmesg, /sys/class/drm/card0/error.

Also, echo 1 > /sys/kernel/debug/dri/0/i915_wedged doesn't seem to have any effect, it's still unable to reset the GPU.
Comment 4 Vasil Kolev 2018-03-07 16:20:09 UTC
Created attachment 137865 [details]
/sys/class/drm/card0/error with 1.04
Comment 5 Vasil Kolev 2018-03-07 16:20:35 UTC
Created attachment 137866 [details]
dmesg with 1.04
Comment 6 Elizabeth 2018-03-07 17:33:49 UTC
Hi, could you attach dmesg with debug info, drm.debug=0xe parameter in grub. Thanks.
Comment 7 Vasil Kolev 2018-03-07 18:15:06 UTC
Created attachment 137869 [details]
dmesg with drim.debug

Here's the dmesg with debug.
Comment 8 Jani Saarinen 2018-03-29 07:10:51 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 9 Vasil Kolev 2018-03-29 07:42:59 UTC
Jani, yes, this is still valid - there doesn't seem to have been a new release of anything related to this, and the bug persists (my GPU is hung and I still use some very slow driver/access to my video card).

The stuff I'm currently running is 4.15.0 with the path for the 1.04 firmware. Is there any new work in the drm-tip, and how do I fetch that?
Comment 10 Jani Saarinen 2018-03-29 08:09:31 UTC
You can get drm-tip from: https://cgit.freedesktop.org/drm-tip.
Comment 11 Vasil Kolev 2018-03-29 13:43:20 UTC
Created attachment 138427 [details]
/sys/class/drm/card0/error with drm-tip
Comment 12 Vasil Kolev 2018-03-29 13:43:57 UTC
Created attachment 138428 [details]
dmesg with drm-tip
Comment 13 Vasil Kolev 2018-03-29 13:45:33 UTC
(In reply to Jani Saarinen from comment #10)
> You can get drm-tip from: https://cgit.freedesktop.org/drm-tip.

Attached are the dmesg (with debug enabled) and the error from the card with drm-tip. The issue persists.
Comment 14 Jani Saarinen 2018-04-24 07:00:58 UTC
Mika, Chris, any advice here?
Comment 15 Mika Kuoppala 2018-04-24 14:07:24 UTC
Looked at this and discussed with Chris on irc and here are the findings:

HW RING START is not from request that was queued to hardware. And the
gpu is dormant on a previous requests tail.

Please retest with fetching a up-to-date drm-tip from https://cgit.freedesktop.org/drm-tip and prevent driver from loading a dmc firmware by moving dmc firmware binaries out from /lib/firmware/i915.
Comment 16 Vasil Kolev 2018-04-24 15:54:30 UTC
Created attachment 139062 [details]
dmesg with drm-tip 4.17.0-rc2 (d04fd4f6d93cea918521059db8358ff9e7a4a03b)
Comment 17 Vasil Kolev 2018-04-24 15:55:06 UTC
Created attachment 139063 [details]
/sys/class/drm/card0/error with drm-tip 4.17.0-rc2 (d04fd4f6d93cea918521059db8358ff9e7a4a03b)
Comment 18 Vasil Kolev 2018-04-24 15:56:46 UTC
Retested with the latest drm-tip, the issue looks the same.

Is there anything else besides the dmesg and /sys/class/drm/card0/error I can help with? I can see to provide access to the laptop in question.

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.