<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Segfault in pushbuf_kref when running the android emulator (qemu) on nv50" href="https://bugs.freedesktop.org/show_bug.cgi?id=92438#c17">Comment # 17</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Segfault in pushbuf_kref when running the android emulator (qemu) on nv50" href="https://bugs.freedesktop.org/show_bug.cgi?id=92438">bug 92438</a> from <a class="email" href="mailto:gabriele.svelto@gmail.com" title="Gabriele Svelto <gabriele.svelto@gmail.com>"> Gabriele Svelto</a> <pre>Thanks for the tip. From the comments in that bug I should be able to test that patch in the 4.3+ kernels. I'm rolling my own build so I can try that out as soon as I have some spare time. I'll also try mesa 11.0.4 when it will be available in portage (which should be shortly after release). I'd also like to do another experiment: traces gathered with apitrace always end up with the seg-faulting command and always work fine when repeating them - possibly because the last command needs to be fully executed to cause the problem. I'll try gathering a much longer trace using the software render and then try to replay that one with apitrace to see if I can trigger the bug. Alternatively this might be a race condition of some sort (I can see in the trace that there's at least 4 threads calling GL commands); possibly re-executing the trace a lot of times might trigger it sooner or later. I'll report back if I find anything useful.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>