<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 - [regression, bisected] Games freeze the PC with newest AMD Staging DRM Next Kernel"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=107367">107367</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>[regression, bisected] Games freeze the PC with newest AMD Staging DRM Next Kernel
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Mesa
          </td>
        </tr>

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

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

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

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

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

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

        <tr>
          <th>Component</th>
          <td>Drivers/Gallium/radeonsi
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>dri-devel@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>gr.muench@gmail.com
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>dri-devel@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>This reproducible all the time with Dota2 starting a benchmark with 1920x1080
and Vulkan using Phoronix test suite.
Starting the benchmark makes the machine freeze and you just can hit the reset
button.
I also experienced the freeze with Shadow of Mordor but not all the time.

fc9a53946d9c107a36b79de3dd1a4eac43f13f3f is the first bad commit
commit fc9a53946d9c107a36b79de3dd1a4eac43f13f3f
Author: Junwei Zhang <<a href="mailto:Jerry.Zhang@amd.com">Jerry.Zhang@amd.com</a>>
Date:   Mon Jul 16 10:53:43 2018 +0800

    drm/scheduler: add NULL pointer check for run queue (v2)

    To check rq pointer before adding entity into it.
    That avoids NULL pointer access in some case.

    v2: move the check to caller

    Suggested-by: Christian König <<a href="mailto:christian.koenig@amd.com">christian.koenig@amd.com</a>>
    Signed-off-by: Junwei Zhang <<a href="mailto:Jerry.Zhang@amd.com">Jerry.Zhang@amd.com</a>>
    Reviewed-by: Christian König <<a href="mailto:christian.koenig@amd.com">christian.koenig@amd.com</a>>

:040000 040000 aa8b4eb640e3995a1f77907edd6ec8fc6fccd1b3
4a061e532ddb8a1293e781a4ccd5ece2efe35d8a M      drivers


Reverting the commit let the freeze go away.</pre>
        </div>
      </p>


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

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>