Bug 109498 - Game enabling VBO Core but disabling VAO Core causing reproducible, predictable, spontaneous powerdown
Summary: Game enabling VBO Core but disabling VAO Core causing reproducible, predictab...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-29 16:56 UTC by Adam Wenocur
Modified: 2019-11-19 09:12 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg output (65.07 KB, text/plain)
2019-01-29 17:12 UTC, Adam Wenocur
no flags Details
XOrg log (57.27 KB, text/x-log)
2019-01-29 17:12 UTC, Adam Wenocur
no flags Details

Description Adam Wenocur 2019-01-29 16:56:00 UTC
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.
Comment 1 Alex Deucher 2019-01-29 17:01:19 UTC
Please attach your dmesg output and xorg log (if using X).
Comment 2 Adam Wenocur 2019-01-29 17:12:19 UTC
Created attachment 143249 [details]
dmesg output
Comment 3 Adam Wenocur 2019-01-29 17:12:55 UTC
Created attachment 143250 [details]
XOrg log
Comment 4 Martin Peres 2019-11-19 09:12:02 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/687.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.