Once rock solid Lenovo dual booting Silverblue/Win is now freezing on reboots after wiping Windows

Ask Fedora
1

I’m having frequent freezes on reboot for Fedora 41 on a Lenovo Carbon X Gen 6.

This is happening on both Workstation and Silverblue. I just did a fresh install of the KDE spin and on first reboot (hitting esc for boot info) the system freezes.

Edit: I did a 2nd test of the reboot/freeze and it froze on a slightly earlier step:

systemd-backlight

That makes me think it’s not the specific step that’s causing the freeze, but something else that is happening around the same time in the reboot process.

Finished modprobe@loop.service - Load Kernel Module loop

What’s really odd is that I was running Silverblue since 39 on this same laptop (as a dual boot with Windows) and it was rock solid, always waking from suspend, booting without issue.

I wiped Windows off the device, and have been experiencing this issue ever since. I’m not sure if something happened with BIOS or boot drive that is creating the issue? I’ve tried adjusting BIOS settings but on luck. I had made BIOS setting adjustments with the Fedora/Win dual boot without issue. No recent BIOS/firmware update.

Any help how to troubleshoot this would be much appreciated.

2

Does replacing quiet rhgb with debug on the kernel command line provide additional clues about what might be going wrong?

3

Helpful suggestion. :slight_smile:

The last debug entries are related to bluetooth.

Bluetooth: hci0: Secure boot is enabled
Bluetooth: hci0 OTC lock is enabled
Bluetooth: hci0: API lock is enabled

On a second reboot test, it stopped with:

resource: resource sanity check: requesting [mem ...], which spans more than pnp 00:08 [mem ...]
caller snb_uncore_imc_init_box+... [intel_uncore] mapping multiple BARs

Then similar Bluetooth messages as above and stopped on:

Intel(R) Wireless WiFi drive for Linux

I then went to perform a reset of BIOS settings to defaults and disable secure boot. But still freezing. Will try disabling bluetooth/wifi to see if that has any change.

I’m still perplexed because I didn’t have this issue when Windows was on the laptop. :confused: