Random freezes after upgrade F36 -> F37

Hi,
the upgrade itself to F37 went well, the following updates, too.

But after some time (minutes to an hour) the screen freezes seemingly randomly and I have to reset/reboot. I had no problems with F36, it was very stable. The problem occurs regardless whether I log in with Gnome or Gnome on Xorg.

Any ideas where I can start looking,

last freeze was 11:55 and that waht i got with “journalctl -b -1 --priority=3”

$ journalctl -b -1 --priority=3
Nov 23 11:27:17 bueropc systemd-gpt-auto-generator[669]: Failed to dissect: Permission denied
Nov 23 11:27:17 bueropc systemd[655]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with >
Nov 23 11:27:18 bueropc systemd-udevd[748]: event7: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key co>
Nov 23 11:27:19 bueropc bluetoothd[915]: Failed to set mode: Failed (0x03)
Nov 23 11:27:29 bueropc pipewire[1475]: mod.x11-bell: XOpenDisplay() failed
Nov 23 11:30:29 bueropc gdm-password][1841]: gkr-pam: unable to locate daemon control file
Nov 23 11:30:30 bueropc pipewire[1997]: mod.x11-bell: XOpenDisplay() failed
Nov 23 11:30:31 bueropc systemd[1862]: Failed to start app-gnome-vboxclient-2436.scope - Application launched by>
Nov 23 11:30:33 bueropc gdm-launch-environment][1289]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (obj>
lines 1-9/9 (END)
3 Likes

Can you provide the whole output without --priority=3 ? Feel free to cut it down to the last minute.

Also, feel free to try disabling bluetoothd for some time and check if the problem still appears (if so, check the journalctl to ensure that bluetooth is not shown in the logs before freezing, so to ensure that it was really disabled at the freeze occurance). Bluetooth-related ACPI-issues had occurred in the past. This does of course not mean that you then should no longer use bluetooth at all. We just want to find out if this is related to the cause.

I cannot say if such issues had already appeared in relation to gdm or gnome in general, since I do not use gdm/gnome. Maybe someone else knows more about that (and if so, maybe how to troubleshoot that).

Sadly, there is nothing in the last two minutes before the freeze (freeze 10:12, see log at the end)

Here is another thread with freezes. Maybe related to AMD? I am running a ASUS PRIME A520M-K board with AMD Ryzen™ 5 PRO 4650G with Radeon™ Graphics × 12.

Nov 24 10:08:08 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fwupd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 24 10:08:08 bueropc systemd[1]: fwupd.service: Consumed 1.360s CPU time.
Nov 24 10:08:35 bueropc systemd[1]: flatpak-system-helper.service: Deactivated successfully.
Nov 24 10:08:35 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=flatpak-system-helper comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? >
Nov 24 10:09:06 bueropc gnome-shell[2000]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xa00008 specified for 0xa0001b.
Nov 24 10:09:27 bueropc wpa_supplicant[1169]: wlp5s0: WPA: Group rekeying completed with c8:0e:14:05:a2:d0 [GTK=CCMP]
Nov 24 10:10:07 bueropc systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
Nov 24 10:10:07 bueropc sa1[6822]: Error: File /etc/sensors.d/asusA520M-K, line 5: Parse error in chip name
Nov 24 10:10:07 bueropc systemd[1]: sysstat-collect.service: Deactivated successfully.
Nov 24 10:10:07 bueropc systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Nov 24 10:10:07 bueropc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=s>
Nov 24 10:10:07 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=su>
-- Boot feaa5449b97a4a81b289501be56b98e8 --

No logs at all for two minutes before freezing? Are you sure that the time you use to determine the freezing (10:12 as you said) is synchronous to the system time used by journalctl? Please check if the clock you use to read the freezing time correlates to the time in journalctl logs (e.g., by causing events and then check the logged time).

There are many potential origins. But without further information, the fact that two people with AMD have a freeze is on itself not sufficient to assume that this is AMD-related.


Concerning the logs: the systemd and audit logs are ok. wpa_supplicant can just like bluetooth cause acpi-issues but if causing a freeze, it is unlikely that there is no related log-causing event for >3 minutes: yet, please try if the freeze also happens if wpa_supplicant and bluetooth are disabled (systemctl stop bluetooth & systemctl stop wpa_supplicant → be aware: with these commands, both will be only disabled in the current boot but reactivated with the next boot).

Concerning the gnome-related error, I cannot say much about that. But although I can find this error in past issues, it seems to have not yet been related to full freezes (yet, I have not made a sophisticated search, so feel free to check yourself if you can find this error in circumstances comparable to yours with your preferred search engine). Also, given that the gnome-event is logged some minutes before the freeze, I would also not automatically assume this to be related.


Before going ahead: what is the output of cat /proc/sys/kernel/tainted ? And do you use the nvidia driver?

Thank you for your help.

Kernel tainted is 0

I stopped bluetooth and wpa_supplicant, but freezes were still coming.

A freeze happened while I was reading, so I didn’t notice it right away and there seemed to be some are some line logs after the freeze.

I got a little more patiently when a freeze happens and these are the last logs:

Freeze 13:22

Nov 28 13:24:20 bueropc systemd[1]: sssd-kcm.service: start-pre operation timed out. Terminating.
Nov 28 13:23:37 bueropc gnome-shell[2051]: libinput error: event4  - Logitech M585/M590: client bug: event processing lagging behind by 319ms, your system is too slow
Nov 28 13:22:52 bueropc systemd[1]: Starting sssd-kcm.service - SSSD Kerberos Cache Manager...
Nov 28 13:22:46 bueropc systemd[1]: sssd-kcm.service: Failed with result 'exit-code'.
Nov 28 13:22:52 bueropc gnome-shell[2051]: libinput error: event4  - Logitech M585/M590: client bug: event processing lagging behind by 139ms, your system is too slow
Nov 28 13:22:46 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Nov 28 13:22:46 bueropc systemd[1]: sssd-kcm.service: Main process exited, code=exited, status=70/SOFTWARE
Nov 28 13:21:56 bueropc gnome-shell[2051]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x800008 specified for 0x800478.
Nov 28 13:20:21 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 28 13:20:21 bueropc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 28 13:20:21 bueropc systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Nov 28 13:20:21 bueropc systemd[1]: sysstat-collect.service: Deactivated successfully.
Nov 28 13:20:21 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=flatpak-system-helper comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=suc>
Nov 28 13:20:21 bueropc sa1[9944]: Error: File /etc/sensors.d/asusA520M-K, line 5: Parse error in chip name
Nov 28 13:20:21 bueropc systemd[1]: flatpak-system-helper.service: Deactivated successfully.
Nov 28 13:20:21 bueropc systemd[1]: Starting sysstat-collect.service - system activity accounting tool...

Freeze 12:55

Freeze Nov 28 12:57:39 bueropc systemd[1]: sssd-kcm.service: start-pre operation timed out. Terminating.
Nov 28 12:56:05 bueropc systemd[1]: Starting sssd-kcm.service - SSSD Kerberos Cache Manager...
Nov 28 12:56:05 bueropc systemd[1]: sssd-kcm.service: Consumed 2.543s CPU time.
Nov 28 12:56:05 bueropc systemd[1]: sssd-kcm.service: Failed with result 'exit-code'.
Nov 28 12:56:05 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sssd-kcm comm="system>
Nov 28 12:56:05 bueropc systemd[1]: sssd-kcm.service: Main process exited, code=exited, status=70/SOFTWARE
Nov 28 12:55:05 bueropc gnome-shell[2005]: libinput error: event4  - Logitech M585/M590: client bug: event processing lagging behind by 44ms, your system >
Nov 28 12:55:05 bueropc gnome-shell[2005]: libinput error: event4  - Logitech M585/M590: client bug: event processing lagging behind by 21ms, your system >
Nov 28 12:50:15 bueropc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm=>
Nov 28 12:50:15 bueropc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sysstat-collect comm>
Nov 28 12:50:15 bueropc systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
Nov 28 12:50:15 bueropc systemd[1]: sysstat-collect.service: Deactivated successfully.

Both those log snippets seem to show this may be the culprit.
Are you using kerberos? If not then it seems that disabling that service should not harm and it may be the cause of the freeze.
This is what that service is from

# dnf info sssd-kcm
Last metadata expiration check: 0:07:27 ago on Mon 28 Nov 2022 12:29:08 PM CST.
Installed Packages
Name         : sssd-kcm
Version      : 2.7.4
Release      : 1.fc36
Architecture : x86_64
Size         : 227 k
Source       : sssd-2.7.4-1.fc36.src.rpm
Repository   : @System
From repo    : updates
Summary      : An implementation of a Kerberos KCM server
URL          : https://github.com/SSSD/sssd/
License      : GPLv3+
Description  : An implementation of a Kerberos KCM server. Use this package if you want to
             : use the KCM: Kerberos credentials cache.

The package can be removed by sudo dnf remove sssd-kcm if you choose to do so.