Kernel Freeze since 6.15 (including 6.16)

Hi everyone, I originally came from this thread but my issue is different.

Since 6.15 my laptop freezes if I start it with kernel 6.15 or 6.16 (latest tested was 6.16.3).
The freeze can happen almost immediately e.g. 1 minute or 30 minutes which is a bit weird.

The previous thread where I ran the kernels with tuxedo-drivers produced the following logs with journalctl --no-hostname -k --boot=-1: fedora 6.16.3 logs - Pastebin.com
where the most interesting part seems to be this:

Logs

Aug 27 22:15:37 kernel: ------------[ cut here ]------------
Aug 27 22:15:37 kernel: WARNING: CPU: 22 PID: 223 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_replay.c:89 dmub_replay_enable+0xf1/0x100 [amdgpu]
Aug 27 22:15:37 kernel: Modules linked in: uinput rfcomm snd_seq_dummy snd_hrtimer nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables qrtr bnep vfat fat iwlmvm snd_acp70 snd_acp_i2s snd_acp_pdm snd_acp_pcm snd_sof_amd_acp70 snd_sof_amd_acp63 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir mac80211 snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_pci_ps amd_atl intel_rapl_msr snd_soc_acpi_amd_match intel_rapl_common snd_amd_sdw_acpi soundwire_amd libarc4 soundwire_generic_allocation soundwire_bus snd_soc_sdca snd_soc_core edac_mce_amd snd_hda_codec_conexant snd_hda_codec_hdmi snd_hda_codec_generic kvm_amd uvcvideo snd_compress snd_hda_intel btusb ac97_bus snd_intel_dspcfg uvc snd_pcm_dmaengine videobuf2_vmalloc snd_intel_sdw_acpi snd_hda_codec snd_rpl_pci_acp6x btrtl snd_acp_pci videobuf2_memops snd_amd_acpi_mach
Aug 27 22:15:37 kernel: iwlwifi snd_hda_core videobuf2_v4l2 snd_acp_legacy_common btintel kvm videobuf2_common btbcm snd_pci_acp6x snd_hwdep btmtk spd5118 uniwill_wmi(OE) snd_seq videodev bluetooth tuxedo_io(OE) clevo_wmi(OE) irqbypass asus_wmi tuxedo_keyboard(OE) snd_seq_device tuxedo_compatibility_check(OE) mc rapl snd_pcm sparse_keymap snd_pci_acp5x wmi_bmof led_class_multicolor cfg80211 pcspkr snd_rn_pci_acp3x snd_timer snd_acp_config amd_pmf snd snd_soc_acpi i2c_piix4 k10temp amdtee i2c_smbus snd_pci_acp3x rfkill soundcore amd_sfh joydev tee platform_profile amd_pmc loop zram lz4hc_compress lz4_compress amdgpu amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec drm_suballoc_helper drm_panel_backlight_quirks drm_buddy sdhci_pci nvme drm_display_helper ucsi_acpi sdhci_uhs2 typec_ucsi nvme_core sdhci amdxdna polyval_clmulni typec ghash_clmulni_intel hid_multitouch cqhci sha512_ssse3 nvme_keyring sha1_ssse3 thunderbolt cec mmc_core gpu_sched sp5100_tco video nvme_auth i2c_hid_acpi wmi i2c_hid serio_raw sunrpc iscsi_tcp libiscsi_tcp
Aug 27 22:15:37 kernel: libiscsi scsi_transport_iscsi fuse i2c_dev nfnetlink
Aug 27 22:15:37 kernel: Unloaded tainted modules: tuxedo_nb02_nvidia_power_ctrl(OE):1
Aug 27 22:15:37 kernel: CPU: 22 UID: 0 PID: 223 Comm: kworker/22:1 Tainted: G OE 6.16.3-200.fc42.x86_64 #1 PREEMPT(lazy)
Aug 27 22:15:37 kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Aug 27 22:15:37 kernel: Hardware name: TUXEDO TUXEDO InfinityBook Pro AMD Gen10/XxKK4NAx_XxSP4NAx, BIOS N.1.19A07 06/27/2025
Aug 27 22:15:37 kernel: Workqueue: events fbcon_register_existing_fbs
Aug 27 22:15:37 kernel: RIP: 0010:dmub_replay_enable+0xf1/0x100 [amdgpu]
Aug 27 22:15:37 kernel: Code: 85 c0 75 cf 81 fb e8 03 00 00 74 1e 48 8b 44 24 48 65 48 2b 05 f8 4a d5 de 75 13 48 83 c4 50 5b 5d 41 5c 41 5d c3 cc cc cc cc <0f> 0b eb de e8 f6 9e ac dc 66 0f 1f 44 00 00 90 90 90 90 90 90 90
Aug 27 22:15:37 kernel: RSP: 0018:ffffd0a840967790 EFLAGS: 00010246
Aug 27 22:15:37 kernel: RAX: 00000041cbdd8008 RBX: 00000000000003e9 RCX: 0000000000000016
Aug 27 22:15:37 kernel: RDX: 00000000000f4010 RSI: 00000000000f3b43 RDI: 00000041cbce3ff8
Aug 27 22:15:37 kernel: RBP: 0000000000000000 R08: 0000000000000002 R09: ffff8d25812c4100
Aug 27 22:15:37 kernel: R10: ffffd0a89f91d100 R11: ffff8d259d7de800 R12: ffff8d259e1db240
Aug 27 22:15:37 kernel: R13: 0000000000000000 R14: 0000000000000001 R15: ffff8d2594073e00
Aug 27 22:15:37 kernel: FS: 0000000000000000(0000) GS:ffff8d34feb5f000(0000) knlGS:0000000000000000
Aug 27 22:15:37 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 27 22:15:37 kernel: CR2: 0000560e6a229ae8 CR3: 0000000157243000 CR4: 0000000000f50ef0
Aug 27 22:15:37 kernel: PKRU: 55555554
Aug 27 22:15:37 kernel: Call Trace:
Aug 27 22:15:37 kernel:
Aug 27 22:15:37 kernel: edp_set_replay_allow_active+0x182/0x1e0 [amdgpu]

But I ran it again I’ve removed the tuxedo-drivers and it still keeps freezing a while and with logs that don’t contain a crash or at least I didn’t see one…
So I assume it is something unrelated to tuxedo but not sure what it is…
Full logs here


My system info below:

System info

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1
Kernel Version: 6.14.0-63.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Memory: 64 GiB of RAM (61,9 GiB usable)
Graphics Processor: AMD Radeon 890M Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO InfinityBook Pro AMD Gen10

if there is anything else I can provide that might help or things i can try out let me know


Update #1: I’ve dared to boot 6.16 once more but also didn’t spot anything particular in the logs

“freeze” needs elaboration. After a freeze:

  • can you get a text console with `?
  • do status lights (, etc.) respond>
  • can you connect to the system with ssh?

Random issues and lack of useful details in the journal suggest a hardware problem.

From https://www.tuxedocomputers.com/en/FAQ-TUXEDO-InfinityBook-Pro-15-Gen10-AMD.tuxedo#2365:

Known issues with other distributions or kernel versions

  • Internal keyboard no longer works after waking up from standby
  • System freezes completely 2–5 minutes after disconnecting the charger
  • Graphical artifacts, e.g. when scrolling within the user interface (such as in the terminal)
  • CPU remains permanently in low power mode regardless of workload
1 Like

Ah that’s a weird corner I’ve never entered before - I kind of assumed that it works with any kernel since I’ve got another device with the same APU and didn’t expect that there might be other issues as well.

I’ve got the 14" version but the help page states the same - so let’s see if they manage to incorporate the changes anytime soon.

Thanks a lot for the explanation!

I’m currently on vacation so don’t have a second device to try things out but switching to a different tty for example didnt work