<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - r600g: unrecoverable GPU lockup after glDrawElements INVALID_ENUM"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74726">74726</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>r600g: unrecoverable GPU lockup after glDrawElements INVALID_ENUM
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>edwin+mesa@etorok.net
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/Gallium/r600
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=93679" name="attach_93679" title="corrupt.trace">attachment 93679</a> <a href="attachment.cgi?id=93679&action=edit" title="corrupt.trace">[details]</a></span>
corrupt.trace
If you send a lot of invalid glDrawElements commands to Mesa it can cause a GPU
lockup. Would it be possible to validate this Mesa side / or kernel CS checker
side to avoid the GPU lockup? [1]
If you replay the attached trace on r600g you get a GPU lockup, see
attachments:
* gpureset.log: dmesg when reboot is the only solution, no text console, no X,
nothing works until a reboot
* text_recovered.log: dmesg when I can kill the application and X, and get to
a framebuffer text console. Starting X is impossible though, unless I reboot
I've run the trace under valgrind, and I see no valgrind errors, but of course
I see a lot of Mesa errors. The mesa errors shouldn't cause a GPU lockup
though.
I reproduced this with the 10.1 branch, but similar lockups happen on the
10.0.2 release too (if you force the version to 3.3), so it doesn't seem to be
related to the 3.3 work on the 10.1 branch.
Mesa built like this:
$ ./configure --enable-dri --enable-glx-tls --enable-shared-glapi
--enable-texture-float --enable-xa --disable-xvmc --disable-vdpau
--with-gallium-drivers=r600,swrast LLVM_CONFIG=/usr/bin/llvm-config-3.4
--disable-dri3 --enable-debug
OpenGL version:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.0-rc1
(git-1e6bba5)
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.1.0-rc1 (git-1e6bba5)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
kernel:
$ uname -a
Linux debian 3.14.0-rc1-00015-g7c4c62a #48 SMP PREEMPT Sat Feb 8 17:33:48 EET
2014 x86_64 GNU/Linux
[1]
There are some use-after-free bugs in the gltut tutorials when you press
Escape: it frees some stuff, then calls glutLeaveMainLoop(), but freeglut still
calls display(), causing use-after-frees. Of course its expected that the
application itself might crash, or otherwise misbehave, but I was not expecting
an unrecoverable GPU lockup.</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>