<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - llvmpipe crash in rendering on Atom" href="https://bugs.freedesktop.org/show_bug.cgi?id=94522#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - llvmpipe crash in rendering on Atom" href="https://bugs.freedesktop.org/show_bug.cgi?id=94522">bug 94522</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>(In reply to Jose Fonseca from <a href="show_bug.cgi?id=94522#c13">comment #13</a>) > I wonder if 0xa8ec01b0 is some sort of funky device memory, or if that > device memory was destroyed before llvmpipe was done. > > After all this is SwapBuffers path. That's very likely, isn't it? comicfans44, can you confirm the dri module used, I would assume it is kms_swrast_dri.so? EGL_LOG_LEVEL=debug environment variable will fish it out. This is triggered by Weston running on bare VT, so likely the DRM-backend (which could be confirmed from Weston's output/logs), and since KMS is involved, I would guess that kms_swrast_dri.so or EGL is using DRM dumb buffers as targets. Well, if it is not using a shadow buffer. I don't know how kms_swrast_dri.so works. Maybe the bug is in the KMS glue code rather than llvmpipe?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>