https://bugs.freedesktop.org/show_bug.cgi?id=108613
Bug ID: 108613 Summary: amdgpu.dc=1 + xf86-video-amdgpu: changing to a GPU upscaling resolution resets pp_dpm_mclk Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: tempel.julian@gmail.com
My display doesn't offer upscaling resolutions. However, amdgpu.dc=1 + xf86-video-amdgpu does. When I change the resolution from native (2560x1440) to one of those automatically offered upscaling resolutions (e.g. 1920x1080), the value in "/sys/class/drm/card0/device/pp_dpm_mclk" gets set to default.
I changed it before like this (to prevent flickering with 75Hz with my display):
echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level echo "2" > /sys/class/drm/card0/device/pp_dpm_mclk
The VRAM runs with its maximum clock as long as I don't change resolution. When I change the resolution like described above, the VRAM clock again gets dynamically changed according to load, which introduces nasty flickering in my case.
The desired behavior would be that the change done to pp_dpm_mclk remains untouched when changing to a GPU upscaling resolution.
I haven't checked if pp_dpm_sclk is affected as well. Other powerplay/overdrive/fan settings remain untouched by resolution change.
Using latest linux-amd-staging-drm-next-wip-git kernel. Xorg session
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #1 from Michel Dänzer michel@daenzer.net --- Please attach the corresponding Xorg log file and output of dmesg.
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #2 from tempel.julian@gmail.com --- Created attachment 142327 --> https://bugs.freedesktop.org/attachment.cgi?id=142327&action=edit dmesg.log
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #3 from tempel.julian@gmail.com --- Created attachment 142328 --> https://bugs.freedesktop.org/attachment.cgi?id=142328&action=edit xorg.log
https://bugs.freedesktop.org/show_bug.cgi?id=108613
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #142327|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=108613
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #142328|text/x-log |text/plain mime type| |
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #4 from dwagner jb5sgc1n.nya@20mm.eu --- This is most certainly a duplicate of bug https://bugs.freedesktop.org/show_bug.cgi?id=107141 (which I would really really like to be fixed one day...)
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #5 from tempel.julian@gmail.com --- Yeah, looks like that. It also happens when changing ttys.
https://bugs.freedesktop.org/show_bug.cgi?id=108613
Michel Dänzer michel@daenzer.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED
--- Comment #6 from Michel Dänzer michel@daenzer.net ---
*** This bug has been marked as a duplicate of bug 107141 ***
https://bugs.freedesktop.org/show_bug.cgi?id=108613
--- Comment #7 from bmilreu@gmail.com --- I gave up trying to use my monitor at it's supported 75hz. Locking mclk to fix flickering works only temporarily because it resets at certain events (sleep/wake, resolution changes). Why is this resolved?
dri-devel@lists.freedesktop.org