On Mon, Apr 25, 2011 at 10:16:57PM +0100, Chris Wilson wrote: > ... even though it was disabled. A mistake in the handling of fence reuse > caused us to skip the vital delay of waiting for the object to finish > rendering before changing the register. This resulted in us changing the > fence register whilst the bo was active and so causing the blits to > complete using the wrong stride or even the wrong tiling. (Visually the > effect is that small blocks of the screen look like they have been > interlaced). The fix is to wait for the GPU to finish using the memory > region pointed to by the fence before changing it. > > Backported from f48629cff5bf3a0df923ce0314ace584212afbe7.
What is that commit id? I don't see that in Linus's tree. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=34584 > Cc: Andy Whitcroft <a...@canonical.com> > Cc: Daniel Vetter <daniel.vet...@ffwll.ch> > Reviewed-by: Daniel Vetter <daniel.vet...@ffwll.ch> > [Note for 2.6.38-stable, we need to reintroduce the interruptible passing] What do you mean by this? confused, greg k-h _______________________________________________ stable mailing list stable@linux.kernel.org http://linux.kernel.org/mailman/listinfo/stable
