https://bugs.freedesktop.org/show_bug.cgi?id=47306
--- Comment #9 from Christoph Bumiller <[email protected]> 2012-03-15 08:47:30 PDT --- Looks like memory corruption to me now, and comically 0x4071d000 could even be a valid address, just not on the CPU (on nv50 VRAM virtual addresses start at 0x40000000 and are at least 4 KiB aligned). If you want to debug it, I'd either put a watch point on the memory location with gdb once it's available, i.e. when chan->user_private = screen is set in nv50_screen_create, or add lots of debug prints in the nv50 code to bisect the point where it gets modified (usually it shouldn't until screen destruction). Or you could try mesa-8.0 and hope it's gone there. Btw. I hope you're not building with clang, it has issues with the linked-list implementation in gallium, and the fence code uses it ... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- 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
