| Summary: | [radeonsi/llvm] Segfault in CS:GO | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Tobias Droste <tdroste> |
| Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED FIXED | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | normal | ||
| Priority: | medium | CC: | sarnex |
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=92944 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Backtrace of the segfault
Output of R600_DEBUG=vs,gs,ps R600_DEBUG=vs,gs,ps |
||
Hi Tobias, thanks for the new report. As with bug #92944, could you please provide a log with R600_DEBUG=vs,gs,ps? This will show the segfaulting shader and should allow simple reproduction at least. Created attachment 120476 [details]
Output of R600_DEBUG=vs,gs,ps
Created attachment 120488 [details]
R600_DEBUG=vs,gs,ps
Hello. I have the exact same issue. The assert in LLVM is llvm::IndexListEntry* llvm::SlotIndex::listEntry() const: Assertion `isValid() && "Attempt to compare reserved index."' failed.
I've attached my R600_DEBUG=vs,gs,ps also. I have a HD 7950/Tahiti.
I hope this helps.
Thanks,
sarnex
I found out why the last CS update caused this issue. They siwtched all graphic options to "auto" with the last update and for my graphics card it figured out that the highest preference in every setting should be the best ones. And with these settings CS:GO is crashing. I switched backed everything to "low" and I can at least play the game again. But the driver should crash with everything set to high. (In reply to Tobias Droste from comment #4) > I found out why the last CS update caused this issue. > They siwtched all graphic options to "auto" with the last update and for my > graphics card it figured out that the highest preference in every setting > should be the best ones. And with these settings CS:GO is crashing. > > I switched backed everything to "low" and I can at least play the game > again. But the driver should crash with everything set to high. "should *not* crash" of course :-) Thank you for posting the workaround! I can confirm that the logs of both of you contain (different) shaders that crash with standalone llc, making this bug easy to reproduce at least. Because bug 92944 was magically fixed I just tested again with everything set to high and it looks like this is not crashing anymore. This was with LLVM svn trunk and mesa git from 2 days ago. Though the image looks wrong with everything set to high. The lighting is doesn't seem to be rendered correctly. Sarnex is it working for you? (In reply to Tobias Droste from comment #7) > Because bug 92944 was magically fixed I just tested again with everything > set to high and it looks like this is not crashing anymore. This was with > LLVM svn trunk and mesa git from 2 days ago. > > Though the image looks wrong with everything set to high. The lighting is > doesn't seem to be rendered correctly. > > Sarnex is it working for you? Hi Tobias, Yeah, it seems to be working for me also. I guess the underlying bug was fixed. Great works guys at AMD. Thanks, sarnex |
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.
Created attachment 120470 [details] Backtrace of the segfault When loading of a level is done in CS:GO and the team selection menu should pop up CS:GO segfaults here: #0 0xf4f2cd2d in llvm::LiveRange::find(llvm::SlotIndex) () from /usr/local/lib/dri/radeonsi_dri.so Hardware: Hawaii PRO [Radeon R9 290] This happens with most recent LLVM SVN and Mesa git, and also with LLVM and Mesa from October. So this seems to be some long standing error in either Mesa or LLVM that is triggered now by a change of CS:GO.