https://bugs.kde.org/show_bug.cgi?id=513812
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WAITINGFORINFO Status|REPORTED |NEEDSINFO --- Comment #5 from Zamundaaa <[email protected]> --- The driver is hitting some sort of resource limits: > [ 240.868304] amdgpu 0000:03:00.0: [drm] Adding stream 000000009e4d87f2 to > context failed with err 2! > [ 240.868306] amdgpu 0000:03:00.0: [drm:amdgpu_dm_atomic_check [amdgpu]] > ENABLE: dm_update_crtc_state() failed > [ 240.868448] amdgpu 0000:03:00.0: [drm:amdgpu_dm_atomic_check [amdgpu]] > Atomic check failed with err: -22 "err 2" is DC_NO_CONTROLLER_RESOURCE, I've never seen that before though. It also has another warning, which I'm more familiar with: > DC global validation failure: Bandwidth validation failure (BW and Watermark) > (13) To reduce bandwidth requirements, you could try reducing resolution and refresh rate on one or more screens. Just to be certain, also check if you're using the exact same modes on Xorg. KWin goes for the highest refresh rate by default, which can cause increased bandwidth requirements. One more thing you can test: is your "color accuracy" setting on any of the screens set to "prefer color accuracy"? In theory, KWin should be doing automatic fallbacks, but it's worth trying with all screens set to "prefer efficiency" anyways. Last but not least, the fastest way to find out what to do about this would be a bisect. If you're sure it worked earlier in 6.5, then you could compile KWin 6.5.0 and see if that can enable all screens with the same settings. -- You are receiving this mail because: You are watching all bug changes.
