Comme=
nt # 48
on bug 11065=
9
from Nicholas Kazlauskas<=
/a>
(In reply to tempel.julian from comment #47)
> I got a new 1440p 144 Hz FreeSync display, and a=
s expected, the issue is
> unchanged with it.
>=20
> With it, I've created a new debug dmesg log for render stutter in Obli=
vion,
> this time with your patch applied to drm-next kernel.
>=20
> Perhaps this could be interesting?
>=20
>=20
> [ 529.556752] [drm:drm_mode_addfb2 [drm]] [FB:79]
> [ 529.557106] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet
> update: crtc=3D47 enabled=3D1 state=3D3
> [ 529.557164] [drm:dc_commit_updates_for_stream [amdgpu]] debug: full
> update issued
> [ 529.564401] [drm:drm_mode_addfb2 [drm]] [FB:86]
> [ 531.420971] [drm:drm_mode_addfb2 [drm]] [FB:95]
> [ 531.459067] [drm:drm_mode_addfb2 [drm]] [FB:96]
> [ 544.144771] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] VRR packet
> update: crtc=3D47 enabled=3D0 state=3D2
> [ 544.145961] [drm:dc_commit_updates_for_stream [amdgpu]] debug: full
> update issued
> [ 544.169447] [drm:drm_mode_addfb2 [drm]] [FB:79]
> [ 544.172953] [drm:drm_mode_addfb2 [drm]] [FB:94]
This is normal behavior for toggling into and out of VRR. I was expecting to
see was a log with hundreds of full updates issued, but since this isn't the
case I think it's something more fundamental with vblank timing though I'm
still not quite sure why it I can't reproduce it in my testing.