Random freezes while starting the system

Ask Fedora
, , , , ,
1

I recently installed Fedora 38 on my Lenovo E14 Gen 2 laptop. So it’s basically a clean installation. After installing the first system updates and doing some restarts, I am experiencing some random freezes while starting the system. The screen freezes, and the laptop does no longer react to mouse or keyboard input. It occurs most of the time as soon as Gnome starts, but I also had it during the boot screen or even in the login manager.

The strange thing is that this only seems to be an issue of boot., once the system has started, it runs stable. Even suspend seems to work without any issues.

I also don’t think it’s some kind of hardware issues. Did a lot of distro hopping during the last weeks and never had any kind of similar issues with other distributions. I think this is now the third time im doing a clean installation of Fedora, but the issue remains.

Here are some messages from the logs, if that helps:

11:05:43 dleyna-renderer: Connector 'dbus' not found
11:02:44 systemd: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2156.scope - Application launched by gnome-session-binary.
11:02:43 gdm-session-wor: gkr-pam: unable to locate daemon control file
11:02:40 kernel: iwlwifi 0000:03:00.0: Unhandled alg: 0x707
11:02:36 bluetoothd: Failed to set mode: Failed (0x03)
11:02:36 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
11:02:34 kernel: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 1.
11:02:28 kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0

Does anyone know what could be the reason for these crashes?

Update: Tried to disable Wayland and use X11 instead like discribed here, but it didn’t help.

2

Hello @alexanderruf ,
Welcome to :fedora: !

Sorry to hear about your issues. Could you try to get the failed boot logs? Use journalctl -b -1 --priority=3 at successful boot to get the proevious (failed) boot errors. if you know how many boots ago it happened change the -1 to the number of boots previous that failed.

3

Hello jakfrost,

So I rebooted several times until the issue occurred again. Then I got the log with journalctl -b -1 --priority=3:

Jul 08 13:33:18 fedora kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
Jul 08 13:33:18 fedora kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 08 13:33:26 lithium (sd-execu[835]: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 1.
Jul 08 13:33:27 lithium kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Jul 08 13:33:27 lithium kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 08 13:33:27 lithium kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 08 13:33:29 lithium kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 08 13:33:29 lithium bluetoothd[1095]: Failed to set mode: Failed (0x03)
Jul 08 13:33:34 lithium gdm-password][1907]: gkr-pam: unable to locate daemon control file
Jul 08 13:33:35 lithium systemd[1973]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2169.scope - Application launched by gnome-session-binary.
Jul 08 13:33:35 lithium systemd[1973]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2171.scope - Application launched by gnome-session-binary.
Jul 08 13:33:35 lithium systemd[1973]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2172.scope - Application launched by gnome-session-binary.
Jul 08 13:34:05 lithium systemd-cryptsetup[3494]: Device luks-c27b2aff-2074-4986-b082-c9af02f7b1c0 is still in use.
Jul 08 13:34:05 lithium systemd-cryptsetup[3494]: Failed to deactivate: Device or resource busy
Jul 08 13:34:05 lithium kernel: watchdog: watchdog0: watchdog did not stop!
4

So you have LUKS encryption installed on your drive? It appears to be the unlocking of your LUKS volume that is causing the errors on signin and the watchdog timer to time out. I don’t use LUKS, haven’t for at least a dogs age, so I’m likely not going to be much help with it. It does appear that something is trying to use the drive at the time an attempt to unlock it is being tried.

5

Thanks. Guess that still might help. I am going to do another fresh re-installation of Fedora without disc encryption and see if that helps.

6

Doesn’t seem to be an issue with disc-encryption, either. Did a fresh installation without disc-encryption, installed the latest system updates sudo dnf update && sudo dnf upgrade and then got this error:

Update: Meanwhile, I’m very confident that this problem is related to Kernel version 6.3.11. Since I have switched back to Kernel version 6.2.9, I didn’t have a single crash and everything runs smooth.

1 Like