http://bugs.freedesktop.org/show_bug.cgi?id=25806
Francisco Jerez <curroje...@riseup.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from Francisco Jerez <curroje...@riseup.net> 2009-12-27
14:25:30 PST ---
(In reply to comment #1)
> Upon further examination, the kernel does seem to have the required logic:
> sending a pushbuffer creates a fence, which is put in bo->sync_obj, which is
> then checked on deletion and if non-null, the buffer is put on a delayed
> destroy list.
>
> However, it seems to be somehow not working.
>
> Maybe fencing is broken on my card? (i.e. the kernel thinks fences are
> signaled
> when they aren't)
> Or possibly fences are being signaled before the vertex shader is finished
> running?
That would be almost unprecedented... it's more likely that some caches in the
GPU aren't being flushed often enough (or maybe the ones in the CPU... a bug in
the kernel PAT code also used to cause the same symptoms, but that's hopefully
already fixed).
I'm marking this as invalid because that's the current policy, unfortunately
we're already aware of too many gallium bugs.
>
> How can I test that fencing is working correctly?
>
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
