Bug 109462

Summary:	[bisected] Latest amd-staging-drm-next vega10 MCLK stuck on lowest level
Product:	DRI	Reporter:	Bas Nieuwenhuizen <bas>
Component:	DRM/AMDgpu	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium	CC:	alexdeucher, antonh
Version:	XOrg git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Bas Nieuwenhuizen 2019-01-27 02:15:44 UTC

Performance is more than halved in games (used Talos Principle on RADV for bisection) due to the mclk being stuck at 167 MHz.

commit 42a2d4839bc4f095621d259a3ff5401063b914cc (HEAD, refs/bisect/bad)
Author: Evan Quan <evan.quan@amd.com>
Date:   Fri Jan 25 14:09:40 2019 +0800

    drm/amd/powerplay: support Vega10 SOCclk and DCEFclk dpm level settings
    
    Enable SOCclk and DCEFclk dpm level retrieving and setting on Vega10.
    
    Change-Id: Iab35a6cc85cdfcf48f06f7d20b95a52c6feb60d1
    Signed-off-by: Evan Quan <evan.quan@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>

Kernel cmdline has
amdgpu.exp_hw_support=1 log_buf_len=1 amdgpu.sched_hw_submission=64 amdgpu.gpu_recovery=1 amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.cg_mask=0 amdgpu.pg_mask=0 idle=nomwait


and nothing interesting showing up in dmesg.

I can't CC Evan Quan due to lack of bugzilla account.

Comment 1 Alex Deucher 2019-02-03 16:54:23 UTC

Should be fixed with this patch:
https://patchwork.freedesktop.org/patch/282836/

Comment 2 Bas Nieuwenhuizen 2019-02-03 22:12:01 UTC

Can confirm it fixes the issue for me.

Comment 3 Martin Peres 2019-11-19 09:11:44 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/685.

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.