On Sat, Oct 09, 2010 at 03:53:58PM +0200, Kai Ruhnau wrote: > On 09/18/2010 01:18 PM, Marcin Slusarz wrote: > > On Sat, Sep 18, 2010 at 09:39:21AM +1000, Ben Skeggs wrote: > >> On Fri, 2010-09-17 at 19:43 +0200, Marcin Slusarz wrote: > >>> Hi > >>> Since upgrade from 2.6.35 to 2.6.36-rc3 (nouveau tree) I'm hitting this bug a couple of times a day: > [oops] > >>> this is BUG_ON(atomic_read(&bo->cpu_writers)); > >>> > >>> I'm on b642f07208988270ac402d2548d42dab1d5fec92 "drm/nv50: fix 100c90 write on nva3". > >>> If you have any patches / ideas how to debug this, let me know. > >> I've actually seen this a couple of times. It appears I was incorrectly > >> blaming some patches I have in progress for it, the problem appeared to > >> go away when I reverted them. Perhaps it's more random. I have no > >> current ideas however. > >> > > Heh, Francisco provided the patch on IRC, which seem to fix this bug. > > > > http://annarchy.freedesktop.org/~currojerez/nouveau_cpu_prep_validate.patch > > > > I'm still testing it. > > > > > > Hi > > How is this fix working out? The fix is in Linus' tree, commit 0fbecd400dd0a82d465b3086f209681e8c54cb0f: "drm/ttm: Clear the ghost cpu_writers flag on ttm_buffer_object_transfer" Marcin _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
