[kwin_wayland] Freeze when 2nd external monitor is connected

Hello.

I am having an issue with kwin_wayland. Well, at least I think it is it.
When I am using a laptop with 1 external monitor - everything is absolutely fine.
When I plug in 2nd external monitor (3 in total obviously) - the hell breaks loose.
Primary (from laptop) monitor and 1st external monitor switch wallpapers :upside_down_face: (yes - they have different), 2nd external monitor remains blank and the entire system freezes! When i unplug 2 external monitor, system unfreezes and wallpapers return to their rightful owners.
2nd external monitor is the same as the first one - in case it matters.

My setup:

OS: Arch Linux x86_64
Kernel: Linux 6.17.9-arch1-1
Display (MSI3CF0): 3840x2160 @ 1.3x in 27", 160 Hz [External]
Display (NE153QDM-NZ2): 2560x1600 @ 1.3x in 15", 300 Hz [Built-in] *
DE: KDE Plasma 6.5.3
WM: KWin (Wayland)
WM Theme: Breeze
Terminal: konsole 25.8.3
CPU: AMD Ryzen AI 9 HX 370 (24) @ 5.16 GHz
GPU: AMD Radeon 890M Graphics [Integrated]
Memory: 5.63 GiB / 124.92 GiB (5%)
Swap: 0 B / 4.00 GiB (0%)

After unplugging 2nd monitor and running:

journalctl --user -b -u plasma-kwin_wayland.service

i get the following entries repeated many times:

Nov 30 20:56:59 azeroth kwin_wayland[1259]: Atomic modeset test failed! Invalid argument
Nov 30 20:56:59 azeroth kwin_wayland[1259]: Atomic modeset test failed! Invalid argument
Nov 30 20:56:59 azeroth kwin_wayland[1259]: Atomic modeset test failed! Invalid argument
Nov 30 20:56:59 azeroth kwin_wayland[1259]: Atomic modeset test failed! Invalid argument
Nov 30 20:56:59 azeroth kwin_wayland[1259]: Atomic modeset test failed! Invalid argument
Nov 30 20:56:59 azeroth kwin_wayland[1259]: Applying output configuration failed!

Tried also:

coredumpctl -1 info kwin_wayland

but lo luck:

No match found.

I would appreciate any suggestions what would halp me to troubleshoot this!

A freeze is not a freeze.

GPU: AMD Radeon 890M Graphics [Integrated]

The 680M, 780 have also some issues.

Which means I should be rather asking AMD?

You can check the already reported issues:

It could also be https://bugs.kde.org/show_bug.cgi?id=512511
There is a fix for it in review.

Does not look quite like it, but maybe… Thanks.
I’ll wait for the release and keep You posted.