https://bugs.kde.org/show_bug.cgi?id=471517
--- Comment #19 from Stefan Springer <stefansp...@gmail.com> --- (In reply to Zamundaaa from comment #18) > Did you actually revert the commit and test that, and what's your second > GPU? Because if you do have mismatching stride, then your output would've > been completely unusable before the commit. And if you don't, then the > commit doesn't change anything. Long story short: I can now say with certainty that my specific issue is not KDE related. Sorry for making such a fuzz! So after reverting the patch, things seemed fine for two days and a reboot, but then the issue got triggered again out of seemingly nowhere. Following some more digging around, and even trying an old 5.19 LTS kernel, I decided to create a new, blank user account to see if it also exhibits the issue. Surprisingly, it wasn't present on a fresh acc. with default settings. I step-wise reconstructed the settings of my main account to see if it reoccurred. The trigger was touching mclk_od on 6800XT (and probably also RX 470 when thinking about the weird behavior on my other PC; for some reason [HBM?] Vega 56 is fine), even if it's just a change of 5Mhz up or down, it will reliably trigger the problem. I manually played around with the pp_od_clk_voltage sysfs interface to confirm this, and ultimately disabled the part of my OC script that adjusts mclk; now everything works. Multiple reboots, logging off and on again, the gsync pendulum at any arbitrary refresh rate, etc… I was using a dual-monitor 144Hz config before, then, after moving, single monitor with 144Hz over HDMI because I grabbed the wrong cable, and only when I finally got around to getting a DP cable (3 in fact, since it looked like I got two defective ones at first), which allowed me to drive my monitor at 165Hz (still single-monitor use now), the issue was unmasked. That's what originally had me sifting through a month worth of system updates and commits. Currently, when looking at the AMDGPU issue tracker, there is fundamental restructuring going on in DC (Display Core) code, with issues around mclk handling being present (It actually broke badly in Kernel 6.4, such that desktop RDNA2 simply won't increase mclk at all, for some OOTB, for others with specific monitors/resolutions/refresh rates and for others once touching mclk_od), aswell as problems with calculating the required bandwidth for a given monitor config (res, hz, multi-display, VRR), so this seems related to that. -- You are receiving this mail because: You are watching all bug changes.
