<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 - GPU HANG: ecode 5:0:0x9ffdffff, in gnome-shell [1926], reason: Ring hung, action: reset"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=91382">91382</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>GPU HANG: ecode 5:0:0x9ffdffff, in gnome-shell [1926], reason: Ring hung, action: reset
          </td>
        </tr>

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

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

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

        <tr>
          <th>OS</th>
          <td>Linux (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>frdsktp@genodeftest.de
          </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=117222" name="attach_117222" title="contains dmesg and /sys/class/drm/card0/error files.">attachment 117222</a> <a href="attachment.cgi?id=117222&action=edit" title="contains dmesg and /sys/class/drm/card0/error files.">[details]</a></span>
contains dmesg and /sys/class/drm/card0/error files.

I am running fedora 22 with kernel 4.0.8 on a x86_64 system. More packages:
gnome-shell-3.16.3-1.fc22.x86_64
firefox-39.0-8.fc22.x86_64
gstreamer1-1.4.5-1.fc22.x86_64
libdrm-2.4.61-3.fc22.x86_64

Hardware: iGPU of an Intel Core i5 6x0 series

Since today (since updating to kernel 4.0.8, this issue was not present in
kernel 4.0.7) I got this issue.

Steps to reproduce:
1. log in to gnome-shell session on X
2. open firefox (works with a fresh profile)
3. load youtube.com
(I tested this several times, always worked)

What happens on the UI:
Gnome-shell crashes (window decorations are gone)
firefox repaints its application window wrong, displaying content at wrong
positions
gnome-session tells me that it crashed and can't recover. I am forced to log
out.


In syslog (systemd journal) I see this:

firefox.desktop[3110]: libva info: VA-API version 0.37.0
firefox.desktop[3110]: libva info: va_getDriverName() returns 0
firefox.desktop[3110]: libva info: Trying to open
/usr/lib64/dri/i965_drv_video.so
firefox.desktop[3110]: libva info: Found init function __vaDriverInit_0_37
firefox.desktop[3110]: libva info: va_openDriver() returns 0
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_lock: assertion 'object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **: gst_memory_unmap:
assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_memory_get_sizes: assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_lock: assertion 'object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **: gst_memory_unmap:
assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_memory_get_sizes: assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_unlock: assertion 'object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_unref: assertion 'mini_object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_lock: assertion 'object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **: gst_memory_unmap:
assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_memory_get_sizes: assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_unlock: assertion 'object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_unref: assertion 'mini_object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_lock: assertion 'object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **: gst_memory_unmap:
assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_memory_get_sizes: assertion 'mem != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_unlock: assertion 'object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_unref: assertion 'mini_object != NULL' failed
firefox.desktop[3110]: (firefox:3467): GStreamer-CRITICAL **:
gst_mini_object_lock: assertion 'object != NULL' failed

with the last 5 lines repeating some hundred or thousand times until I kill
firefox (with sigterm or SAK). Inbetween I see this:

kernel: [drm] stuck on render ring
kernel: [drm] GPU HANG: ecode 5:0:0x9ffdffff, in gnome-shell [1926], reason:
Ring hung, action: reset
kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack,
including userspace.
kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against
DRI -> DRM/Intel
kernel: [drm] drm/i915 developers can then reassign to the right component if
it's not a kernel issue.
kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please
always attach it.
kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error

and

kernel: drm/i915: Resetting chip after gpu hang</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are on the CC list for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>