Created attachment 104682 [details] full backtrace For people who are part of the Closed Alpha and want to test: It doesn't happen when changing the shadow levels between active levels. But when changing shadows from off to any level or from any level to off, this segfault happens every time. 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff) It does not crash when I run it on intel. It also does not crash when I run it on llvmpipe. So it is possibly related to PRIME rather than radeonsi, unfortunately I can't test without PRIME. mesa git, linux 3.16, launched in steam with: DRI_PRIME=1 GALLIUM_HUD="fps,VRAM-usage+GTT-usage" %command% It happens with both dri3 offloading and with LIBGL_DRI3_DISABLE=1
Does it also happen with llvmpipe?
(In reply to comment #1) > Does it also happen with llvmpipe? No. > It also does not crash when I run it on llvmpipe. For testing such things on PRIME v.s. no prime it would be good to be able to set up only xf86-video-ati in xorg.conf to be used in an "invisible" x server on a gpu with no outpus and then use e.g. vnc, but I didn't find any way to do this yet. "(EE) RADEON(0): No modes." seems to prevent X from starting, even with a modeline. (catalyst supports this OOTB) Best I could do is send the download link per mail or so if you want to test yourself.
Created attachment 105768 [details] The Book of Unwritten Tales 2 Early access - same backtrace The same happens when changing the graphics quality setting in "The Book of Unwritten Tales 2" Early Access (for kickstarter backers). Interestingly with the mesa debug build it works sometimes(?), but when changing the settings a few times, it very quickly crashes.
Both games had multiple updates by now. Whether the games got fixed, or the driver, I don't know. But it doesn't happen anymore.
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.