Bug 506908 - atomic commit failed: Invalid argument when sharing screen
Summary: atomic commit failed: Invalid argument when sharing screen
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (other bugs)
Version First Reported In: 6.3.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-11 12:14 UTC by stellarpower
Modified: 2025-10-16 21:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stellarpower 2025-07-11 12:14:06 UTC
SUMMARY

I have seen the "atomic commit failed: Invalid argument" log message in journalctl countless times previously before a crash, however, I've generally assumed the NVidia drivers were at fault. To narrow down the issues I've now pulled that card out and replaced with an AMD GPU (there is also an inbuilt VGA - it's a server mobo), so that can be ruled out. Most of my stability problems however are still present.

I have just performed a killswitch and rebooted with kernel 6.15 and then logged in to test first thing if screensharing was working properly through a video call in Chromium. Everything proceeded to work, I can share my screen, although I think the mouse was not moving properly over one of the displays, I will retest in a minute to see if reproducible. But I see thousands of lines like the below in the journal and given usually when I see an atomic commit fail it's around something serious that kills the compositor or makes it unusable, am assuming is something that would want to be fixed:

```


Jul 11 12:44:34 localhost kwin_wayland[7267]: kwin_wayland_drm: atomic commit failed: Invalid argument
Jul 11 12:44:34 localhost kernel: ------------[ cut here ]------------
Jul 11 12:44:34 localhost kernel: WARNING: CPU: 21 PID: 7310 at drivers/dma-buf/dma-buf.c:1527 dma_buf_vmap+0xd1/0xf0
Jul 11 12:44:34 localhost kernel: Modules linked in: xt_MASQUERADE xt_tcpudp xt_mark nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject snd_seq_dummy rfcomm snd_hrtimer snd_seq af_packet tun iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 qrtr cmac algif_hash algif_skcipher af_alg iptable_filter bnep binfmt_misc nls_iso8859_1 nls_cp437 ipmi_ssif vfat fat amdgpu amd_atl intel_rapl_msr intel_rapl_common iwlmvm amd64_edac edac_mce_amd snd_hda_codec_hdmi amdxcp gpu_sched snd_usb_audio snd_hda_intel drm_panel_backlight_quirks mac80211 snd_intel_dspcfg drm_buddy drm_exec snd_intel_sdw_acpi libarc4 snd_usbmidi_lib drm_suballoc_helper snd_hda_codec snd_ump btusb drm_ttm_helper snd_hda_core snd_rawmidi btrtl ttm eeepc_wmi snd_hwdep snd_seq_device btintel ixgbe asus_wmi drm_display_helper btbcm jc42 platform_profile iwlwifi btmtk snd_pcm kvm_amd cec battery xfrm_algo ee1004 mdio_devres snd_timer sparse_keymap rc_core cfg80211 bluetooth snd kvm mc video libphy wmi_bmof soundcore pcspkr joydev crc16 irqbypass rfkill acpi_ipmi mdio
Jul 11 12:44:34 localhost kernel:  i2c_piix4 dca i2c_smbus k10temp ipmi_si ipmi_devintf ipmi_msghandler tiny_power_button loop nvme_fabrics fuse efi_pstore configfs ip_tables x_tables hid_generic usbhid zfs(POE) spl(OE) ahci libahci libata polyval_clmulni polyval_generic ghash_clmulni_intel sd_mod sha512_ssse3 scsi_dh_emc sha256_ssse3 xhci_pci scsi_dh_rdac xhci_hcd scsi_dh_alua sha1_ssse3 nvme sg aesni_intel crypto_simd mxm_wmi scsi_mod nvme_core ast cryptd nvme_keyring ccp usbcore i2c_algo_bit nvme_auth scsi_common sp5100_tco wmi button btrfs blake2b_generic xor raid6_pq dm_mirror dm_region_hash dm_log dm_mod br_netfilter bridge stp llc nf_tables msr i2c_dev nfnetlink efivarfs dmi_sysfs
Jul 11 12:44:34 localhost kernel: CPU: 21 UID: 1000 PID: 7310 Comm: VGA-1 Tainted: P        W  OE       6.15.2-1.0.6.sr20250601-default #1 PREEMPT(voluntary) openSUSE Tumbleweed (unreleased)  47768c69b75363f4b954e25a6193200b3e5ae815
Jul 11 12:44:34 localhost kernel: Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Jul 11 12:44:34 localhost kernel: Hardware name: ASUS System Product Name/Pro WS WRX80E-SAGE SE WIFI, BIOS 1602 09/04/2024
Jul 11 12:44:34 localhost kernel: RIP: 0010:dma_buf_vmap+0xd1/0xf0
Jul 11 12:44:34 localhost kernel: Code: 83 c4 18 5b 41 5c 5d e9 8d 6c 39 00 83 c0 01 89 43 28 48 85 c9 74 1c 48 8b 43 30 48 8b 53 38 49 89 04 24 49 89 54 24 08 eb c4 <0f> 0b b8 ea ff ff ff eb bd 0f 0b 0f 0b 0f 0b eb b5 b8 ea ff ff ff
Jul 11 12:44:34 localhost kernel: RSP: 0018:ffffd1a884b579d8 EFLAGS: 00010246
Jul 11 12:44:34 localhost kernel: RAX: ffffffffa843d7f0 RBX: 0000000000000000 RCX: ffffffffa844a520
Jul 11 12:44:34 localhost kernel: RDX: ffff8f1926b85040 RSI: ffff8f18957344c8 RDI: 0000000000000000
Jul 11 12:44:34 localhost kernel: RBP: ffffd1a884b57a00 R08: 00000000000000c0 R09: 0000000000000000
Jul 11 12:44:34 localhost kernel: R10: ffffd1a884b57a68 R11: 0000000000000040 R12: ffff8f18957344c8
Jul 11 12:44:34 localhost kernel: R13: ffff8f189ff08000 R14: ffff8f18957344c8 R15: ffff8f18957344c8
Jul 11 12:44:34 localhost kernel: FS:  00007f9eb17fa6c0(0000) GS:ffff8f3794830000(0000) knlGS:0000000000000000
Jul 11 12:44:34 localhost kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 11 12:44:34 localhost kernel: CR2: 000004f4026b3000 CR3: 000000033d701000 CR4: 0000000000350ef0
Jul 11 12:44:34 localhost kernel: Call Trace:
Jul 11 12:44:34 localhost kernel:  <TASK>
Jul 11 12:44:34 localhost kernel:  drm_gem_shmem_vmap+0x2d/0x1b0
Jul 11 12:44:34 localhost kernel:  drm_gem_vmap+0x22/0x50
Jul 11 12:44:34 localhost kernel:  drm_gem_vmap_unlocked+0x2a/0x50
Jul 11 12:44:34 localhost kernel:  drm_gem_fb_vmap+0x41/0x120
Jul 11 12:44:34 localhost kernel:  drm_atomic_helper_prepare_planes+0x17a/0x210
Jul 11 12:44:34 localhost kernel:  drm_atomic_helper_commit+0x78/0x140
Jul 11 12:44:34 localhost kernel:  drm_mode_atomic_ioctl+0xaa3/0xd10
Jul 11 12:44:34 localhost kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
Jul 11 12:44:34 localhost kernel:  drm_ioctl_kernel+0xa6/0x100
Jul 11 12:44:34 localhost kernel:  drm_ioctl+0x256/0x520
Jul 11 12:44:34 localhost kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? switch_fpu_return+0x4e/0xd0
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90
Jul 11 12:44:34 localhost kernel:  __x64_sys_ioctl+0x97/0xc0
Jul 11 12:44:34 localhost kernel:  do_syscall_64+0x82/0x830
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? hrtimer_cancel+0x21/0x40
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? futex_wait+0x7b/0x110
Jul 11 12:44:34 localhost kernel:  ? __pfx_hrtimer_wakeup+0x10/0x10
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? __rseq_handle_notify_resume+0xa5/0x4b0
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? __x64_sys_futex+0x10b/0x1c0
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? switch_fpu_return+0x4e/0xd0
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? syscall_exit_to_user_mode+0x37/0x1d0
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? do_syscall_64+0x8e/0x830
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? syscall_exit_to_user_mode+0x37/0x1d0
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? syscall_exit_to_user_mode+0x37/0x1d0
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  ? do_syscall_64+0x8e/0x830
Jul 11 12:44:34 localhost kernel:  ? srso_return_thunk+0x5/0x5f
Jul 11 12:44:34 localhost kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jul 11 12:44:34 localhost kernel: RIP: 0033:0x7f9ecdb1916f
Jul 11 12:44:34 localhost kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
Jul 11 12:44:34 localhost kernel: RSP: 002b:00007f9eb17f95d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jul 11 12:44:34 localhost kernel: RAX: ffffffffffffffda RBX: 00007f9e980013d0 RCX: 00007f9ecdb1916f
Jul 11 12:44:34 localhost kernel: RDX: 00007f9eb17f96c0 RSI: 00000000c03864bc RDI: 0000000000000013
Jul 11 12:44:34 localhost kernel: RBP: 00007f9eb17f96c0 R08: 0000000000000058 R09: 00007f9e98001fc0
Jul 11 12:44:34 localhost kernel: R10: 00007f9e98001fc0 R11: 0000000000000246 R12: 00000000c03864bc
Jul 11 12:44:34 localhost kernel: R13: 0000000000000013 R14: 00007f9e98001fc0 R15: 00007f9e8800a2e0
Jul 11 12:44:34 localhost kernel:  </TASK>
Jul 11 12:44:34 localhost kernel: ---[ end trace 0000000000000000 ]---
Jul 11 12:44:34 localhost kernel: ------------[ cut here ]------------


# Repeated for each core...

# And finally:

Jul 11 12:45:04 localhost chromium-browser[8747]: 'loop->recurse > 0' failed at ../src/pipewire/thread-loop.c:425 pw_thread_loop_wait()
Jul 11 12:45:04 localhost kded6[7478]: Service  ":1.232" unregistered
Jul 11 12:45:04 localhost kwin_wayland[7267]: kwin_core: XCB error: 3 (BadWindow), sequence: 1846, resource id: 0, major code: 129 (SHAPE), minor code: 8 (GetRectangles)
Jul 11 12:45:07 localhost chromium-browser[8747]: [8742:8772:0711/124507.129786:ERROR:tent/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
 11 12:45:07 localhost kded6[7478]: Service  ":1.230" unregistered
Jul 11 12:45:07 localhost systemd[3846]: app-org.chromium.Chromium-8742.scope: Consumed 4.276s CPU time.
Jul 11 12:45:07 localhost systemd[3846]: app-\x2fusr\x2fbin\x2fchromium\x2dbrowser@ec41c35c3e0c494baf6ffb0a6b4b0ff4.service: Consumed 15.944s CPU time.

```

Not sure whether the driver/kernel graphics stack or KWin would be the culprits here, especially as I have seen other more serious issues with the amdgpu driver (which was suprising me as I thought non-Nvidia cards were generally stable in wayland by now).


SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed-Slowroll 20250601
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.15.2-1.0.6.sr20250601-default (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen Threadripper PRO 3955WX 16-Cores
Memory: 125.6 GiB of RAM
Graphics Processor 1: AMD Radeon RX 580 2048SP
Graphics Processor 2: llvmpipe

ADDITIONAL INFORMATION

Working through a list of journal entries, so appreciate this might not be sufficient info; let me know what else would be useful!

Thanks
Comment 1 stellarpower 2025-07-11 12:18:12 UTC
Note: Realised it was the VGA screen I was sharing at the time and a monitor on the AMD card where I think the mouse was not working properly. However as I saw "DMA" my mind immediately went to the discrete card. I could see the cursor fine within my shared screen from the shared monitor. Afraid I don't remember exactly what happened at the time.
Comment 2 Zamundaaa 2025-10-16 21:48:10 UTC
Hmm, "atomic commit failed" is almost always a driver issue. In your case it's certain because of the traces in the log; you can report this at https://gitlab.freedesktop.org/drm/amd/-/issues

You're not supposed to see "atomic commit failed" warnings on NVidia either, so if you still see them, feel free to create a new bug report with drm debug logs attached (https://invent.kde.org/plasma/kwin/-/wikis/Debugging/Debugging-DRM-issues)