Framework Laptop 13 AMD Ryzen AI 5 340 soft lockup

Which Linux distro are you using?
Ubuntu 24.04.02 LTS

Which kernel are you using?
6.11.0-25-generic

Which BIOS version are you using?
3.03

Which Framework Laptop 13 model are you using?
AMD Ryzen™ AI 5 340

Hello everybody,

I have been encountering the following error.
Once it starts I will loose my laptop.
The display is gone but the backlight will still be on.
Pressing the On/Off button does nothing. The laptop just hang until I press down the power button and force a shutdown.

Checking the logs I see a bunch of these with increasing time on the stuck

May 06 14:45:47 frame kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 3156s! [KMS thread:2810]
May 06 14:45:47 frame kernel: Modules linked in: tls exfat rfcomm snd_seq_dummy snd_hrtimer ccm cmac algif_hash algif_skcipher af_alg bnep b>
May 06 14:45:47 frame kernel:  snd_hda_core mt7925_common crct10dif_pclmul snd_pcm_dmaengine snd_hwdep polyval_clmulni cros_ec_dev amdxcp sn>
May 06 14:45:47 frame kernel:  nvme ucsi_acpi i2c_hid_acpi xhci_pci nvme_core typec_ucsi thunderbolt crc32_pclmul i2c_hid video xhci_pci_ren>
May 06 14:45:47 frame kernel: CPU: 4 UID: 1000 PID: 2810 Comm: KMS thread Tainted: G             L     6.11.0-25-generic #25~24.04.1-Ubuntu
May 06 14:45:47 frame kernel: Tainted: [L]=SOFTLOCKUP
May 06 14:45:47 frame kernel: Hardware name: Framework Laptop 13 (AMD Ryzen AI 300 Series)/FRANMGCP05, BIOS 03.03 03/10/2025
May 06 14:45:47 frame kernel: RIP: 0010:delay_halt_mwaitx+0x3c/0x50
May 06 14:45:47 frame kernel: Code: 05 91 3f 00 63 48 05 00 60 00 00 0f 01 fa b8 ff ff ff ff b9 02 00 00 00 48 39 c6 48 0f 46 c6 48 89 c3 b8>
May 06 14:45:47 frame kernel: RSP: 0018:ffffbced865272f8 EFLAGS: 00000293
May 06 14:45:47 frame kernel: RAX: 00000000000000f0 RBX: 00000000000007cd RCX: 0000000000000002
May 06 14:45:47 frame kernel: RDX: 0000000000000000 RSI: 00000000000007cd RDI: 000066c1bd97de1c
May 06 14:45:47 frame kernel: RBP: ffffbced86527300 R08: 0000000000000000 R09: 0000000000000000
May 06 14:45:47 frame kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000007cd
May 06 14:45:47 frame kernel: R13: 00000000000186a0 R14: ffffbced86527478 R15: 0000000000000001
May 06 14:45:47 frame kernel: FS:  0000783a03fff6c0(0000) GS:ffff9a8afe600000(0000) knlGS:0000000000000000
May 06 14:45:19 frame kernel: R10: 0000000000000016 R11: 0000000000000246 R12: 0000783a03ffdc70
May 06 14:45:19 frame kernel: R13: 00000000c03864bc R14: 000000000000000c R15: 00007839f8005c70
May 06 14:45:19 frame kernel:  </TASK>
May 06 14:45:47 frame kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 3156s! [KMS thread:2810]
May 06 14:45:47 frame kernel: Modules linked in: tls exfat rfcomm snd_seq_dummy snd_hrtimer ccm cmac algif_hash algif_skcipher af_alg bnep b>
May 06 14:45:47 frame kernel:  snd_hda_core mt7925_common crct10dif_pclmul snd_pcm_dmaengine snd_hwdep polyval_clmulni cros_ec_dev amdxcp sn>
May 06 14:45:47 frame kernel:  nvme ucsi_acpi i2c_hid_acpi xhci_pci nvme_core typec_ucsi thunderbolt crc32_pclmul i2c_hid video xhci_pci_ren>
May 06 14:45:47 frame kernel: CPU: 4 UID: 1000 PID: 2810 Comm: KMS thread Tainted: G             L     6.11.0-25-generic #25~24.04.1-Ubuntu
May 06 14:45:47 frame kernel: Tainted: [L]=SOFTLOCKUP
May 06 14:45:47 frame kernel: Hardware name: Framework Laptop 13 (AMD Ryzen AI 300 Series)/FRANMGCP05, BIOS 03.03 03/10/2025
May 06 14:45:47 frame kernel: RIP: 0010:delay_halt_mwaitx+0x3c/0x50
May 06 14:45:47 frame kernel: Code: 05 91 3f 00 63 48 05 00 60 00 00 0f 01 fa b8 ff ff ff ff b9 02 00 00 00 48 39 c6 48 0f 46 c6 48 89 c3 b8>
May 06 14:45:47 frame kernel: RSP: 0018:ffffbced865272f8 EFLAGS: 00000293
May 06 14:45:47 frame kernel: RAX: 00000000000000f0 RBX: 00000000000007cd RCX: 0000000000000002
May 06 14:45:47 frame kernel: RDX: 0000000000000000 RSI: 00000000000007cd RDI: 000066c1bd97de1c
May 06 14:45:47 frame kernel: RBP: ffffbced86527300 R08: 0000000000000000 R09: 0000000000000000
May 06 14:45:47 frame kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000007cd
May 06 14:45:47 frame kernel: R13: 00000000000186a0 R14: ffffbced86527478 R15: 0000000000000001
May 06 14:45:47 frame kernel: FS:  0000783a03fff6c0(0000) GS:ffff9a8afe600000(0000) knlGS:0000000000000000
May 06 14:45:47 frame kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 06 14:45:47 frame kernel: CR2: 000074e8540e1000 CR3: 000000015886c000 CR4: 0000000000f50ef0
May 06 14:45:47 frame kernel: PKRU: 55555554
May 06 14:45:47 frame kernel: Call Trace:
May 06 14:45:47 frame kernel:  <IRQ>
May 06 14:45:47 frame kernel:  ? show_regs+0x6c/0x80
May 06 14:45:47 frame kernel:  ? watchdog_timer_fn+0x218/0x2a0
May 06 14:45:47 frame kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
May 06 14:45:47 frame kernel:  ? __hrtimer_run_queues+0x10f/0x2a0
May 06 14:45:47 frame kernel:  ? clockevents_program_event+0xbe/0x150
May 06 14:45:47 frame kernel:  ? hrtimer_interrupt+0xf8/0x250
May 06 14:45:47 frame kernel:  ? __sysvec_apic_timer_interrupt+0x56/0x130
May 06 14:45:47 frame kernel:  ? sysvec_apic_timer_interrupt+0x9b/0xc0
May 06 14:45:47 frame kernel:  </IRQ>
May 06 14:45:47 frame kernel:  <TASK>
May 06 14:45:47 frame kernel:  ? asm_sysvec_apic_timer_interrupt+0x1b/0x20
May 06 14:45:47 frame kernel:  ? delay_halt_mwaitx+0x3c/0x50
May 06 14:45:47 frame kernel:  ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
May 06 14:45:47 frame kernel:  delay_halt.part.0+0x3b/0x70
May 06 14:45:47 frame kernel:  delay_halt+0x13/0x30
May 06 14:45:47 frame kernel:  __const_udelay+0x3a/0x50
May 06 14:45:47 frame kernel:  dmub_srv_wait_for_idle+0x52/0xb0 [amdgpu]
May 06 14:45:47 frame kernel:  dc_dmub_srv_cmd_run_list+0x137/0x210 [amdgpu]
May 06 14:45:47 frame kernel:  dc_dmub_srv_cmd_run+0x18/0x30 [amdgpu]
May 06 14:45:47 frame kernel:  dm_execute_dmub_cmd+0x15/0x30 [amdgpu]
May 06 14:45:47 frame kernel:  dc_wake_and_execute_dmub_cmd_list+0xe1/0x110 [amdgpu]
May 06 14:45:47 frame kernel:  dc_wake_and_execute_dmub_cmd+0x18/0x30 [amdgpu]
May 06 14:45:47 frame kernel:  dcn35_update_clocks+0x3a8/0x810 [amdgpu]
May 06 14:45:47 frame kernel:  dcn20_prepare_bandwidth+0x49/0x1e0 [amdgpu]
May 06 14:45:47 frame kernel:  dcn35_prepare_bandwidth+0xa6/0xe0 [amdgpu]
May 06 14:45:47 frame kernel:  dc_commit_state_no_check+0x163/0xe20 [amdgpu]
May 06 14:45:47 frame kernel:  dc_commit_streams+0x181/0x6f0 [amdgpu]
May 06 14:45:47 frame kernel:  amdgpu_dm_commit_streams+0x68d/0x890 [amdgpu]
May 06 14:45:47 frame kernel:  amdgpu_dm_atomic_commit_tail+0xc3/0x10a0 [amdgpu]
May 06 14:45:47 frame kernel:  ? drm_atomic_helper_setup_commit+0x232/0x790
May 06 14:45:47 frame kernel:  ? __kmalloc_noprof+0x192/0x490
May 06 14:45:47 frame kernel:  ? amdgpu_dm_atomic_check+0x12f6/0x1520 [amdgpu]
May 06 14:45:47 frame kernel:  ? wait_for_completion_timeout+0x110/0x150
May 06 14:45:47 frame kernel:  ? drm_dp_mst_atomic_setup_commit+0x91/0x1f0 [drm_display_helper]
May 06 14:45:47 frame kernel:  ? drm_dp_mst_atomic_setup_commit+0x91/0x1f0 [drm_display_helper]
May 06 14:45:47 frame kernel:  commit_tail+0xca/0x1b0
May 06 14:45:47 frame kernel:  drm_atomic_helper_commit+0x132/0x160
May 06 14:45:47 frame kernel:  drm_atomic_commit+0xa5/0xe0
May 06 14:45:47 frame kernel:  ? __pfx___drm_printfn_info+0x10/0x10
May 06 14:45:47 frame kernel:  drm_mode_atomic_ioctl+0x560/0x850
May 06 14:45:47 frame kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
May 06 14:45:47 frame kernel:  drm_ioctl_kernel+0xb9/0x120
May 06 14:45:47 frame kernel:  drm_ioctl+0x2f6/0x5b0
May 06 14:45:47 frame kernel:  ? __pfx_drm_mode_atomic_ioctl+0x10/0x10
May 06 14:45:47 frame kernel:  amdgpu_drm_ioctl+0x4e/0x90 [amdgpu]
May 06 14:45:47 frame kernel:  __x64_sys_ioctl+0xa0/0xf0
May 06 14:45:47 frame kernel:  x64_sys_call+0x11ad/0x25f0
May 06 14:45:47 frame kernel:  do_syscall_64+0x7e/0x170
May 06 14:45:47 frame kernel:  ? __count_memcg_events+0x86/0x160
May 06 14:45:47 frame kernel:  ? ksys_write+0xe6/0x100
May 06 14:45:47 frame kernel:  ? syscall_exit_to_user_mode+0x4e/0x250
May 06 14:45:47 frame kernel:  ? do_syscall_64+0x8a/0x170
May 06 14:45:47 frame kernel:  ? irqentry_exit_to_user_mode+0x43/0x250
May 06 14:45:47 frame kernel:  ? irqentry_exit+0x43/0x50
May 06 14:45:47 frame kernel:  ? exc_page_fault+0x96/0x1c0
May 06 14:45:47 frame kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
May 06 14:45:47 frame kernel: RIP: 0033:0x783a29524ded
May 06 14:45:47 frame 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>
May 06 14:45:47 frame kernel: RSP: 002b:0000783a03ffdbd0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
May 06 14:45:47 frame kernel: RAX: ffffffffffffffda RBX: 00007839f8011690 RCX: 0000783a29524ded
May 06 14:45:47 frame kernel: RDX: 0000783a03ffdc70 RSI: 00000000c03864bc RDI: 000000000000000c
May 06 14:45:47 frame kernel: RBP: 0000783a03ffdc20 R08: 00007839f8000090 R09: 0000000000000130
May 06 14:45:47 frame kernel: R10: 0000000000000016 R11: 0000000000000246 R12: 0000783a03ffdc70
May 06 14:45:47 frame kernel: R13: 00000000c03864bc R14: 000000000000000c R15: 00007839f8005c70
May 06 14:45:47 frame kernel:  </TASK>

The CPU#4 stuck for 3156s! message just keeps going up and up and up until I force a power off.

So far I’m blaming AMD GPU drivers.

I know I’m running an unsupported version of Ubuntu, but I was not expecting this hard crashes.

Any idea or suggestion will be helpful.

Hi there,

Ubuntu 22.04.02 and kernel 6.11 is not supported for the new Ryzen boards. You will need to upgrade to Ubuntu 25.04 and Kernel 6.14.

I was in the same boat and I have the AI 5 340. I first had to upgrade on CLI to 24.10, and then to 25.04.

Which wifi card are you using? I’m using my old AX210 and it’s running fine with 25.04 and Kernel 6.14.

:melting_face:
Thanks for the Ubuntu 25.04 suggestion. That’s what I was trying to avoid. Mostly laziness.

I just got my new DIY Framework 13 AI 5 340.
I didn’t check the board itself but I’m guessing they were shipping it with AMD RZ717

For what is worth it lspci is reporting it like:

Network controller: MEDIATEK Corp. Device 0717
Subsystem: MEDIATEK Corp. Device 0717

Got it, I’ve read informally that there are some wifi dropouts at times on 25.04 with the new wifi card, but apparently that can be mitigated with changing wifi settings

I’ve had zero issues on 25.04 but YMMV