Thanks Andrew, but I guess I don't know how to interpret your =
last comment ;-)
Is there something I can test/change? I can't change the value of
"/sys/class/drm/card0/device/pp_dpm_mclk" which is the memclock f=
requency
AFAIK. It always stays at 875Mhz regardless which value I submit. As soon a=
s I
start KDE Plasma I open "konsole" and I see the 875Mhz. So the po=
wer usage is
already high at this point and not after using KDE Plasma for a while.
Executing=20

echo "2" > /sys/class/drm/card0/device/pp_dpm_mclk

e.g. doesn't change the freqency.

Maybe it's a "KDE Plasma + X server" thingy. Users which are usin=
g "KDE Plasma
+ Wayland" seems less frequently affected by the problem. But that's n=
ot really
an option for me as I need screen sharing from time to time via Zoom video
conferencing or Slack and AFAIK that still doesn't work with Wayland (besid=
es
other problems). It's somehow funny that Wayland seems to be less of an iss=
ue
than X...

Maybe it's a X570 chipset + 5700XT thingy. I've no idea. I'm not a driver
developer ;-) I can only try things out like settings or patches (if I get
some). But I guess this is one of the issues that some future commit will m=
aybe
fix "by accident" or it will just stay there forever ;-) If I see=
 how long
other AMD related threads stay around in this bug tracker without solution =
or
some solution after years I currently don't have much hope that there will =
be
any solution for my problem. Hopefully Intel launches a dedicated graphics =
card
sometimes next year. I never had notable issues with Intel hardware and Lin=
ux
within the last few years. It just works ;-)