<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 - Screen flashes, but eventual "Blue Screen""
   href="https://bugs.freedesktop.org/show_bug.cgi?id=92319">92319</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Screen flashes, but eventual "Blue Screen"
          </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>critical
          </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>ianh@brownpapertickets.com
          </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>We have many Dell Optiplex 380/390 which have run CentOS 6.5 happily for years.
 We upgraded some to CentOS 7 and have intermittent screen flashing and
occasional blue screen (not like Windows, the screen just goes shades of blue
and locks up)

Saw this in the log and did it:

Oct  6 11:06:47 seattle154 kernel: [drm] GPU HANG: ecode -1:0x00000000, reason:
Kicking stuck semaphore on render ring, action: continue
Oct  6 11:06:47 seattle154 kernel: [drm] GPU hangs can indicate a bug anywhere
in the entire gfx stack, including userspace.
Oct  6 11:06:47 seattle154 kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Oct  6 11:06:47 seattle154 kernel: [drm] drm/i915 developers can then reassign
to the right component if it's not a kernel issue.
Oct  6 11:06:47 seattle154 kernel: [drm] The gpu crash dump is required to
analyze gpu hangs, so please always attach it.
Oct  6 11:06:47 seattle154 kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error</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>