Comment # 2
on bug 103486
from Andy Furniss
(In reply to Michel Dänzer from comment #1) > (In reply to Andy Furniss from comment #0) > > R9285, I notice that on both drm-next-4.15-dc and amd-staging-drm-next, > > Which commit exactly of amd-staging-drm-next? I was the version before 11h ago update at time of filing bug, 4ce527eb8bb3c4130f3f6bcd9b4b2efe25fcd534 drm/amdgpu: Remove job->s_entity to avoid keeping reference to stale pointer I first noticed on the version before that, while testing a different bug but don't have the head commit available. I've just updated to what is current now and it's the same. I see loads of warnings at startup, but see these have already been reported. 7781a8c68a6ad110e0d3e11a38357b599ab04da3 drm/amdgpu: remove extra parameter from amdgpu_ttm_bind() v2 > > when using DC, vblank_mode=0 works windowed but not properly full screen. > > > > Tried forcing TearFree from auto to off no difference. > > That's expected; forcing TearFree on works around the problem though. :) Ahh, so it does. I knew auto should = off for me, but it was worth being explicit. > > There is no tearing where it would be expected - but it's not like it's just > > being ignored, a bench mark test will cap fps at 2X refresh rate rather than > > 1X. > > > > Maybe this is expected? > > Definitely not, looks like there's been a regression affecting async flips. > > > > It doesn't happen with a months older DC kernel I have [...] > > Can you try bisecting? Otherwise I'll try next week. I'll try, I just didn't want to start if this was already known/expected.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
