<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=106342">106342</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[drm] HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g [103585], reason: Hang on rcs0, action: reset
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DRI
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>XOrg git
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>major
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>DRM/Intel
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>thiago@kde.org
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Created <span class=""><a href="attachment.cgi?id=139259" name="attach_139259" title="card0_error 2018-05-02">attachment 139259</a> <a href="attachment.cgi?id=139259&action=edit" title="card0_error 2018-05-02">[details]</a></span>
card0_error 2018-05-02

Possibly related to <a class="bz_bug_link 
          bz_status_CLOSED  bz_closed"
   title="CLOSED FIXED - [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset"
   href="show_bug.cgi?id=101991">Bug 101991</a> (which I reported), <a class="bz_bug_link 
          bz_status_CLOSED  bz_closed"
   title="CLOSED FIXED - kernel: [drm] GPU HANG: ecode 9:0:0xfffffffe, reason: Hang on rcs0, action: reset"
   href="show_bug.cgi?id=104545">bug 104545</a> (which says was
fixed by the same commit).

<a class="bz_bug_link 
          bz_status_CLOSED  bz_closed"
   title="CLOSED FIXED - [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset"
   href="show_bug.cgi?id=101991">Bug 101991</a> was about a GPU hang after resuming from hibernation. That is still
the problem I am having: after a few cycles of suspend-to-disk (hibernate) and
resume, I get a GPU hang soon after resuming, if not immediately after.

<a class="bz_bug_link 
          bz_status_CLOSED  bz_closed"
   title="CLOSED FIXED - [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset"
   href="show_bug.cgi?id=101991">Bug 101991</a> was reportedly fixed by SKL DMC 1.27, which is what I am now using
(kernel 4.16.3):

[    4.106911] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin
(v1.27)

Unlike <a class="bz_bug_link 
          bz_status_CLOSED  bz_closed"
   title="CLOSED FIXED - [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset"
   href="show_bug.cgi?id=101991">Bug 101991</a>, the screen is still responsive after hang, not frozen. But
many OpenGL workloads stop working, to the point that desktop is unusable due
to EIO errors happening. It's just good enough for me to cleanly reboot, as
opposed to forcing it via Alt+SysRq. Applications are not actually crashing (no
coredump created), but appear to be exiting with error by something inside
Mesa.

dmesg log:
[217047.398083] [drm] GPU HANG: ecode 9:0:0x9cba0f27, in kscreenlocker_g
[103585], reason: Hang on rcs0, action: reset
[217047.398085] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[217047.398085] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[217047.398086] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[217047.398086] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[217047.398087] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[217047.398104] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[217048.617889] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[217048.617933] i915 0000:00:02.0: Resetting chip after gpu hang
[217049.833883] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[217051.160111] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[217052.482897] [drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request
timeout
[217052.589836] i915 0000:00:02.0: Failed to reset chip

Attached the card0/error file.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are on the CC list for the bug.</li>
          <li>You are the assignee for the bug.</li>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>