https://bugs.freedesktop.org/show_bug.cgi?id=79823
--- Comment #20 from Ilia Mirkin <[email protected]> --- (In reply to comment #19) > (In reply to comment #18) > > What happens if you add > > > > screen->base.pushbuf->user_priv = NULL > > > > right before the if (screen->base.fence.current) check in > > nv30_screen_destroy? > > No effect. Well, I've been unable to reproduce the "kernel rejected pushbuf" + hang behaviour, although I've only been testing with a NV43. However I did observe the issue that I thought I would observe due to that line not being there... here's a slightly more correct version than my previous suggestion: http://patchwork.freedesktop.org/patch/28050/ And another patch which I think is unlikely to affect what you're seeing, but who knows: http://patchwork.freedesktop.org/patch/28049/ Assuming these don't help, could you run that glxtest application inside valgrind, and let me know if you see any illegal accesses. (Note that the first one of those patches will in fact prevent one such illegal access.) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
