Created attachment 118582 [details] gdb log (start | Ctrl-C | thread apply all bt) I already reported this on the linux kernel (https://bugzilla.kernel.org/show_bug.cgi?id=105201) but am not sure if it belongs there or here. I'm getting this error message on the command line with Borderlands 2. The game freezes and shortly after terminates when this happens. Does it matter what stuff in the game triggers it? Can I debug this somehow? I attached a log of starting it in gdb and stopping it manually after it froze, because for some reason in gdb it doesn't terminate itself, but I guess that's probably not very useful.
dmesg? Possible dup of bug 91730?
I'd think it's not a duplicate of that other bug as that is about an older CPU and my older CPU (although it was Haswell and not Ivy Bridge) didn't have this problem. Anyway, I guess I should have thought of this myself. Then I wouldn't have posted on the Linux kernel bug tracker, as the dmesg log tells me where to report this, and it is here. Also, the log talks about i915, but the gdb backtrace told me Borderlands2 was calling into /usr/lib32/xorg/modules/dri/i965_dri.so. Should this bug be moved from DRI/i965 to DRI/i915 or is this the right category?
Created attachment 118591 [details] full dmesg log (crash at [ 440.023966])
Created attachment 119682 [details] /sys/class/drm/card0/error Just noticed dmesg referenced this file. Would this help to find the problem? Also, there is are at least two ways of reproducing this in the game, and it's two special animations. Would it be possible to use this fact to narrow down the possible causes (with help from the games developers)?
Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. If you can reproduce, please capture and upload an apitrace (https://github.com/apitrace/apitrace) so that we can easily reproduce as well. (In reply to Jonas Platte from comment #2) > Also, the log talks about i915, but the gdb backtrace told me Borderlands2 > was calling into /usr/lib32/xorg/modules/dri/i965_dri.so. Should this bug be > moved from DRI/i965 to DRI/i915 or is this the right category? i915 is the name of the kernel driver (and also a 3D driver for old hardware), and i965 is the 3D driver you're using. It's annoying and confusing...
Thanks for making me retry, it doesn't crash anymore with mesa 13.0.0! :) I got some lag spikes that were a bit annoying when trying to reproduce the issue from last year, but I'm not sure yet if that happens everywhere in the game or just in the areas that caused it to crash before. Either way I'm very happy that everything works now!
Great. Thanks a lot for retesting!
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.