Bug 112243

Summary: Micro stuttering in RocketLeague
Product: DRI Reporter: Matthias Heinz <mh>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: not set    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Shader clock and fps directly after boot
none
Shader clock and fps after setting performance level to high
none
Shader clock and fps after setting performance level back to auto none

Description Matthias Heinz 2019-11-11 09:40:48 UTC
Created attachment 145932 [details]
Shader clock and fps directly after boot

Hi,

I'm copying this over from bugzilla.kernel.org, because I think it's the wrong place for amdgpu bug reports.

So everytime I start RocketLeague the first time after a boot I have some kind of  micro stuttering. This happens with my RX550 and on a Vega 56.

A workaround is to set power_dpm_force_performance_level to "high".

Setting it back to "auto" on the RX550 makes the stuttering return. Doing the same thing on the Vega 56 not and the stuttering is gone until the next boot.

I recently found out that I can set power_dpm_force_performance_level to "manual" as well and forbid the lowest clock mode by setting pp_dpm_mclk to "1 2 3".

I'll attach three screenshots that display the shader clock and fps via gallium hud. One directly after a boot, one with performance_level set to "high" and one after resetting it to "auto". All screenshots were made with the Vega 56 and Mesa 18.2.0.

The Mesa version is quiet old, but neither a newer kernel, nor an updated Mesa helps.

Best regards
Matthias
Comment 1 Matthias Heinz 2019-11-11 09:41:36 UTC
Created attachment 145933 [details]
Shader clock and fps after setting performance level to high
Comment 2 Matthias Heinz 2019-11-11 09:42:11 UTC
Created attachment 145934 [details]
Shader clock and fps after setting performance level back to auto
Comment 3 Martin Peres 2019-11-19 10:01:34 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/954.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.