<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:aeb@debian.org" title="Andreas Bombe <aeb@debian.org>"> <span class="fn">Andreas Bombe</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression)"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=68125">bug 68125</a>
        <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>---
           </td>
           <td>FIXED
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression)"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=68125#c4">Comment # 4</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression)"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=68125">bug 68125</a>
              from <span class="vcard"><a class="email" href="mailto:aeb@debian.org" title="Andreas Bombe <aeb@debian.org>"> <span class="fn">Andreas Bombe</span></a>
</span></b>
        <pre>While bisecting I noticed that CONFIG_DEBUG_WW_MUTEX_SLOWPATH was introduced
and that I had it enabled. Since that potentially introduces additional
-EDEADLK I suspected that check.

Turns out that check was buggy, the fix 85f489612 "mutex: Fix w/w mutex
deadlock injection" was merged since I posted this bug and the commit even
mentions explicitly that the bug caused spurious GPU lockups on radeon. The
problem appears to be gone with this fix.</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>