<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#c12">Comment # 12</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:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>[35345.800105] nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 6 [emulator-x86[1371]] get 0x00200f9878 put 0x00200f98d0 ib_get 0x000000ed ib_put 0x000000f6 state 0x80000000 (err: INVALID_CMD) push 0x00406040 This is a long-standing and utterly undiagnosed issue. Somehow an invalid command manages to make it onto the pushbuf. [A command as in a FIFO command, like "BEGIN_NV04" style, not like the actual data being fed to the engine.] There has never been a reproducible way of triggering it. Only seems to happen on tesla GPUs. Either something *very* subtle is going on in mesa, or we're driving the hardware wrong, or... who knows. Search around for 406040 -- tons of bugs open about this.</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>