<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 - Tonga Oopses with uvd + agd5f drm-next-4.3-wip"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=91667">91667</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Tonga Oopses with uvd + agd5f drm-next-4.3-wip
          </td>
        </tr>

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

        <tr>
          <th>Version</th>
          <td>DRI 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>DRM/AMDgpu
          </td>
        </tr>

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

        <tr>
          <th>Reporter</th>
          <td>adf.lists@gmail.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Created <span class=""><a href="attachment.cgi?id=117730" name="attach_117730" title="Oops 1">attachment 117730</a> <a href="attachment.cgi?id=117730&action=edit" title="Oops 1">[details]</a></span>
Oops 1

Tried the newly updated agd5f drm-next-4.3-wip today and got some oopses with
uvd.

These are provoked by repeatedly starting a vid with mpplayer - a known issue,
but the change for me on Tonga is getting the Oopses.

On other kernels amdgpu/amd-staging/drm-fixes the same test would provoke a
ring 9 lock (rarely ring 0) and a failed reset, which at least would leave me
alive enough to get a VT.

I notice GPU stall detection has now been disabled - but testing various
4.3-wips over some weeks I have never got one anyway. Doing something like this
test or running valley would just lock the display and log nothing. SysRq
worked OK as it still does - just now I get some logging (though not for the
one Unigine Valley lock I just provoked).

I am now running mesa/drm mesa/mesa Git Xorg with DRI3 enabled.

While testing I noticed the tree got another update  - retested and still get
the same.

The first 2 are from the older tree, the second long as secondary Oopses were
provoked.

The third is current.</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>