<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV84] Repeated system crashes under graphics load, E[PFIFO] DMA_PUSHER and lots of E[PGRAPH]" href="https://bugs.freedesktop.org/show_bug.cgi?id=70390#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV84] Repeated system crashes under graphics load, E[PFIFO] DMA_PUSHER and lots of E[PGRAPH]" href="https://bugs.freedesktop.org/show_bug.cgi?id=70390">bug 70390</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>nv84_fence_emit32+0xda/0x1a0 Can you figure out exactly which write this is pointing at? For some of the values, it could be perfectly legitimate to have the 0x406040 value (e.g. the sequence id, or the low bits of the address). (Load up nouveau.ko in gdb, and run "disassemble nv84_fence_emit32". Note that gdb emits offsets in decimal as opposed to the above offsets which are in hex, for maximal confusion.) Ideally we'd have some sort of (optional) command stream validator that made sure that there was no funny business going on. My point about nv50_dma_push is that this is the path that user-submitted command streams take; they don't go through nouveau_bo_wr*, they are written by userspace via mmap'd sections, and then commands are written to the ring to jump to them.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>