<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 - Game enabling VBO Core but disabling VAO Core causing reproducible, predictable, spontaneous powerdown"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109498">109498</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Game enabling VBO Core but disabling VAO Core causing reproducible, predictable, spontaneous powerdown
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (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>awenocur@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>The game "openAstroMenace", for some reason defaults to using VBO Core in the
absence of VAO core, which predictably causes the game to crash on a modern
OpenGL implementation. The game itself crashing is not a problem; it's the PSU
switching off that's very concerning.
I'm running an ASRock E3V5 WS motherboard with a 4 GB Sapphire R9 Fury X, and
an E3-1235L CPU.
I'm early on in diagnosing it so I don't have a stack trace, but I think I've
ruled out hardware problems, as this system doesn't break a sweat maxing out
the Heaven benchmark or the Phoronix JuliaGPU (via ROCm) benchmark, and plays
every other game flawlessly. It can run with all CPU cores at 100% for hours on
end. openAstroMenace runs flawlessly with max settings when VAO Core is
enabled.
Mesa may be malfunctioning here, but a userspace library wouldn't affect PSU
behavior. This is pointing me in the direction of suspecting AMDGPU to be the
culprit. It exhibits this behavior on both my Ubuntu and Gentoo installations,
and on 4.15 and 4.18 series kernels. The system poweroff is predictable down to
less than half a second, and is triggered exactly the same way at exactly the
same time in every instance. It occurs around 3/4 of a second after the game's
menu appears.</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>