You are not logged in.

Pages: 1

#1 2025-11-08 00:15:28

eomanis
Member
Registered: 2013-04-17
Posts: 64

Discord sending out video crashes amdgpu and Desktop session

Edit: Upstream issue report

Since about a week ago my desktop session crashes as soon as Discord starts sending out my own video to other video chat participants.

Meaning, I am safe as long as either I do not enable my camera, or nobody else is in the video chat and I am only viewing my own video.

I know Discord worked on 2025-10-27.

Using the Arch Linux Archive I went "back in time" to a point in time when Discord still worked, but Discord kept crashing my session:

- Crash: 2025-11-07, mesa-1:25.2.6-1, linux-6.17.7.arch1-1
- Crash: 2025-10-25, mesa-1:25.2.5-2, linux-6.17.5.arch1-1
- Crash: 2025-10-16, mesa-1:25.2.4-2, linux-6.17.2.arch1-1

In all tests this is the same current Flatpak Discord version (com.discordapp.Discord from flathub, Version 0.0.113).
I could not downgrade Discord since it updates itself; Discord version is Discord Stable 466058 (0a5fa0b).

This leaves me with two possible causes:
- Discord has, with a recent update, exposed a (linux kernel driver?) bug
- Hardware fault

Anyone else having this problem?

System information

## Report details
- **Date generated:**                              2025-11-08 01:02:41

## Hardware Information:
- **Hardware Model:**                              Gigabyte Technology Co., Ltd. X570 AORUS ELITE
- **Memory:**                                      32.0 GiB
- **Processor:**                                   AMD Ryzen™ 7 5700X × 16
- **Graphics:**                                    AMD Radeon™ RX 480 Graphics
- **Disk Capacity:**                               2.0 TB

## Software Information:
- **Firmware Version:**                            F40h
- **OS Name:**                                     Arch Linux
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               49
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.17.7-arch1-1

Kernel log excerpt

[   76.878018] thesystem kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* [CRTC:61:crtc-0] flip_done timed out
[   78.926027] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: [drm] *ERROR* [CRTC:61:crtc-0] hw_done or flip_done timed out
[   89.166060] thesystem kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* flip_done timed out
[   89.166492] thesystem kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* [CRTC:61:crtc-0] commit wait timed out
[   99.406324] thesystem kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* flip_done timed out
[   99.406776] thesystem kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* [PLANE:56:plane-5] commit wait timed out
[  109.646071] thesystem kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* flip_done timed out
[  109.646453] thesystem kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* [PLANE:59:plane-6] commit wait timed out
[  109.901191] thesystem kernel: ------------[ cut here ]------------
[  109.901272] thesystem kernel: WARNING: CPU: 1 PID: 890 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:9598 amdgpu_dm_atomic_commit_tail+0x36f6/0x3780 [amdgpu]
[  109.901293] thesystem kernel: Modules linked in: rfcomm snd_hrtimer nls_utf8 cifs cifs_arc4 nls_ucs2_utils rdma_cm iw_cm ib_cm ib_core cifs_md4 dns_resolver netfs uhid cmac nct6775_core hwmon_vid algif_hash algif_skcipher af_alg bnep amdgpu amdxcp uvcvideo snd_hda_codec_atihdmi gpu_sched btusb snd_hda_codec_hdmi amd_atl videobuf2_vmalloc intel_rapl_msr btrtl drm_panel_backlight_quirks uvc btintel drm_buddy intel_rapl_common videobuf2_memops snd_hda_intel btbcm drm_exec amd64_edac videobuf2_v4l2 drm_suballoc_helper btmtk wmi_bmof videobuf2_common gigabyte_wmi drm_ttm_helper snd_usb_audio snd_hda_codec bluetooth videodev kvm_amd ttm snd_usbmidi_lib snd_hda_core snd_ump rapl joydev mousedev sp5100_tco drm_display_helper snd_intel_dspcfg snd_virtuoso pcspkr i2c_piix4 k10temp mc snd_intel_sdw_acpi cec snd_oxygen_lib i2c_smbus snd_mpu401_uart igb snd_hwdep video snd_rawmidi i2c_algo_bit ptp pps_core snd_pcm dca wmi bridge stp llc mac_hid cfg80211 rfkill vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) kvm irqbypass snd_seq_dummy uinput snd_seq_oss
[  109.901357] thesystem kernel:  snd_seq_midi_event snd_seq snd_seq_device snd_timer snd soundcore cuse i2c_dev sg crypto_user loop nfnetlink ip_tables x_tables dm_crypt encrypted_keys trusted asn1_encoder tee dm_mod nvme sr_mod cdrom polyval_clmulni nvme_core ghash_clmulni_intel aesni_intel nvme_keyring ccp nvme_auth vfat fat uas usb_storage xfs
[  109.901377] thesystem kernel: CPU: 1 UID: 0 PID: 890 Comm: systemd-logind Tainted: G           OE       6.17.7-arch1-1 #1 PREEMPT(full)  487c2a7c3ba80b17aa21e17ff916d191154be38f
[  109.901400] thesystem kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[  109.901418] thesystem kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F40h 08/12/2025
[  109.901436] thesystem kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x36f6/0x3780 [amdgpu]
[  109.901463] thesystem kernel: Code: ff ff 89 8d 98 fe ff ff c7 85 84 fe ff ff 04 00 00 00 e9 34 d5 ff ff 31 f6 e9 c8 f5 ff ff 80 8d a0 fe ff ff 80 e9 0a fe ff ff <0f> 0b e9 f7 f8 ff ff 0f 0b 49 8d 84 24 60 5b 04 00 c6 85 28 fe ff
[  109.901485] thesystem kernel: RSP: 0018:ffffd53b41bdf328 EFLAGS: 00010002
[  109.901503] thesystem kernel: RAX: 0000000000000002 RBX: 0000000000000296 RCX: ffff8ea8c5b7e118
[  109.901521] thesystem kernel: RDX: 0000000000000001 RSI: 0000000000000286 RDI: ffff8ea90fb00180
[  109.901544] thesystem kernel: RBP: ffffd53b41bdf588 R08: ffffd53b41bdf294 R09: ffff8ea946020000
[  109.901561] thesystem kernel: R10: 0000000000000000 R11: ffff8ea8da95f500 R12: ffff8ea8c5b7e118
[  109.901578] thesystem kernel: R13: ffff8ea90fb00010 R14: ffff8ea8c5b7e000 R15: ffff8ea9aef45c00
[  109.901596] thesystem kernel: FS:  00007fd24a2c7900(0000) GS:ffff8eb036549000(0000) knlGS:0000000000000000
[  109.901616] thesystem kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  109.901636] thesystem kernel: CR2: 00007fcb1692a1c0 CR3: 000000014c0ff000 CR4: 0000000000f50ef0
[  109.901649] thesystem kernel: PKRU: 55555554
[  109.901672] thesystem kernel: Call Trace:
[  109.901689] thesystem kernel:  <TASK>
[  109.901706] thesystem kernel:  ? __mutex_lock_slowpath+0x1/0x10
[  109.901727] thesystem kernel:  commit_tail+0xb1/0x140
[  109.901747] thesystem kernel:  drm_atomic_helper_commit+0x13c/0x180
[  109.901766] thesystem kernel:  drm_atomic_commit+0xb1/0xe0
[  109.901786] thesystem kernel:  ? __pfx___drm_printfn_info+0x10/0x10
[  109.901807] thesystem kernel:  drm_client_modeset_commit_atomic+0x1ec/0x230
[  109.901830] thesystem kernel:  drm_client_modeset_commit_locked+0x58/0x160
[  109.901845] thesystem kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked+0x55/0xd0
[  109.901863] thesystem kernel:  drm_fb_helper_set_par+0x2d/0x40
[  109.901880] thesystem kernel:  fb_set_var+0x23c/0x430
[  109.901900] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.901929] thesystem kernel:  ? __dquot_free_space+0x2f9/0x310
[  109.901949] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.901966] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.901981] thesystem kernel:  fbcon_blank+0x271/0x330
[  109.901996] thesystem kernel:  do_unblank_screen+0xc8/0x1b0
[  109.902088] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902115] thesystem kernel:  ? down+0x1e/0x70
[  109.902132] thesystem kernel:  vt_ioctl+0x583/0x1450
[  109.902147] thesystem kernel:  tty_ioctl+0xe4/0x9a0
[  109.902167] thesystem kernel:  ? __seccomp_filter+0x41/0x4e0
[  109.902187] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902203] thesystem kernel:  __x64_sys_ioctl+0x97/0xe0
[  109.902224] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902236] thesystem kernel:  do_syscall_64+0x81/0x970
[  109.902261] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902275] thesystem kernel:  ? kmem_cache_free+0x490/0x4d0
[  109.902289] thesystem kernel:  ? __x64_sys_close+0x3d/0x80
[  109.902303] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902315] thesystem kernel:  ? __x64_sys_close+0x3d/0x80
[  109.902329] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902341] thesystem kernel:  ? do_syscall_64+0x81/0x970
[  109.902357] thesystem kernel:  ? mntput_no_expire+0x49/0x2d0
[  109.902375] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902391] thesystem kernel:  ? __dentry_kill+0x183/0x190
[  109.902408] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902424] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902441] thesystem kernel:  ? page_counter_uncharge+0x4a/0x90
[  109.902458] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902469] thesystem kernel:  ? drain_stock+0x7d/0xa0
[  109.902486] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902503] thesystem kernel:  ? refill_stock+0x1c1/0x200
[  109.902517] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902529] thesystem kernel:  ? obj_cgroup_uncharge_pages+0x5d/0xe0
[  109.902551] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902565] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902577] thesystem kernel:  ? security_capable+0x7d/0x1a0
[  109.902596] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902612] thesystem kernel:  ? capable+0x32/0x60
[  109.902627] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902641] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902656] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902672] thesystem kernel:  ? tty_mode_ioctl+0x67a/0x6e0
[  109.902702] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902723] thesystem kernel:  ? tty_ioctl+0x156/0x9a0
[  109.902750] thesystem kernel:  ? __seccomp_filter+0x41/0x4e0
[  109.902764] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902774] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902788] thesystem kernel:  ? __x64_sys_ioctl+0x97/0xe0
[  109.902812] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902824] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902838] thesystem kernel:  ? do_syscall_64+0x81/0x970
[  109.902851] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902865] thesystem kernel:  ? do_syscall_64+0x81/0x970
[  109.902879] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.902891] thesystem kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[  109.902908] thesystem kernel: RIP: 0033:0x7fd249b1674d
[  109.902922] thesystem kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
[  109.902940] thesystem kernel: RSP: 002b:00007fffd1f04030 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[  109.902950] thesystem kernel: RAX: ffffffffffffffda RBX: 000055600212b5e0 RCX: 00007fd249b1674d
[  109.902969] thesystem kernel: RDX: 0000000000000000 RSI: 0000000000004b3a RDI: 000000000000000c
[  109.902979] thesystem kernel: RBP: 00007fffd1f04080 R08: 9962244cf250595b R09: 00000000000001e0
[  109.902993] thesystem kernel: R10: 00000000000001e1 R11: 0000000000000246 R12: 000000000000000c
[  109.903022] thesystem kernel: R13: 0000556002110640 R14: 000055600210de90 R15: 00005560021191b0
[  109.903042] thesystem kernel:  </TASK>
[  109.903057] thesystem kernel: ---[ end trace 0000000000000000 ]---
[  109.903071] thesystem kernel: ------------[ cut here ]------------
[  109.903081] thesystem kernel: WARNING: CPU: 1 PID: 890 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8984 amdgpu_dm_atomic_commit_tail+0x3721/0x3780 [amdgpu]
[  109.903098] thesystem kernel: Modules linked in: rfcomm snd_hrtimer nls_utf8 cifs cifs_arc4 nls_ucs2_utils rdma_cm iw_cm ib_cm ib_core cifs_md4 dns_resolver netfs uhid cmac nct6775_core hwmon_vid algif_hash algif_skcipher af_alg bnep amdgpu amdxcp uvcvideo snd_hda_codec_atihdmi gpu_sched btusb snd_hda_codec_hdmi amd_atl videobuf2_vmalloc intel_rapl_msr btrtl drm_panel_backlight_quirks uvc btintel drm_buddy intel_rapl_common videobuf2_memops snd_hda_intel btbcm drm_exec amd64_edac videobuf2_v4l2 drm_suballoc_helper btmtk wmi_bmof videobuf2_common gigabyte_wmi drm_ttm_helper snd_usb_audio snd_hda_codec bluetooth videodev kvm_amd ttm snd_usbmidi_lib snd_hda_core snd_ump rapl joydev mousedev sp5100_tco drm_display_helper snd_intel_dspcfg snd_virtuoso pcspkr i2c_piix4 k10temp mc snd_intel_sdw_acpi cec snd_oxygen_lib i2c_smbus snd_mpu401_uart igb snd_hwdep video snd_rawmidi i2c_algo_bit ptp pps_core snd_pcm dca wmi bridge stp llc mac_hid cfg80211 rfkill vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) kvm irqbypass snd_seq_dummy uinput snd_seq_oss
[  109.903124] thesystem kernel:  snd_seq_midi_event snd_seq snd_seq_device snd_timer snd soundcore cuse i2c_dev sg crypto_user loop nfnetlink ip_tables x_tables dm_crypt encrypted_keys trusted asn1_encoder tee dm_mod nvme sr_mod cdrom polyval_clmulni nvme_core ghash_clmulni_intel aesni_intel nvme_keyring ccp nvme_auth vfat fat uas usb_storage xfs
[  109.903140] thesystem kernel: CPU: 1 UID: 0 PID: 890 Comm: systemd-logind Tainted: G        W  OE       6.17.7-arch1-1 #1 PREEMPT(full)  487c2a7c3ba80b17aa21e17ff916d191154be38f
[  109.903157] thesystem kernel: Tainted: [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[  109.903171] thesystem kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS ELITE/X570 AORUS ELITE, BIOS F40h 08/12/2025
[  109.903186] thesystem kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3721/0x3780 [amdgpu]
[  109.903203] thesystem kernel: Code: 0b e9 f7 f8 ff ff 0f 0b 49 8d 84 24 60 5b 04 00 c6 85 28 fe ff ff 00 48 89 85 30 fe ff ff e9 66 cf ff ff 0f 0b e9 b1 cf ff ff <0f> 0b e9 eb f8 ff ff 48 c7 85 20 fe ff ff 00 00 00 00 48 c7 85 f0
[  109.903220] thesystem kernel: RSP: 0018:ffffd53b41bdf328 EFLAGS: 00010082
[  109.903237] thesystem kernel: RAX: 0000000000000001 RBX: 0000000000000296 RCX: ffff8ea8c5b7e118
[  109.903254] thesystem kernel: RDX: 0000000000000001 RSI: 0000000000000286 RDI: ffff8ea90fb00180
[  109.903266] thesystem kernel: RBP: ffffd53b41bdf588 R08: ffffd53b41bdf294 R09: ffff8ea946020000
[  109.903280] thesystem kernel: R10: 0000000000000000 R11: ffff8ea8da95f500 R12: ffff8ea8c5b7e118
[  109.903292] thesystem kernel: R13: ffff8ea90fb00010 R14: ffff8ea8c5b7e000 R15: ffff8ea9aef45c00
[  109.903302] thesystem kernel: FS:  00007fd24a2c7900(0000) GS:ffff8eb036549000(0000) knlGS:0000000000000000
[  109.903316] thesystem kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  109.903331] thesystem kernel: CR2: 00007fcb1692a1c0 CR3: 000000014c0ff000 CR4: 0000000000f50ef0
[  109.903343] thesystem kernel: PKRU: 55555554
[  109.903355] thesystem kernel: Call Trace:
[  109.903372] thesystem kernel:  <TASK>
[  109.903387] thesystem kernel:  ? __mutex_lock_slowpath+0x1/0x10
[  109.903399] thesystem kernel:  commit_tail+0xb1/0x140
[  109.903480] thesystem kernel:  drm_atomic_helper_commit+0x13c/0x180
[  109.903494] thesystem kernel:  drm_atomic_commit+0xb1/0xe0
[  109.903511] thesystem kernel:  ? __pfx___drm_printfn_info+0x10/0x10
[  109.903527] thesystem kernel:  drm_client_modeset_commit_atomic+0x1ec/0x230
[  109.903539] thesystem kernel:  drm_client_modeset_commit_locked+0x58/0x160
[  109.903552] thesystem kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked+0x55/0xd0
[  109.903564] thesystem kernel:  drm_fb_helper_set_par+0x2d/0x40
[  109.903576] thesystem kernel:  fb_set_var+0x23c/0x430
[  109.903588] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903601] thesystem kernel:  ? __dquot_free_space+0x2f9/0x310
[  109.903617] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903629] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903644] thesystem kernel:  fbcon_blank+0x271/0x330
[  109.903658] thesystem kernel:  do_unblank_screen+0xc8/0x1b0
[  109.903670] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903682] thesystem kernel:  ? down+0x1e/0x70
[  109.903696] thesystem kernel:  vt_ioctl+0x583/0x1450
[  109.903710] thesystem kernel:  tty_ioctl+0xe4/0x9a0
[  109.903722] thesystem kernel:  ? __seccomp_filter+0x41/0x4e0
[  109.903736] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903748] thesystem kernel:  __x64_sys_ioctl+0x97/0xe0
[  109.903763] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903775] thesystem kernel:  do_syscall_64+0x81/0x970
[  109.903787] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903803] thesystem kernel:  ? kmem_cache_free+0x490/0x4d0
[  109.903820] thesystem kernel:  ? __x64_sys_close+0x3d/0x80
[  109.903833] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903848] thesystem kernel:  ? __x64_sys_close+0x3d/0x80
[  109.903863] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903872] thesystem kernel:  ? do_syscall_64+0x81/0x970
[  109.903890] thesystem kernel:  ? mntput_no_expire+0x49/0x2d0
[  109.903901] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903913] thesystem kernel:  ? __dentry_kill+0x183/0x190
[  109.903925] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903937] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903951] thesystem kernel:  ? page_counter_uncharge+0x4a/0x90
[  109.903964] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.903980] thesystem kernel:  ? drain_stock+0x7d/0xa0
[  109.903992] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904015] thesystem kernel:  ? refill_stock+0x1c1/0x200
[  109.904038] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904053] thesystem kernel:  ? obj_cgroup_uncharge_pages+0x5d/0xe0
[  109.904067] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904079] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904092] thesystem kernel:  ? security_capable+0x7d/0x1a0
[  109.904103] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904120] thesystem kernel:  ? capable+0x32/0x60
[  109.904132] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904149] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904158] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904172] thesystem kernel:  ? tty_mode_ioctl+0x67a/0x6e0
[  109.904186] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904196] thesystem kernel:  ? tty_ioctl+0x156/0x9a0
[  109.904208] thesystem kernel:  ? __seccomp_filter+0x41/0x4e0
[  109.904217] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904227] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904241] thesystem kernel:  ? __x64_sys_ioctl+0x97/0xe0
[  109.904253] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904263] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904273] thesystem kernel:  ? do_syscall_64+0x81/0x970
[  109.904283] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904293] thesystem kernel:  ? do_syscall_64+0x81/0x970
[  109.904305] thesystem kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[  109.904317] thesystem kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[  109.904329] thesystem kernel: RIP: 0033:0x7fd249b1674d
[  109.904339] thesystem kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
[  109.904349] thesystem kernel: RSP: 002b:00007fffd1f04030 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[  109.904360] thesystem kernel: RAX: ffffffffffffffda RBX: 000055600212b5e0 RCX: 00007fd249b1674d
[  109.904371] thesystem kernel: RDX: 0000000000000000 RSI: 0000000000004b3a RDI: 000000000000000c
[  109.904383] thesystem kernel: RBP: 00007fffd1f04080 R08: 9962244cf250595b R09: 00000000000001e0
[  109.904392] thesystem kernel: R10: 00000000000001e1 R11: 0000000000000246 R12: 000000000000000c
[  109.904400] thesystem kernel: R13: 0000556002110640 R14: 000055600210de90 R15: 00005560021191b0
[  109.904408] thesystem kernel:  </TASK>
[  109.904420] thesystem kernel: ---[ end trace 0000000000000000 ]---
[  111.080014] thesystem kernel: rfkill: input handler disabled
(...)
[  208.333790] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: GPU fault detected: 146 0x0e203e0c
[  208.334255] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu:  Process Discord pid 9861 thread exe:cs0 pid 10147
[  208.334521] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001007C4
[  208.334789] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0603E00C
[  208.335006] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: VM fault (0x0c, vmid 3, pasid 32780) at page 1050564, read from 'VCE0' (0x56434530) (62)
[  218.702018] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: Dumping IP State
[  218.702489] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: Dumping IP State Completed
[  218.702795] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[  218.703059] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[  218.703311] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: ring vce0 timeout, signaled seq=16, emitted seq=17
[  218.703557] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu:  Process Discord pid 9861 thread exe:cs0 pid 10147
[  218.703799] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset begin!
[  218.865024] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: suspend of IP block <vce_v3_0> failed -22
[  218.876017] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: BACO reset
[  219.052012] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset succeeded, trying to resume
[  219.054007] thesystem kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400380000).
[  219.054037] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: VRAM is lost due to GPU reset!
[  219.177028] thesystem kernel: [drm] UVD and UVD ENC initialized successfully.
[  219.278032] thesystem kernel: [drm] VCE initialized successfully.
[  219.389058] thesystem kernel: amdgpu 0000:0a:00.0: amdgpu: GPU reset(2) succeeded!
[  219.389585] thesystem kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[  219.404009] thesystem kernel: amdgpu 0000:0a:00.0: [drm] device wedged, but recovered through reset
[  220.356082] thesystem kernel: rfkill: input handler enabled

Last edited by eomanis (2025-11-10 21:39:04)

Offline

#2 2025-11-08 17:30:22

rkevin
Member
Registered: 2025-11-08
Posts: 5

Re: Discord sending out video crashes amdgpu and Desktop session

I have had the same issue since yesterday. Things were definitely working a week ago. Interestingly, my system doesn't crash immediately. I can keep my webcam turned on for a bit, and discord shows my webcam is fine, but everyone else sees a completely green video feed on their end. If I mix that with sharing my screen (again, looks fine on my end, but other participants can't load my screenshare, or they see a green screen), then xorg crashes (inconsistent in when it crashes, sometimes after 10 seconds, sometimes after a minute or two). For now, an OK workaround is to use the web version of discord in your browser (both webcam and screenshare works).

EDIT: to clarify, neither my webcam nor my screenshare works. But I only get a Xorg crash if I do both at the same time.

I have a RX580, using the amdgpu drivers on X11 (not wayland). The webcam is a Logitech C920 (unsure if it matters). I have not spent any time debugging this, but this seems like a driver issue that affects more than one person. (Or we are the 2 unluckiest people alive and our GPUs developed a random hardware fault at the same time lol)

Nov 07 11:24:57 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: GPU fault detected: 146 0x0e203e0c
Nov 07 11:24:57 hadron kernel: amdgpu 0000:2b:00.0: amdgpu:  Process Discord pid 5827 thread exe:cs0 pid 6121
Nov 07 11:24:57 hadron kernel: amdgpu 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001007C4
Nov 07 11:24:57 hadron kernel: amdgpu 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E03E00C
Nov 07 11:24:57 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: VM fault (0x0c, vmid 7, pasid 32778) at page 1050564, read from 'VCE0' (0x56434530) (62)
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: Dumping IP State
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: Dumping IP State Completed
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: ring vce0 timeout, signaled seq=6223, emitted seq=6226
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu:  Process Discord pid 5827 thread exe:cs0 pid 6121
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: GPU reset begin!
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: suspend of IP block <vce_v3_0> failed -22
Nov 07 11:25:07 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: BACO reset
Nov 07 11:25:08 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: GPU reset succeeded, trying to resume
Nov 07 11:25:08 hadron kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400380000).
Nov 07 11:25:08 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: VRAM is lost due to GPU reset!
Nov 07 11:25:08 hadron kernel: [drm] UVD and UVD ENC initialized successfully.
Nov 07 11:25:08 hadron kernel: [drm] VCE initialized successfully.
Nov 07 11:25:08 hadron kernel: amdgpu 0000:2b:00.0: amdgpu: GPU reset(1) succeeded!
Nov 07 11:25:08 hadron kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Nov 07 11:25:08 hadron systemd-coredump[6131]: Process 5827 (Discord) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Nov 07 11:25:08 hadron systemd[1]: Started Process Core Dump (PID 6131/UID 0).
Nov 07 11:25:08 hadron kernel: amdgpu 0000:2b:00.0: [drm] device wedged, but recovered through reset
Nov 07 11:25:09 hadron systemd-coredump[6134]: Process 868 (Xorg) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Nov 07 11:25:09 hadron systemd[1]: Started Process Core Dump (PID 6134/UID 0).
Nov 07 11:25:09 hadron systemd-coredump[6135]: [?] Process 868 (Xorg) of user 1000 dumped core.

Last edited by rkevin (2025-11-08 17:35:34)

Offline

#3 2025-11-09 19:58:04

oeniehead
Member
Registered: 2025-11-09
Posts: 1

Re: Discord sending out video crashes amdgpu and Desktop session

I'm seeing the same issues on the workstation of my partner. I've seen different crashes:
- Using extra/discord with X11 results in a green webcam when viewed via another PC, and it crashes GNOME when viewed from a phone
- Using aur/discord-canary with Wayland causes a crash in amdgpu
- Using aur/discord_arch_electron with Wayland causes a crash in amdgpu

The resulting logs in dmesg look the same. This issue seems to have started in the last two weeks. On my own workstation (also with amdgpu) I've not encountered the same issue, but that is still running discord version 1:0.0.111-1.

Specs on the workstation where discord crashes:

$ inxi -b
System:
  Host: socrates Kernel: 6.17.7-zen1-1-zen arch: x86_64 bits: 64
  Desktop: GNOME v: 49.1 Distro: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: Z170-DELUXE v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 2202
    date: 09/19/2016
CPU:
  Info: quad core Intel Core i7-6700K [MT MCP] speed (MHz): avg: 4600
    min/max: 800/4200:4600
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
    470/480/570/570X/580/580X/590] driver: amdgpu v: kernel
  Device-2: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
  Display: wayland server: X.org v: 1.21.1.20 with: Xwayland v: 24.1.9
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu resolution:
    1: 2560x1440~60Hz 2: 2560x1440~60Hz
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: x11: xprop,xrandr
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e
  Device-2: Broadcom BCM4360 802.11ac Dual Band Wireless Network Adapter
    driver: bcma-pci-bridge
  Device-3: Intel I211 Gigabit Network driver: igb
Drives:
  Local Storage: total: 1.82 TiB used: 487.86 GiB (26.2%)
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 9.15 GiB (29.3%)
  Processes: 357 Uptime: 34m Shell: Bash inxi: 3.3.39

Offline

#4 2025-11-10 14:52:32

eomanis
Member
Registered: 2013-04-17
Posts: 64

Re: Discord sending out video crashes amdgpu and Desktop session

I have filed an issue at gitlab.freedesktop.org.

Last edited by eomanis (2025-11-10 21:39:17)

Offline

#5 2025-11-11 05:00:59

rkevin
Member
Registered: 2025-11-08
Posts: 5

Re: Discord sending out video crashes amdgpu and Desktop session

Thanks for filing a issue upstream.

Discord recently upgraded to 0.0.114 on my system. From a simple test, I no longer experience a crash when I am screensharing and have my webcam on at the same time, even with another account joined. I'll let my friends confirm if they see a greenscreen once they are online, but from my own testing when I join with an alt account, the video stream is basically unusable, but isn't completely green like before. Example on my phone:
V2z2ii.png

I'll see if I can trigger a crash again and grab the dump from `/sys/class/drm/card1/device/devcoredump/data` like the kernel messages mentioned, since I forgot to do that last time before rebooting.

Offline

#6 2025-11-15 11:14:44

Qwerty-Space
Member
Registered: 2020-03-13
Posts: 17

Re: Discord sending out video crashes amdgpu and Desktop session

Same issue here.  Was working a few weeks ago, now users are seeing a green image when I share my screen.

Interestingly, it works on Discord in the browser, but there's no desktop audio. 

I've tried with discord and discord canary

Offline

#7 2025-11-18 03:13:31

rkevin
Member
Registered: 2025-11-08
Posts: 5

Re: Discord sending out video crashes amdgpu and Desktop session

I got another repro (funnily enough, for me it only crashes if one particular friend of mine views both my screenshare and webcam at the same time. I can't get it to reproduce by using my phone to view these streams, or if my friend is watching only one of those). I also grabbed the `/sys/class/drm/card1/device/devcoredump/data` file and am attaching it below.

dmesg:

[ 8062.334608] amdgpu 0000:2b:00.0: amdgpu: GPU fault detected: 146 0x0e203e0c
[ 8062.334616] amdgpu 0000:2b:00.0: amdgpu:  Process Discord pid 1232 thread exe:cs0 pid 20040
[ 8062.334620] amdgpu 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x001007C4
[ 8062.334623] amdgpu 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0A03E00C
[ 8062.334625] amdgpu 0000:2b:00.0: amdgpu: VM fault (0x0c, vmid 5, pasid 32781) at page 1050564, read from 'VCE0' (0x56434530) (62)
[ 8072.611019] amdgpu 0000:2b:00.0: amdgpu: Dumping IP State
[ 8072.611025] amdgpu 0000:2b:00.0: amdgpu: Dumping IP State Completed
[ 8072.611074] amdgpu 0000:2b:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
[ 8072.611076] amdgpu 0000:2b:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
[ 8072.611078] amdgpu 0000:2b:00.0: amdgpu: ring vce0 timeout, signaled seq=48289, emitted seq=48292
[ 8072.611083] amdgpu 0000:2b:00.0: amdgpu:  Process Discord pid 1232 thread exe:cs0 pid 20040
[ 8072.611086] amdgpu 0000:2b:00.0: amdgpu: GPU reset begin!
[ 8072.635729] amdgpu 0000:2b:00.0: amdgpu: suspend of IP block <vce_v3_0> failed -22
[ 8072.646280] amdgpu 0000:2b:00.0: amdgpu: BACO reset
[ 8073.163092] amdgpu 0000:2b:00.0: amdgpu: GPU reset succeeded, trying to resume
[ 8073.165578] [drm] PCIE GART of 256M enabled (table at 0x000000F400380000).
[ 8073.165599] amdgpu 0000:2b:00.0: amdgpu: VRAM is lost due to GPU reset!
[ 8073.341426] [drm] UVD and UVD ENC initialized successfully.
[ 8073.442502] [drm] VCE initialized successfully.
[ 8073.456014] amdgpu 0000:2b:00.0: amdgpu: GPU reset(1) succeeded!
[ 8073.456258] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
[ 8073.470297] amdgpu 0000:2b:00.0: [drm] device wedged, but recovered through reset

coredump: https://zipline.rkevin.dev/u/8waukr.txt

Offline

#8 2025-11-18 03:57:00

rkevin
Member
Registered: 2025-11-08
Posts: 5

Re: Discord sending out video crashes amdgpu and Desktop session

I've confirmed the patch from eomanis's upstream bug report to mesa here solves the crashing problem, but doesn't solve the green screen problem (which is basically what the upstream bug report said). Good that we fixed the mesa bug so we aren't crashing anymore, but discord video streams will still be broken until someone at discord fixes this problem.

Offline

#9 2025-11-18 19:53:13

eomanis
Member
Registered: 2013-04-17
Posts: 64

Re: Discord sending out video crashes amdgpu and Desktop session

rkevin wrote:

I got another repro (funnily enough, for me it only crashes if one particular friend of mine views both my screenshare and webcam at the same time. (...)

That makes sense insofar as possibly the codec Discord uses to encode the webcam video stream with varies depending on what the remote participant's device supports or prefers, and possibly not all codecs affect the Video Coding Engine on Ellesmere the same way.

The Ellesmere VCE can encode H264 and HEVC, with HEVC having some restrictions if I am not mistaken (no B Frames, or something).

[theuser@thesystem ~]$ vainfo | grep EncSlice
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointEncSlice

If the remote device prefers something else entirely, for example AV1, and Discord deems it prudent to encode the webcam video to AV1 on the CPU, then the VCE will not be used at all.

Offline

#10 2025-12-02 23:40:17

rkevin
Member
Registered: 2025-11-08
Posts: 5

Re: Discord sending out video crashes amdgpu and Desktop session

Looks like the most recent discord update should have fixed the issue! It did for me at least

Offline

Pages: 1

Board footer

Powered by FluxBB