<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 - vm protection faults in piglit lest: texsubimage cube_map_array pbo"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=89957">89957</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>vm protection faults in piglit lest: texsubimage cube_map_array pbo
          </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>tstellar@gmail.com
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>dri-devel@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>To reproduce:  /home/tstellar/piglit/bin/texsubimage cube_map_array pbo -auto
-fbo

I've spent some time debugging this and it appears the result from the
v_cubeid_f32
instruction is causing the shader to access memory outside the bounds of the
texture.

If I replace v_cubeid_f32 $dst, $src0, $src1, $src2 instructions with v_mov_f32
$dst, 0.0 or v_mov_f32 $dst, 1.0
I no longer see vm protection faults.

However, if I replace the v_cubeid_f32 instructions with v_mov_f32 $dst, 2.0
then the vm protection faults return.  So, it seems the bad case is whenever
the face id is computed as >= 2.0f.</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>