Bug 110350 - DOOM 2016 crash + severe artifacting on RADV + Vega VII
Summary: DOOM 2016 crash + severe artifacting on RADV + Vega VII
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/radeon (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-08 06:41 UTC by Thomas Crider
Modified: 2019-05-06 07:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
desktop artifacting after doom crash (4.22 MB, image/png)
2019-04-08 06:41 UTC, Thomas Crider
Details

Description Thomas Crider 2019-04-08 06:41:25 UTC
Created attachment 143890 [details]
desktop artifacting after doom crash

Got a shiny new Vega VII, was running some tests on mesa-git + llvm-git. Managed to get a fun game crash with DOOM 2016 in Vulkan that causes the GPU to artifact on all desktops. Restarting the system makes it go back to normal. This only happens on mesa-git + llvm-svn, does not happen on Mesa 19.0.1 + LLVM 8

System:
Fedora 30
Kernel 5.0.7
Threadripper 2920x
Radeon Vega VII

Broken:
Mesa-git + LLVM-git

Working:
Mesa 19.0.1 + LLVM 8.0.0
Comment 1 Samuel Pitoiset 2019-04-08 14:38:12 UTC
Can you explain the steps for reproducing the problem in-game?
Comment 2 Thomas Crider 2019-04-08 19:49:10 UTC
Sure, I just started a new campaign and loaded into the first mission. no less than about 15-30 seconds in it immediately went black/polygony, then crashed. I'll see if I can record it later tonight. My resolution was 4k60 and settings were maxed
Comment 3 Thomas Crider 2019-04-09 04:13:19 UTC
https://youtu.be/9dtlKTMGqTE

game didn't crash this time, and at least i was able to capture it
Comment 4 Samuel Pitoiset 2019-04-09 11:37:42 UTC
Does it render correctly with Mesa-git + LLVM 8.0.0 ?
Comment 5 Samuel Pitoiset 2019-04-09 12:04:23 UTC
Could be something specific to Vega20 as it renders correctly for me on Vega10+mesa-git+llvm-git.
Comment 6 Thomas Crider 2019-04-09 14:46:22 UTC
Issue does -not- occur on mesa-git + llvm 8, so looks like it's an llvm issue
Comment 7 Samuel Pitoiset 2019-04-09 15:16:09 UTC
Can you eventually bisect?
Unfortunately, I don't have a Vega20.
Comment 8 Samuel Pitoiset 2019-04-26 16:51:09 UTC
Got a Vega20, I tried to reproduce the problem with mesa-git, llvm-git and the same settings as you, but it doesn't happen.

I also tried some older LLVM commits, no graphic glitches so far.

Are you still able to reproduce the problem?
Comment 9 Anton Herzfeld 2019-05-01 19:03:57 UTC
could you try reverting:

https://github.com/mesa3d/mesa/commit/b5ea4378c3260ff003532c8138a81a57091bdaa0#diff-078b981b454c93e62531f44768fca61d

ac/nir: only use the new raw/struct image atomic intrinsics with LLVM 9+
b5ea4378c3260ff003532c8138a81a57091bdaa0

and see if this fixes your issue?
Comment 10 Thomas Crider 2019-05-05 17:42:25 UTC
Hi all, sorry for such a long delay on this. I recently switched to Fedora and realized the llvm build from the copr repo I was using was over a month old. I needed some time to create my own repos to circumvent this problem. As of today I've tested with llvm-git + mesa-git built yesterday and everything is working as it should. Please feel free to close the ticket as the issue has been resolved with an updated llvm build.
Comment 11 Samuel Pitoiset 2019-05-06 07:05:46 UTC
Thanks for confirming!


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.