[Bug 207383] [Regression] 5.7 amdgpu/polaris11 gpf: amdgpu_atomic_commit_tail - bugzilla-daemon

From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207383] [Regression] 5.7 amdgpu/polaris11 gpf: amdgpu_atomic_commit_tail
Date: Tue, 28 Jul 2020 07:14:06 +0000	[thread overview]
Message-ID: <bug-207383-2300-wil2Uj89Z5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207383-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207383

--- Comment #105 from Duncan (1i5t5.duncan@cox.net) ---
(In reply to Duncan from comment #102)
> (In reply to Duncan from comment #101)
> > (In reply to Nicholas Kazlauskas from comment #95)
> > > 0001-drm-amd-display-Force-add-all-CRTCs-to-state-when-us.patch
> > 
> > Just booted to 5.8-rc7 with this patched in 
> 
> So far building system updates so heavy cpu load while playing only moderate
> FHD video.  No freezes but I have seen a bit of the predicted judder.
> 
> The 4k30 and 4k60 youtube tests will probably have to wait for tomorrow, tho,
> as I've been up near 24 now...

Still up...  Here's the promised 4k youtube-in-firefox tests.

4k is a bit more stuttery than normal with the patch, but not near as bad as I
expected it to be.  I can normally run 4k60 at 80-85% normal speed with
occasional stutters but without freezing the video entirely until I drop the
speed down again as I often have to do if I try running over that.  With the
patch I was doing 70-75%.  So there's definitely some effect on 4k60. 
Switching to the performance cpufreq governor from my default conservative, as
usual, helps a bit, but not a lot, maybe 5%, tho the frame-freezes seem to
recover a bit better on performance.  In addition to long video freezes at the
full 4k60 100%, even normally I'll sometimes get tab-crashes depending on the
video.  I didn't have any for this test but then I'm so used to not being able
to run at full-speed that I didn't try it for long.

I can normally run 4k30 videos without much problem on default conservative. 
With the patch I was still getting some stuttering at 30fps on conservative,
but it pretty much cleared up with on-demand.  I did just have a tab-crash at
4k30, something I very rarely if ever see normally on 4k30, it normally takes
4k60 to trigger them, so it's definitely affecting it.

But... other than slowing down the usable 4k fps, I'm not seeing any of judder
artifacts on the work (non-video-playing) monitor that I was seeing with the
high system load but relatively low video load build testing with only FHD
video.  That surprised me.  I expected to see more of that with the more
demanding video.  But apparently that's tied to CPU or memory load, not video
load.

But nothing like the problems mnrzk's seeing with the patch, at all.  Both
monitors running fine in text mode, login, startx to plasma, running fine there
too.  Hardware cursor's fine. <shrug>  The only thing I'm seeing is some
slowdown and judder, as described above.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel