The oldest version of Mesa where I don't get this occurring is the one my Linux distribution comes with, 9.2.3. The problem likely existed months before I first tried running the SL viewer on a GIT version of MESA. Do I just set that as a variable in the same console before running the SL process, or is it a compile parameter? If you had started the bisection when you reported this bug, you would have isolated the change introducing the problem for you a long time ago, even if you only tested it once a day. > I crashed my machine 5 times in order to record this.įive iterations of git bisect would go a long way towards isolating the problem. Unfortunately, I'm not able to reproduce anything like what you describe with that apitrace on my machines. > I was however able to do an apitrace, which also produces the crash Also (to preempt another concern you mentioned on IRC), bisecting normally doesn't require any knowledge of the code. > crashing my machine dozens of times, I can't try GIT bisect myself. > Since I have no idea when the issue started happening and I can't risk > Kernel requiring a boot parameter for that as that's not yet default.īTW, in case your Mesa is built with -enable-r600-llvm-compiler, does the problem also occur if you disable the LLVM based shader compiler with the environment variable R600_LLVM=0 for the SL process? > One thing I noticed additionally: I have Radeon DPM enabled, despite my
So I'd appreciate it if someone could make the effort worth it and please test this more in depth, to see where the issue really takes place in the MESA code.įirst of all, please attach the Xorg.0.log file and the output of glxinfo and dmesg. I crashed my machine 5 times in order to record this. Be prepared for a system freeze, and only do this on a machine where it's safe! Also, post a comment here if that link stops working, so I can re-post the trace file if needed. Unpack that somewhere, then run the command "glretrace. This should allow anyone who can't try the Second Life viewer themselves to reproduce the crash.
Kokua viewer bug archive#
As requested, I packed it as an xz archive and uploaded it. I was however able to do an apitrace, which also produces the crash when played back. Since I have no idea when the issue started happening and I can't risk crashing my machine dozens of times, I can't try GIT bisect myself. I brought this up on IRC last night, and was advised to do a GIT bisect or an apitrace. Currently, I don't have any more information on the problem apart from having experienced the described symptoms. If someone has Second Life, please try the deferred lighting system under the 10.1 development version of Mesa. Shadows were disabled and likely not a cause. This does not happen with Mesa 9.2.3, and other Graphics options in the viewer work fine (like "Basic shaders" or "Atmospheric shaders"). Once I did, everything returned to normal. I was barely able to move the mouse pointer and shut the viewer down.
The scene also got covered in pink pixels, meaning it also failed to render correctly. Upon enabling Advanced Lighting Model from Preferences - Graphics, the system froze and the screen started flickering, turning black then recovering every few seconds. I started up the Second Life viewer through it (Kokua 圆4, 3.3, 05:51:00) and logged in. I compiled Mesa with libdrm from their GIT repositories (10.1, commit 2dc35a619c50139d07ad96fc4dfe456e5811c84e).
0 kommentar(er)
