On Tue, Sep 21, 2010 at 02:15:15AM +0200, Francisco Jerez wrote: > It makes sense for a BO to move after a process has requested > exclusive RW access on it (e.g. because the BO used to be located in > unmappable VRAM and we intercepted the CPU access from the fault > handler). > > If we let the ghost object inherit cpu_writers from the original > object, ttm_bo_release_list() will raise a kernel BUG when the ghost > object is destroyed. This can be reproduced with the nouveau driver on > nv5x. > > Reported-by: Marcin Slusarz <marcin.slusarz@xxxxxxxxx> > Signed-off-by: Francisco Jerez <currojerez@xxxxxxxxxx> After few hours of testing, I can say: Tested-by: Marcin Slusarz <marcin.slusarz@xxxxxxxxx> Thanks, Marcin _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
