(In reply to Andy Furniss from comment #16)
> (In reply to Andy Furniss from comment #15)
>
> > I only recently started seeing locks - turns out that dri3 was OK for me,
> > but of course it then got disabled by default and I started getting locks.
>
> It seems I was a bit hasty in calling dri3 OK - I can lock if I try long
> enough, just that it takes about 20x longer than dri2.
Looks like the locks were a mesa issue which is now fixed.
I can't point to a commit, but the reason I suspect mesa is that I changed my test case to s/w decode no de-int fps < refresh and could lock/not lock depending on the level of gl output chosen in kodi.
dri2 is still < dri3 - neither lock but 2 glitches occasionally.
Anyway, I guess I am in the wrong bug, sorry for the noise.
(In reply to Andy Furniss from comment #16)
> (In reply to Andy Furniss from comment #15)
>
> > I only recently started seeing locks - turns out that dri3 was OK for me,
> > but of course it then got disabled by default and I started getting locks.
>
> It seems I was a bit hasty in calling dri3 OK - I can lock if I try long
> enough, just that it takes about 20x longer than dri2.
Looks like the locks were a mesa issue which is now fixed.
I can't point to a commit, but the reason I suspect mesa is that I changed my test case to s/w decode no de-int fps < refresh and could lock/not lock depending on the level of gl output chosen in kodi.
dri2 is still < dri3 - neither lock but 2 glitches occasionally.
Anyway, I guess I am in the wrong bug, sorry for the noise.