Comment # 4
on bug 98028
from Daniel Scharrer
Created attachment 127001 [details] R600_DEBUG=vs,tcs,tes,gs,ps,cs log (In reply to Nicolai Hähnle from comment #3) > I haven't been able to reproduce this with Mesa master and LLVM r283219 so > far. Does this happen with clean re-builds? Yes, all LLVM and Mesa builds were done through the package manager, starting with an empty build directory. And I don't use ccache. I just re-checked with an updated LLVM & Mesa and the game still crashes: Mesa: git-0e85ff3 LLVM: r283225 I also verified that it still starts properly with amdgpu-pro (running on top of the upstream 4.7.5 amdgpu module). > If this still happens with current LLVM and clean re-builds, please provide > logs with R600_DEBUG=vs,tcs,tes,gs,ps,cs. > > The wide range of different backtraces suggests that it might be random > memory corruption, so running under Valgrind may also be worth a shot. It does look like it. I'll get a valgrind memcheck log, but will first need to recompile a couple of libraries because valgrind still doesn't support all the instructions of my CPU :/
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel