Random system freezes/reboots

Gricenchos · 2025-04-08 20:10:38

Hello!

For a couple of days now I've been experiencing random freezes and (rarely) reboots. I'm using Lenovo Legion 7 16ARHA7, Ryzen 9 and Radeon graphics. Usually those freezes happen when I leave the laptop unattended and it tries to enter the sleep mode, but not always. The freezes are complete, rendering the laptop completely unresponsive, and the only way out is a hard reboot with the power button. I haven't been able to find anything meaningful in the logs.

Output of journalctl: https://0x0.st/8_Im.txt

Output of journalctl -b -1 -p 3:

апр 08 12:31:08 ZAX512L kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
апр 08 12:31:08 ZAX512L kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.OKEC], AE_NOT_FOUND (20240827/psargs-332)
апр 08 12:31:08 ZAX512L kernel: ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
апр 08 12:31:11 ZAX512L bluetoothd[611]: Failed to set mode: Failed (0x03)
апр 08 12:31:26 ZAX512L kwin_wayland[922]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
апр 08 13:32:05 ZAX512L bluetoothd[611]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected
 (107)
апр 08 13:32:12 ZAX512L kwin_wayland[922]: kwin_libinput: Libinput: event0  - Power Button: client bug: event processing lagging behind by 2008ms, your system is too slow
апр 08 13:32:12 ZAX512L kwin_wayland[922]: kwin_libinput: Libinput: event5  - ITE Tech. Inc. ITE Device(8258) Keyboard: client bug: event processing lagging behind by 1946ms, yo
ur system is too slow
апр 08 13:32:13 ZAX512L bluetoothd[611]: src/service.c:btd_service_connect() a2dp-source profile connect failed for F4:4E:FD:8C:B0:9C: Device or resource busy
апр 08 13:32:13 ZAX512L bluetoothd[611]: src/service.c:btd_service_connect() avrcp-controller profile connect failed for F4:4E:FD:8C:B0:9C: Operation already in progress
апр 08 13:32:14 ZAX512L bluetoothd[611]: plugins/policy.c:reconnect_timeout() Reconnecting services failed: Operation already in progress (114)
апр 08 13:32:22 ZAX512L bluetoothd[611]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected
 (107)
апр 08 13:32:32 ZAX512L bluetoothd[611]: src/service.c:btd_service_connect() a2dp-source profile connect failed for F4:4E:FD:8C:B0:9C: Device or resource busy
апр 08 13:32:32 ZAX512L bluetoothd[611]: profiles/audio/avctp.c:avctp_control_confirm() Control: Refusing unexpected connect
апр 08 13:32:33 ZAX512L bluetoothd[611]: plugins/policy.c:reconnect_timeout() Reconnecting services failed: Operation already in progress (114)
апр 08 13:32:38 ZAX512L bluetoothd[611]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected
 (107)
апр 08 13:32:46 ZAX512L kwin_wayland[922]: kwin_libinput: Libinput: event0  - Power Button: client bug: event processing lagging behind by 1971ms, your system is too slow
апр 08 13:32:46 ZAX512L kwin_wayland[922]: kwin_libinput: Libinput: event5  - ITE Tech. Inc. ITE Device(8258) Keyboard: client bug: event processing lagging behind by 1908ms, yo
ur system is too slow
апр 08 13:32:47 ZAX512L bluetoothd[611]: src/service.c:btd_service_connect() a2dp-source profile connect failed for F4:4E:FD:8C:B0:9C: Device or resource busy
апр 08 13:32:47 ZAX512L bluetoothd[611]: profiles/audio/avctp.c:avctp_control_confirm() Control: Refusing unexpected connect
апр 08 13:32:49 ZAX512L bluetoothd[611]: plugins/policy.c:reconnect_timeout() Reconnecting services failed: Operation already in progress (114)
апр 08 13:32:56 ZAX512L bluetoothd[611]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected
 (107)
апр 08 13:33:03 ZAX512L bluetoothd[611]: src/service.c:btd_service_connect() a2dp-source profile connect failed for F4:4E:FD:8C:B0:9C: Device or resource busy
апр 08 13:33:04 ZAX512L bluetoothd[611]: plugins/policy.c:reconnect_timeout() Reconnecting services failed: Operation already in progress (114)
апр 08 14:02:47 ZAX512L kernel: snd_pci_acp6x 0000:07:00.5: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xfffffffffffffffc flags=0x0030]
апр 08 16:00:45 ZAX512L kernel: snd_pci_acp6x 0000:07:00.5: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xfffffffffffffffc flags=0x0030]
апр 08 21:40:24 ZAX512L kernel: snd_pci_acp6x 0000:07:00.5: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xfffffffffffffffc flags=0x0030]

Output of dmesg -T | grep -i "error\|warn\|fail":

[Вт апр  8 22:34:44 2025] hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
[Вт апр  8 22:34:44 2025] RAS: Correctable Errors collector initialized.
[Вт апр  8 22:34:44 2025] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.OKEC], AE_NOT_FOUND (20240827/psargs-332)
[Вт апр  8 22:34:44 2025] ACPI Error: Aborting method \_SB.GPIO._EVT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[Вт апр  8 22:35:05 2025] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

I'm unsure what to do. Any help would be greatly appreciated!

GMP · 2025-04-08 21:29:25

Gricenchos wrote:

Hello!
For a couple of days now I've been experiencing random freezes and (rarely) reboots. I'm using Lenovo Legion 7 16ARHA7, Ryzen 9 and Radeon graphics...

Hi Gricentos, welcome to the forums! Your logs point to two likely culprits:

1. ACPI Errors:
   ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0.OKEC]
   ACPI Error: Aborting method \_SB.GPIO._EVT

2. AMD-Vi IOMMU Faults:
   snd_pci_acp6x 0000:07:00.5: AMD-Vi: Event logged [IO_PAGE_FAULT...]

Recommended steps:

1. Test these kernel parameters (add to `GRUB_CMDLINE_LINUX` in `/etc/default/grub`):
- `acpi_osi=Linux`
- `amd_iommu=off`
(Run `sudo grub-mkconfig -o /boot/grub/grub.cfg` after editing)

2. Update your BIOS (current: `KFCN30WW` from 2022)

3. Try linux-zen kernel for better hardware support.

Start with #1 and report back – we can refine further based on results!

Last edited by GMP (2025-04-08 21:51:27)

Gricenchos · 2025-04-08 23:06:54

Thank you for the recommendations!

I will start with the kernel parameters, but since I've found no easy way to reproduce the freeze, it might take me a bit of time to return with the findings. Regarding the kernels: I've tried switching to linux-lts kernel, but that didn't fix the issue. Will try zen if the issue persists after adding the kernel parameters.

seth · 2025-04-09 15:15:14

https://wiki.archlinux.org/title/Ryzen#Troubleshooting
Spontanous reboots mean one or more of
* underpowered
* overheated
* broken CPU
* broken RAM

Rebooting w/ the power button will lose all relevant journal logs, see whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) works (but in case it's your CPU: "no it won't")

Ftr, the zen kernel has nothing to do with the AMD Ryzen architecture, they both engage in what might be called cultural appropriation (and these days will get you cancelled, but before was just a sign of great affection…)
https://github.com/zen-kernel/zen-kernel/wiki/FAQ

Gricenchos · 2025-04-11 04:42:54

GMP wrote:

1. Test these kernel parameters (add to `GRUB_CMDLINE_LINUX` in `/etc/default/grub`):
- `acpi_osi=Linux`
- `amd_iommu=off`
(Run `sudo grub-mkconfig -o /boot/grub/grub.cfg` after editing)

It's been three days of uptime for me, these parameters seems to have helped. Thank you!

Gricenchos · 2025-04-15 14:26:44

Update: the issue seems to have resurfaced. Linux-zen allowed me to capture the kernel panic report, and it looks like this:

Arch: x86_64
Version: 6.14.2-zen1-1-zen
[ 3101.266396] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[ 3101.317091] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[ 3101.318857] [drm] kiq ring mec 2 pipe 1 q 0
[ 3101.324607] [drm] DMUB hardware initialized: version=0x02020020
[ 3102.528243] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
[ 3102.528276] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 3102.528278] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
[ 3102.528279] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
[ 3102.528281] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
[ 3102.528283] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[ 3102.528284] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[ 3102.528285] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[ 3102.528287] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[ 3102.528288] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[ 3102.528289] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[ 3102.528291] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
[ 3102.528292] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
[ 3102.528294] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 14 on hub 0
[ 3102.528295] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[ 3102.528297] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[ 3102.528298] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[ 3102.528300] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
[ 3102.535624] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
[ 9123.229522] BUG: kernel NULL pointer dereference, address: 0000000000000007
[ 9123.229535] #PF: supervisor instruction fetch in kernel mode
[ 9123.229542] #PF: error_code(0x0010) - not-present page
[ 9123.229548] PGD 0 P4D 0 
[ 9123.229558] Oops: Oops: 0010 [#1] PREEMPT SMP NOPTI
[ 9123.229566] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.14.2-zen1-1-zen #1 218dc6f0ba61db4f373647be0c0a9ff09a60d2a9
[ 9123.229576] Hardware name: LENOVO 82UG/LNVNB161216, BIOS KFCN30WW 08/10/2022
[ 9123.229582] RIP: 0010:0x7
[ 9123.229636] Code: Unable to access opcode bytes at 0xffffffffffffffdd.
[ 9123.229641] RSP: 0018:ffffae3a40003f80 EFLAGS: 00010216
[ 9123.229648] RAX: 0000000000000001 RBX: 0000000000000002 RCX: 0000000000000008
[ 9123.229653] RDX: 0000000000000009 RSI: 000000010079d29b RDI: 0000000000000009
[ 9123.229658] RBP: 0000000000000002 R08: ffff957642462800 R09: 0000000000000101
[ 9123.229663] R10: ffffffffa6407100 R11: 00000000000003e8 R12: ffffffffa6407108
[ 9123.229667] R13: 0000000000000007 R14: 0000000000000101 R15: 0000000000000009
[ 9123.229672] FS:  0000000000000000(0000) GS:ffff957b46200000(0000) knlGS:0000000000000000
[ 9123.229678] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9123.229683] CR2: ffffffffffffffdd CR3: 0000000106eca000 CR4: 0000000000f50ef0
[ 9123.229688] PKRU: 55555554
[ 9123.229692] Call Trace:
[ 9123.229701]  <IRQ>
[ 9123.229707]  ? handle_softirqs+0xd8/0x2b0
[ 9123.229721]  ? srso_alias_return_thunk+0x5/0xfbef5
[ 9123.229730]  ? irq_exit_rcu+0xd7/0x100
[ 9123.229738]  ? sysvec_apic_timer_interrupt+0x71/0x90
[ 9123.229746]  </IRQ>
[ 9123.229750]  <TASK>
[ 9123.229755]  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
[ 9123.229768]  ? cpuidle_enter_state+0xc6/0x800
[ 9123.229780]  ? cpuidle_enter+0x2d/0x40
[ 9123.229788]  ? do_idle+0x1ad/0x210
[ 9123.229798]  ? cpu_startup_entry+0x29/0x30
[ 9123.229805]  ? rest_init+0xcc/0xd0
[ 9123.229813]  ? start_kernel+0x989/0x990
[ 9123.229824]  ? x86_64_start_reservations+0x24/0x30
[ 9123.229833]  ? x86_64_start_kernel+0x95/0xa0
[ 9123.229841]  ? common_startup_64+0x13e/0x141
[ 9123.229855]  </TASK>
[ 9123.229859] Modules linked in: uinput ccm snd_seq_dummy rfcomm snd_hrtimer snd_seq snd_seq_device cmac algif_hash algif_skcipher af_alg bnep snd_ctl_led snd_soc_acp6x_mach snd_soc_dmic snd_acp6x_pdm_dma snd_sof_amd_acp70 snd_sof_amd_acp63 snd_sof_amd_vangogh vfat fat amd_atl intel_rapl_msr snd_sof_amd_rembrandt intel_rapl_common snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof amdgpu snd_sof_utils snd_pci_ps mt7921e snd_soc_acpi_amd_match snd_amd_sdw_acpi mt7921_common soundwire_amd mt792x_lib soundwire_generic_allocation kvm_amd snd_hda_codec_realtek soundwire_bus mt76_connac_lib snd_hda_codec_generic mt76 snd_hda_scodec_cs35l41_spi snd_soc_sdca snd_hda_scodec_component snd_hda_codec_hdmi amdxcp snd_soc_core kvm gpu_sched snd_hda_intel mac80211 snd_compress drm_panel_backlight_quirks snd_intel_dspcfg ac97_bus drm_buddy uvcvideo drm_exec snd_intel_sdw_acpi snd_pcm_dmaengine polyval_clmulni videobuf2_vmalloc drm_suballoc_helper polyval_generic snd_rpl_pci_acp6x uvc ghash_clmulni_intel
[ 9123.230039]  snd_hda_codec think_lmi drm_ttm_helper snd_hda_scodec_cs35l41_i2c snd_acp_pci sha512_ssse3 videobuf2_memops libarc4 spd5118 ttm snd_acp_legacy_common snd_hda_scodec_cs35l41 btusb sha256_ssse3 videobuf2_v4l2 snd_hda_core ideapad_laptop snd_pci_acp6x btrtl sha1_ssse3 i2c_algo_bit snd_hda_cs_dsp_ctls hid_multitouch firmware_attributes_class snd_pci_acp5x wmi_bmof drm_display_helper videobuf2_common snd_hwdep snd_soc_cs_amp_lib sp5100_tco snd_rn_pci_acp3x platform_profile btintel aesni_intel cfg80211 snd_soc_cs35l41_lib cec ucsi_acpi sparse_keymap snd_pcm btbcm snd_acp_config crypto_simd videodev cs_dsp typec_ucsi btmtk snd_soc_acpi i2c_piix4 video snd_timer cryptd bluetooth typec snd rapl mc pcspkr k10temp mousedev i2c_smbus ccp soundcore snd_pci_acp3x rfkill roles wmi joydev i2c_hid_acpi serial_multi_instantiate i2c_hid acpi_tad amd_pmc psmouse mac_hid pkcs8_key_parser i2c_dev crypto_user loop dm_mod nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress ip_tables x_tables hid_logitech_hidpp
[ 9123.230260]  hid_logitech_dj hid_generic usbhid serio_raw rtsx_pci_sdmmc atkbd mmc_core libps2 nvme vivaldi_fmap nvme_core i8042 rtsx_pci nvme_auth serio
[ 9123.230309] CR2: 0000000000000007
[ 9123.230316] ---[ end trace 0000000000000000 ]---
[ 9123.230322] RIP: 0010:0x7
[ 9123.230338] Code: Unable to access opcode bytes at 0xffffffffffffffdd.
[ 9123.230343] RSP: 0018:ffffae3a40003f80 EFLAGS: 00010216
[ 9123.230350] RAX: 0000000000000001 RBX: 0000000000000002 RCX: 0000000000000008
[ 9123.230355] RDX: 0000000000000009 RSI: 000000010079d29b RDI: 0000000000000009
[ 9123.230361] RBP: 0000000000000002 R08: ffff957642462800 R09: 0000000000000101
[ 9123.230365] R10: ffffffffa6407100 R11: 00000000000003e8 R12: ffffffffa6407108
[ 9123.230371] R13: 0000000000000007 R14: 0000000000000101 R15: 0000000000000009
[ 9123.230376] FS:  0000000000000000(0000) GS:ffff957b46200000(0000) knlGS:0000000000000000
[ 9123.230382] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9123.230387] CR2: ffffffffffffffdd CR3: 0000000106eca000 CR4: 0000000000f50ef0
[ 9123.230392] PKRU: 55555554
[ 9123.230397] Kernel panic - not syncing: Fatal exception in interrupt
[ 9123.230656] Kernel Offset: 0x22e00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)

seth wrote:

https://wiki.archlinux.org/title/Ryzen#Troubleshooting
Spontanous reboots mean one or more of
* underpowered
* overheated
* broken CPU
* broken RAM
Rebooting w/ the power button will lose all relevant journal logs, see whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) works (but in case it's your CPU: "no it won't")

SysRq shortcuts didn't work during that. I've looked though the troubleshooting section, and it seems to suggest to increase CPU voltage: is that relevant? I've never done this before, where can I read on that?

seth · 2025-04-15 20:01:39

[ 9123.229768]  ? cpuidle_enter_state+0xc6/0x800
[ 9123.229780]  ? cpuidle_enter+0x2d/0x40
[ 9123.229788]  ? do_idle+0x1ad/0x210
[ 9123.229798]  ? cpu_startup_entry+0x29/0x30

Did you see the Ryzen troubleshooting page?

Gricenchos · 2025-04-17 05:20:04

seth wrote:

[ 9123.229768]  ? cpuidle_enter_state+0xc6/0x800
[ 9123.229780]  ? cpuidle_enter+0x2d/0x40
[ 9123.229788]  ? do_idle+0x1ad/0x210
[ 9123.229798]  ? cpu_startup_entry+0x29/0x30

Did you see the Ryzen troubleshooting page?

Yes, I did. I'm going through the recommendations there, but so far none of them worked, and trying them out takes time, since I can't easily reproduce the kernel panic.
The issue always appears on exiting suspend, at least that I've narrowed down.

seth · 2025-04-17 06:45:38

limiting the c-state will likely prevent that particular panic (the question is to which value) but for the reboots you're looking at offsetting the curve optimizer, +4pt being a useful initial value.
If you can run windows on that system, corecycler seems to be reliable in triggering that problem.

always appears on exiting suspend, at least that I've narrowed

https://wiki.archlinux.org/title/Intel_ … up_from_S3 (ignore the context, similar approach might work)

Gricenchos · 2025-04-17 16:40:09

seth wrote:

limiting the c-state will likely prevent that particular panic (the question is to which value) but for the reboots you're looking at offsetting the curve optimizer, +4pt being a useful initial value.
If you can run windows on that system, corecycler seems to be reliable in triggering that problem.
always appears on exiting suspend, at least that I've narrowed
https://wiki.archlinux.org/title/Intel_ … up_from_S3 (ignore the context, similar approach might work)

I've tried limiting the c-state with processor.max_cstate=5 parameter, it didn't help. I've also tried to set rcu_nocbs=0-15, similarly to no avail. The random reboots have stopped on their own, now I consistently get the kernel panic state, not just freeze or reboot (if there was any difference to begin with). Mostly on exiting suspend, it seems, but one time it happened without that.

I haven't tried updating UEFI, as I've never done that before.

seth · 2025-04-17 20:18:38

Try "processor.max_cstate=1" and would you have to update the UEFI to adjust the curve optimizer?

Gricenchos · 2025-04-18 05:41:50

seth wrote:

Try "processor.max_cstate=1" and would you have to update the UEFI to adjust the curve optimizer?

Trying that parameter right now.

Regarding the second question: no idea. I don't have windows partition on that laptop (and would rather avoid getting it), and I've never really delved into the UEFI settings. I'll look into it.

GMP · 2025-04-18 11:37:30

The panic confirms it’s crashing in a low-power idle path:

cpuidle_enter_state → do_idle → cpu_startup_entry

This puts the spotlight on firmware and C-state transitions — exactly where Ryzen mobile tends to fail without platform-specific BIOS fixes.

1. Update your BIOS
Current version: KFCN30WW (2022-08-10)
Available update: K9CN46WW — Lenovo’s support site lists it for your model (Legion 7 16ARHA7).
→ Download the latest BIOS update ISO or extract the update to a FAT32 USB and flash via UEFI.

Yes, this can be done without Windows. No excuse to skip this step.

2. While in UEFI, check these:

Disable “Modern Standby” if present
Check AMD CBS → CPPC, C-State settings
If a Curve Optimizer offset is applied (undervolting): reset it

This platform has known issues if C6 or undervolting is involved.

3. About linux-zen
To clarify for @seth and others: `linux-zen` is not “for Zen CPUs,” but it does apply different kernel configs — including scheduler, preempt, and I/O choices — that can affect behavior under load or power transitions. In this case, it didn’t solve the issue but gave us the first panic trace, which makes it the most useful kernel tested so far. That alone justifies trying it.

---

Update the BIOS and check UEFI config. That’s the lowest layer still untouched — and the one most likely to fix resume-related panics.

Gricenchos · 2025-04-18 16:04:40

Update: 'processor.max_cstate=1' didn't help, still got kernel panic after about 11h of uptime.

GMP wrote:

The panic confirms it’s crashing in a low-power idle path:
cpuidle_enter_state → do_idle → cpu_startup_entry
This puts the spotlight on firmware and C-state transitions — exactly where Ryzen mobile tends to fail without platform-specific BIOS fixes.
1. Update your BIOS
Current version: KFCN30WW (2022-08-10)
Available update: K9CN46WW — Lenovo’s support site lists it for your model (Legion 7 16ARHA7).
→ Download the latest BIOS update ISO or extract the update to a FAT32 USB and flash via UEFI.
Yes, this can be done without Windows. No excuse to skip this step.
2. While in UEFI, check these:
Disable “Modern Standby” if present
Check AMD CBS → CPPC, C-State settings
If a Curve Optimizer offset is applied (undervolting): reset it
This platform has known issues if C6 or undervolting is involved.

I'll start with updating the BIOS. For some reason I can only find it in .exe format on Lenovo's support page? Strange.

Edit: the options mentioned aren't in UEFI at all, and updating BIOS might require making a windows partition, at least according to the Lenovo forums.

Edit #2: after removing all the kernel parameters, the situation has returned to what it was before: just black screen freeze.

Edit #3: parameter 'pci=nomsi' makes it so that loading into any of the kernels doesn't work at all. The laptop simply freezes.

Last edited by Gricenchos (2025-04-18 18:07:45)

seth · 2025-04-18 18:26:24

Update: 'processor.max_cstate=1' didn't help, still got kernel panic after about 11h of uptime.

With "cpuidle_enter_state" in the stack trace?

Last edited by seth (2025-04-18 18:26:38)

GMP · 2025-04-19 08:33:17

Thanks for the detailed follow-ups — that helps narrow things down.

1. `processor.max_cstate=1` didn't help → scratch C-states as root cause.

2. BIOS update blocked → that's the real problem now.
Lenovo distributes firmware in Windows-only `.exe` format, and doesn't always provide `.iso` or `.img`.
That’s not unusual — it’s just vendor lock-in. A few paths to try:

Try extracting the `.exe` using one of the following (run from terminal):
- `7z x BIOS.exe` → works on many InnoSetup/NSIS/ZIP-packed Lenovo flashers
- `cabextract BIOS.exe` → useful if the `.exe` contains CAB archive
- `innoextract BIOS.exe` → for Inno Setup-based installers
Some `.exe` files extract a `.hdr`, `.rom`, or `.img` — usable with `fwupd`, UEFI shell, or bootable USB tools
Search https://winraid.level1techs.com/ — they maintain threads on BIOS flashing tools and recovery options (especially for Lenovo, Dell, HP)
Fallback: Windows-to-Go on USB → boot it, flash, wipe it

If BIOS stays outdated, no kernel parameter gymnastics will fix broken suspend handling at firmware level.

3. UEFI config locked down → not unexpected for Lenovo consumer-grade systems.

4. `pci=nomsi` breaking boot → expected. MSI is critical for amdgpu + NVMe + IOMMU. Don’t use it.

5. You're back to square one: unstable suspend/resume, now confirmed not solvable from the OS side.

Your best path forward is forcing a BIOS update one way or another. Let us know what format you can extract from the `.exe`, we can go from there.

Gricenchos · 2025-04-20 05:58:24

seth wrote:

Update: 'processor.max_cstate=1' didn't help, still got kernel panic after about 11h of uptime.
With "cpuidle_enter_state" in the stack trace?

I'm sorry, I didn't record the trace that time.

GMP wrote:

Your best path forward is forcing a BIOS update one way or another. Let us know what format you can extract from the `.exe`, we can go from there.

I've managed to update BIOS via a live windows USB, but on itself that still didn't fix the issue. Got kernel panic on entering suspend after about 24h of uptime, sadly didn't record the trace. No kernel parameters whatsoever.

Last edited by Gricenchos (2025-04-20 06:01:11)

seth · 2025-04-20 06:41:05

But it does panic, not spontanously reboot?
Set "processor.max_cstate=1 amd_iommu=off" again and then lets see what the backtraces look like now

Gricenchos · 2025-04-20 06:54:37

seth wrote:

But it does panic, not spontanously reboot?
Set "processor.max_cstate=1 amd_iommu=off" again and then lets see what the backtraces look like now

Yes, it does panic.

Will do and return with the findings.

Edit: what kernel should I be testing this on? Linux, lts or zen?

Last edited by Gricenchos (2025-04-20 06:55:55)

seth · 2025-04-20 07:15:56

If they all cause that: doesn't matter.
If it's limited to one of them, that's important information.

GMP · 2025-04-20 07:44:00

Good, this gives us clarity.

1. Panic still occurring post-BIOS update confirms it's not a firmware-level fixable bug.

2. Resume path is still the suspect → especially with GPU/IOMMU/ACPI interactions.

Reintroduce the previous mitigations:

processor.max_cstate=1 amd_iommu=off

Use them together — they target slightly different subsystems (power mgmt + memory mapping).

3. Kernel suggestions:

`linux` → baseline test
`linux-lts` → sanity check for regressions
`linux-zen` → useful for visibility, already gave us useful backtraces earlier

Doesn't matter which one *you* prefer — test all 3, same conditions, same boot params. If it panics, capture the trace immediately:

journalctl -b -1 -k

We’ll dissect from there. No point in further guessing without a trace.

GMP · 2025-04-20 11:40:03

Gricenchos wrote:
I've managed to update BIOS via a live windows USB, but on itself that still didn't fix the issue. Got kernel panic on entering suspend after about 24h of uptime, sadly didn't record the trace. No kernel parameters whatsoever.

Also, please post the output of the following:

sudo dmidecode -t bios

Gricenchos · 2025-04-21 05:01:14

With the given parameters, I've got the uptime of 22h without kernel panics. Still a bit wary, admittedly.

GMP wrote:

Gricenchos wrote:
I've managed to update BIOS via a live windows USB, but on itself that still didn't fix the issue. Got kernel panic on entering suspend after about 24h of uptime, sadly didn't record the trace. No kernel parameters whatsoever.
Also, please post the output of the following:
sudo dmidecode -t bios

# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.4.0 present.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
        Vendor: LENOVO
        Version: KFCN42WW
        Release Date: 12/03/2024
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 32 MB
        Characteristics:
                PCI is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                EDD is supported
                Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
                Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
                5.25"/360 kB floppy services are supported (int 13h)
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 kB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                8042 keyboard services are supported (int 9h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                BIOS boot specification is supported
                Targeted content distribution is supported
                UEFI is supported
        BIOS Revision: 1.42
        Firmware Revision: 1.41

Handle 0x001C, DMI type 13, 22 bytes
BIOS Language Information
        Language Description Format: Long
        Installable Languages: 4
                en|US|iso8859-1
                fr|FR|iso8859-1
                ja|JP|unicode
                zh|TW|unicode
        Currently Installed Language: en|US|iso8859-1

KFCN42WW is the latest BIOS for Legion S7 16ARHA7.

Gricenchos · 2025-04-21 13:59:32

Sadly, the issue has resurfaced. Not during a suspend at all. Standard Linux kernel, parameters 'processor.max_cstate=1 amd_iommu=off'.

Output of journalctl -b -1 -k:

http://0x0.st/8OhB.txt

Kernel panic report:

https://tinyurl.com/yc57j72a

davidovitch · 2025-04-21 16:10:52

processor.max_cstate=1

I've observed that for some hardware configurations that doesn't help either. What worked for me (on much older hardware than yours) was to disable the C-States in the BIOS/UEFI. On ASUS based BIOS/EUFI this means:

Advanced > AMD CBS
* set "Power Supply idle control" to "Typical Current Idle"
* Disable Global C State Control

Arch Linux

#1 2025-04-08 20:10:38

Random system freezes/reboots

#2 2025-04-08 21:29:25

Re: Random system freezes/reboots

#3 2025-04-08 23:06:54

Re: Random system freezes/reboots

#4 2025-04-09 15:15:14

Re: Random system freezes/reboots

#5 2025-04-11 04:42:54

Re: Random system freezes/reboots

#6 2025-04-15 14:26:44

Re: Random system freezes/reboots

#7 2025-04-15 20:01:39

Re: Random system freezes/reboots

#8 2025-04-17 05:20:04

Re: Random system freezes/reboots

#9 2025-04-17 06:45:38

Re: Random system freezes/reboots

#10 2025-04-17 16:40:09

Re: Random system freezes/reboots

#11 2025-04-17 20:18:38

Re: Random system freezes/reboots

#12 2025-04-18 05:41:50

Re: Random system freezes/reboots

#13 2025-04-18 11:37:30

Re: Random system freezes/reboots

#14 2025-04-18 16:04:40

Re: Random system freezes/reboots

#15 2025-04-18 18:26:24

Re: Random system freezes/reboots

#16 2025-04-19 08:33:17

Re: Random system freezes/reboots

#17 2025-04-20 05:58:24

Re: Random system freezes/reboots

#18 2025-04-20 06:41:05

Re: Random system freezes/reboots

#19 2025-04-20 06:54:37

Re: Random system freezes/reboots

#20 2025-04-20 07:15:56

Re: Random system freezes/reboots

#21 2025-04-20 07:44:00

Re: Random system freezes/reboots

#22 2025-04-20 11:40:03

Re: Random system freezes/reboots

#23 2025-04-21 05:01:14

Re: Random system freezes/reboots

#24 2025-04-21 13:59:32

Re: Random system freezes/reboots

#25 2025-04-21 16:10:52

Re: Random system freezes/reboots

Board footer