Kernel panic when playing WoW for several hours

deadmeu · 2026-01-14 14:37:13

I have been experiencing frequent crashes due to a kernel panic when I play World of Warcraft for an extended period of time (several hours). I can pretty reliably trigger it by just playing for a few hours, it happens nearly every time I play for a long while. If I play for a bit, then stop, then play again after, it seems to crash sooner the second time, but this might just be a red herring and it's possible the crashes are entirely random...

I think I have been experiencing this for several months so it is not a recent issue, but I have been playing more WoW recently and so am affected by the crashes more often now. I don't crash when I haven't played.

Does anyone have any suggestions for resolving or better logging this issue?

System Details:
Operating System: Arch Linux
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.2-arch2-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 7900 XT
Motherboard: Asus CROSSHAIR VI HERO
vulkan-radeon 1:25.3.2-1

The panic report is as follows:

Arch: x86_64
Version: 6.18.2-arch2-1

[45258.451225] ------------[ cut here ]------------
[45258.451232] kernel BUG at mm/vmalloc.c:3173!
[45258.451244] Oops: invalid opcode: 0000 [#1] SMP NOPTI
[45258.451250] CPU: 0 UID: 0 PID: 76782 Comm: kworker/u97:4 Not tainted 6.18.2-arch2-1 #1 PREEMPT(full)  e9d53cde2ee9d1bdaa4464d2214ad0f22bd43723
[45258.451255] Hardware name: ASUS System Product Name/CROSSHAIR VI HERO, BIOS 8701 02/08/2023
[45258.451259] Workqueue: events_unbound commit_work
[45258.451268] RIP: 0010:__get_vm_area_node+0x12d/0x130
[45258.451274] Code: 83 c1 01 39 d1 0f 4c ca ba 1e 00 00 00 39 d1 0f 4f ca 48 d3 e6 49 89 f7 e9 35 ff ff ff 4c 89 f7 e8 78 2c 02 00 45 31 f6 eb ae <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40
[45258.451278] RSP: 0018:ffffcf58de36f598 EFLAGS: 00010202
[45258.451282] RAX: 0000000000000dc0 RBX: 0000000000001000 RCX: 0000000000000422
[45258.451286] RDX: 000000000000000c RSI: 0000000000001000 RDI: 0000000000038bc8
[45258.451289] RBP: 000000000000000c R08: ffffcf58c0000000 R09: ffffef58bfffffff
[45258.451292] R10: ffff8ce03f2d5200 R11: 0000000000000000 R12: 0000000000000dc0
[45258.451295] R13: 0000000000038bc8 R14: 00000000ffffffff R15: 0000000000000dc0
[45258.451298] FS:  0000000000000000(0000) GS:ffff8ce03f2f2000(0000) knlGS:0000000000000000
[45258.451302] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[45258.451305] CR2: 00007f98794e3d00 CR3: 00000008bcb75000 CR4: 0000000000350ef0
[45258.451308] Call Trace:
[45258.451314]  <TASK>
[45258.451317]  __vmalloc_node_range_noprof+0x149/0x840
[45258.451327]  ? dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.451897]  ? __alloc_frozen_pages_noprof+0x334/0x350
[45258.451904]  ? dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.452356]  ? alloc_pages_mpol+0x86/0x170
[45258.452364]  __kvmalloc_node_noprof+0x2a2/0x8a0
[45258.452371]  ? dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.452829]  ? srso_return_thunk+0x5/0x5f
[45258.452835]  ? get_pixel_clock_parameters+0x180/0x1c0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.453341]  ? dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.453801]  ? dcn20_build_pipe_pix_clk_params+0x1d/0x40 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.454313]  ? dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.454777]  dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.455251]  dc_state_create_phantom_plane+0x1a/0x60 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.455712]  dcn32_add_phantom_pipes+0x160/0x440 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.456222]  dcn32_internal_validate_bw+0xb79/0x15b0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.456756]  dml1_validate+0xbf/0x2d0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.457272]  ? srso_return_thunk+0x5/0x5f
[45258.457279]  ? dc_validate_global_state+0x3a0/0x410 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.457754]  dcn32_validate_bandwidth+0xb7/0x1c0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.458266]  dc_validate_with_context+0x559/0x6d0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.458736]  dc_commit_streams+0x2a5/0x520 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.459223]  amdgpu_dm_atomic_commit_tail+0x6a4/0x3c70 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.459722]  ? srso_return_thunk+0x5/0x5f
[45258.459728]  ? generic_reg_get+0x21/0x40 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.460203]  ? srso_return_thunk+0x5/0x5f
[45258.460209]  ? optc1_get_crtc_scanoutpos+0x75/0xb0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.460715]  ? dc_stream_send_dp_sdp+0xa0/0xd0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.461188]  ? srso_return_thunk+0x5/0x5f
[45258.461192]  ? dm_crtc_get_scanoutpos+0xa4/0x120 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.461689]  ? srso_return_thunk+0x5/0x5f
[45258.461693]  ? ktime_get+0x3b/0xd0
[45258.461699]  ? srso_return_thunk+0x5/0x5f
[45258.461703]  ? amdgpu_display_get_crtc_scanoutpos+0xa8/0x1d0 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.462083]  ? srso_return_thunk+0x5/0x5f
[45258.462087]  ? amdgpu_crtc_get_scanout_position+0x28/0x40 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.462454]  ? srso_return_thunk+0x5/0x5f
[45258.462459]  ? drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x148/0x380
[45258.462467]  ? srso_return_thunk+0x5/0x5f
[45258.462471]  ? dma_fence_default_wait+0x8a/0x270
[45258.462478]  ? srso_return_thunk+0x5/0x5f
[45258.462481]  ? wait_for_completion_timeout+0x14e/0x1a0
[45258.462487]  ? srso_return_thunk+0x5/0x5f
[45258.462495]  commit_tail+0xc1/0x150
[45258.462503]  process_one_work+0x193/0x350
[45258.462512]  worker_thread+0x2d7/0x410
[45258.462518]  ? __pfx_worker_thread+0x10/0x10
[45258.462523]  kthread+0xfc/0x240
[45258.462528]  ? __pfx_kthread+0x10/0x10
[45258.462532]  ? __pfx_kthread+0x10/0x10
[45258.462537]  ret_from_fork+0x1c2/0x1f0
[45258.462543]  ? __pfx_kthread+0x10/0x10
[45258.462547]  ret_from_fork_asm+0x1a/0x30
[45258.462558]  </TASK>
[45258.462562] Modules linked in: overlay wireguard libcurve25519 ip6_udp_tunnel udp_tunnel snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nft_masq nft_ct vfat fat amdgpu intel_rapl_msr amd_atl snd_hda_codec_alc882 intel_rapl_common snd_hda_codec_realtek_lib snd_hda_codec_generic snd_hda_codec_atihdmi snd_hda_codec_hdmi amdxcp drm_panel_backlight_quirks snd_hda_intel gpu_sched drm_buddy snd_hda_codec drm_exec eeepc_wmi kvm_amd drm_suballoc_helper snd_hda_core asus_wmi drm_ttm_helper ucsi_ccg snd_intel_dspcfg platform_profile ee1004 ttm snd_intel_sdw_acpi typec_ucsi sparse_keymap snd_hwdep i2c_algo_bit kvm rfkill typec sp5100_tco mxm_wmi wmi_bmof snd_pcm igc drm_display_helper roles asus_wmi_sensors irqbypass snd_timer cec thunderbolt snd ptp i2c_piix4 joydev rapl video pcspkr soundcore k10temp i2c_smbus pps_core mousedev gpio_amdpt gpio_generic wmi mac_hid ip6t_REJECT xt_hl ip6t_rt ipt_REJECT xt_LOG nf_log_syslog nft_limit xt_limit nft_reject_inet xt_addrtype nf_reject_ipv4 nf_reject_ipv6 xt_tcpudp nft_reject
[45258.462699]  nft_chain_nat xt_conntrack nf_nat nft_compat nf_conntrack x_tables nf_defrag_ipv6 nf_defrag_ipv4 nf_tables i2c_dev pkcs8_key_parser crypto_user nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress dm_crypt encrypted_keys trusted asn1_encoder tee dm_mod nvme polyval_clmulni ghash_clmulni_intel nvme_core aesni_intel nvme_keyring nvme_auth ccp hkdf
[45258.462774] ---[ end trace 0000000000000000 ]---
[45258.462778] RIP: 0010:__get_vm_area_node+0x12d/0x130
[45258.462787] Code: 83 c1 01 39 d1 0f 4c ca ba 1e 00 00 00 39 d1 0f 4f ca 48 d3 e6 49 89 f7 e9 35 ff ff ff 4c 89 f7 e8 78 2c 02 00 45 31 f6 eb ae <0f> 0b 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40
[45258.462791] RSP: 0018:ffffcf58de36f598 EFLAGS: 00010202
[45258.462795] RAX: 0000000000000dc0 RBX: 0000000000001000 RCX: 0000000000000422
[45258.462799] RDX: 000000000000000c RSI: 0000000000001000 RDI: 0000000000038bc8
[45258.462802] RBP: 000000000000000c R08: ffffcf58c0000000 R09: ffffef58bfffffff
[45258.462805] R10: ffff8ce03f2d5200 R11: 0000000000000000 R12: 0000000000000dc0
[45258.462808] R13: 0000000000038bc8 R14: 00000000ffffffff R15: 0000000000000dc0
[45258.462811] FS:  0000000000000000(0000) GS:ffff8ce03f2f2000(0000) knlGS:0000000000000000
[45258.462814] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[45258.462817] CR2: 00007f98794e3d00 CR3: 00000008bcb75000 CR4: 0000000000350ef0
[45258.462821] Kernel panic - not syncing: Fatal exception in interrupt
[45258.463407] Kernel Offset: 0x3b800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

Last edited by ewaller (2026-01-17 16:42:33)

5hridhyan · 2026-01-16 17:49:40

kernel BUG at mm/vmalloc.c:3173!
invalid opcode: 0000

so the kernel is intentionally stopping because an internal invariant was violated I don't think like it should'nt be a random memory corruption.

[45258.453341]  ? dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.453801]  ? dcn20_build_pipe_pix_clk_params+0x1d/0x40 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.454313]  ? dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.454777]  dc_create_plane_state+0x29/0x90 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]
[45258.455251]  dc_state_create_phantom_plane+0x1a/0x60 [amdgpu a325137a1623f2caf2132b803fbbacc9399907ab]

stack trace is entirely amdgpu dc.
"dcn32_*" RDNA3 specific?

__get_vm_area_node
__vmalloc_node_range

the trace indicates a kernel BUG triggered from amdgpu display code, but idk why in your case, likely a logic error or state handling bug in amdgpu dC
from my understandings I say WoW just triggers the workload, the panic is caused by an amdgpu dc bug in the kernel

is the behavior same in LTS KErnel?

edit:

deadmeu wrote:

Version: 6.18.2-arch2-1

the latest is "6.18.5-arch1-1" first try updating and testing it, if still the same, then test it in LTS

edit2:
I’ve provided guidance to the best of my knowledge. I won’t be able to follow up further, hope this will be solved Good luck!

Last edited by 5hridhyan (2026-01-28 15:53:20)

deadmeu · 2026-01-17 07:23:43

It may be worth noting that I am running WoW through the Bottles Flatpak.

Looking at the journal while playing I often see many entries like

kwin_wayland[2153]: atomic commit failed: Device or resource busy

and

flatpak[11323]: 071c:err:seh:dispatch_exception assertion failure exception

e.g.:

Jan 17 17:13:25 hostname kwin_wayland[2153]: atomic commit failed: Device or resource busy
Jan 17 17:13:25 hostname flatpak[11323]: 071c:err:seh:dispatch_exception assertion failure exception
Jan 17 17:13:30 hostname kwin_wayland[2153]: atomic commit failed: Device or resource busy
Jan 17 17:13:32 hostname kwin_wayland[2153]: atomic commit failed: Device or resource busy
Jan 17 17:13:35 hostname flatpak[11323]: 071c:err:seh:dispatch_exception assertion failure exception
Jan 17 17:13:37 hostname systemd[2084]: Started Firefox - Web Browser.
Jan 17 17:13:37 hostname systemd[2084]: Started app-flatpak-org.mozilla.firefox-3989083858.scope.
Jan 17 17:13:37 hostname flatpak[12145]: [2] Sandbox: CanCreateUserNamespace() clone() failure: EPERM
Jan 17 17:13:45 hostname flatpak[11323]: 071c:err:seh:dispatch_exception assertion failure exception
Jan 17 17:13:55 hostname flatpak[11323]: 071c:err:seh:dispatch_exception assertion failure exception
Jan 17 17:14:05 hostname flatpak[11323]: 071c:err:seh:dispatch_exception assertion failure exception
Jan 17 17:14:15 hostname kwin_wayland[2153]: atomic commit failed: Device or resource busy
Jan 17 17:14:15 hostname flatpak[11323]: 071c:err:seh:dispatch_exception assertion failure exception

I will try the latest kernel and the LTS kernel and see how that goes.

Last edited by deadmeu (2026-01-18 06:12:13)

ewaller · 2026-01-17 16:44:09

deadmeu, I took the liberty of editing your first post to add code tags around your journal output. Welcome to the forums.

deadmeu · 2026-01-18 06:12:42

ewaller wrote:

deadmeu, I took the liberty of editing your first post to add code tags around your journal output. Welcome to the forums.

Thank you, I was wondering how to do that.

Arch Linux

#1 2026-01-14 14:37:13

Kernel panic when playing WoW for several hours

#2 2026-01-16 17:49:40

Re: Kernel panic when playing WoW for several hours

#3 2026-01-17 07:23:43

Re: Kernel panic when playing WoW for several hours

#4 2026-01-17 16:44:09

Re: Kernel panic when playing WoW for several hours

#5 2026-01-18 06:12:42

Re: Kernel panic when playing WoW for several hours

Board footer