Hi there,
since a few weeks (maybe even a few months) I get random freezes of my UI (using Wayland and sway x64). The rest of the system is running (e.g. music is still playing in the background and even video calls are continuing - the others see a frozen picture of me but can hear me and I can hear them). But I cannot switch to console (ctrl+alt+[1-9]) so I need to press the power button to restart my PC.
Now, since a few days, the freezes are occurring multiple times a day. I tried to tackle the triggers down and in journalctl always one line appears when the UI crashes:
kernel: sched: RT throttling activated
The last time it crashed I waited some time before rebooting. Then I checked with journalctl
and this is literally the only entry at this time. Here are the logs with timestamps. The GUI froze at 17:37.
Feb 01 17:35:01 [PCNAME]> rtkit-daemon[1111]: Supervising 9 threads of 6 processes of 1 users.
Feb 01 17:35:01 [PCNAME]> rtkit-daemon[1111]: Supervising 9 threads of 6 processes of 1 users.
Feb 01 17:35:07 [PCNAME]> rtkit-daemon[1111]: Supervising 9 threads of 6 processes of 1 users.
Feb 01 17:35:07 [PCNAME]> rtkit-daemon[1111]: Supervising 9 threads of 6 processes of 1 users.
Feb 01 17:37:35 [PCNAME]> kernel: sched: RT throttling activated
Feb 01 17:38:00 [PCNAME]> systemd[1]: Started Refresh existing keys of archlinux-keyring.
Feb 01 17:38:00 [PCNAME]> archlinux-keyring-wkd-sync[7611]: Skipping key 91C7BE39F7D158E8E518C7D957247034E31EC72A with UID pacman@localhost...
[keyring process continues...]
Feb 01 17:38:15 [PCNAME]> archlinux-keyring-wkd-sync[7611]: Error refreshing key 48C3B1F30DDD0FE67E516D16396E3E25BAB142C1 with UID keenerd@archlinux.org.
Feb 01 17:38:15 [PCNAME]> systemd[1]: archlinux-keyring-wkd-sync.service: Main process exited, code=exited, status=1/FAILURE
Feb 01 17:38:15 [PCNAME]> systemd[1]: archlinux-keyring-wkd-sync.service: Failed with result 'exit-code'.
Feb 01 17:38:15 [PCNAME]> systemd[1]: archlinux-keyring-wkd-sync.service: Consumed 1.314s CPU time.
Feb 01 17:38:16 [PCNAME]> rtkit-daemon[1111]: Supervising 9 threads of 6 processes of 1 users.
Feb 01 17:38:16 [PCNAME]> rtkit-daemon[1111]: Supervising 9 threads of 6 processes of 1 users.
Feb 01 17:38:21 [PCNAME]> systemd-logind[808]: Power key pressed short.
Feb 01 17:38:21 [PCNAME]> systemd-logind[808]: Powering off...
Feb 01 17:38:21 [PCNAME]> systemd-logind[808]: System is powering down.
Feb 01 17:38:21 [PCNAME]> polkitd[1279]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.42, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Feb 01 17:38:21 [PCNAME]> greetd[7863]: config: Config { file: ConfigFile { terminal: ConfigTerminal { vt: None, switch: false }, general: ConfigGeneral { source_profile: true, runfile: "/run/greetd.run" }, default_session: ConfigSession { command: "", user: "" }, initial_session: None }, internal: ConfigInternal { session_worker: 11 } }
Feb 01 17:38:21 [PCNAME]> systemd[1]: Stopping Session 3 of User [USERNAME]...
Feb 01 17:38:21 [PCNAME]> systemd[1]: Removed slice Slice /system/getty.
Feb 01 17:38:21 [PCNAME]> kernel: traps: 1password[4194] trap int3 ip:55c232cc6a14 sp:7ffe83aa24a0 error:0 in 1password[55c22f939000+71c3000]
Feb 01 17:38:21 [PCNAME]> systemd[1]: Removed slice Slice /system/modprobe.
[shutdown process continues... until next snippet with wayland errors and sourrounding logs]
Feb 01 17:38:21 [PCNAME]> systemd[1]: Stopped CUPS Scheduler.
Feb 01 17:38:21 [PCNAME]> systemd[1]: greetd.service: Deactivated successfully.
Feb 01 17:38:21 [PCNAME]> systemd[1]: Stopped Greeter daemon.
Feb 01 17:38:21 [PCNAME]> systemd[1]: ntpd.service: Deactivated successfully.
Feb 01 17:38:21 [PCNAME]> mkinitcpio[7953]: ==> Build complete.
Feb 01 17:38:21 [PCNAME]> foot[2008]: err: wayland.c:1405: failed to read events from the Wayland socket: Broken pipe
Feb 01 17:38:21 [PCNAME]> foot[2008]: err: wayland.c:1942: failed to flush wayland socket: Broken pipe
Feb 01 17:38:21 [PCNAME]> foot[2008]: wayland: failed to read events from the Wayland socket: Broken pipe
Feb 01 17:38:21 [PCNAME]> foot[2008]: wayland: failed to flush wayland socket: Broken pipe
Feb 01 17:38:21 [PCNAME]> systemd[1189]: foot-server.service: Main process exited, code=exited, status=230/PERSONALITY
Feb 01 17:38:21 [PCNAME]> systemd[1189]: foot-server.service: Failed with result 'exit-code'.
Feb 01 17:38:21 [PCNAME]> bluetoothd[806]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSource/ldac
Feb 01 17:38:21 [PCNAME]> bluetoothd[806]: Endpoint unregistered: sender=:1.52 path=/MediaEndpoint/A2DPSink/aptx_hd
[shutdown process continues...until next snippet with bluetooth error and sourrounding logs]
Feb 01 17:38:21 [PCNAME]> systemd[1]: session-3.scope: Deactivated successfully.
Feb 01 17:38:21 [PCNAME]> systemd[1]: Stopped Session 3 of User [USERNAME].
Feb 01 17:38:21 [PCNAME]> systemd[1]: session-3.scope: Consumed 10min 49.830s CPU time.
Feb 01 17:38:21 [PCNAME]> systemd-logind[808]: Session 3 logged out. Waiting for processes to exit.
Feb 01 17:38:21 [PCNAME]> dbus-broker-launch[800]: Activation request for 'org.bluez' failed.
Feb 01 17:38:21 [PCNAME]> systemd-logind[808]: Removed session 3.
Feb 01 17:38:22 [PCNAME]> systemd[1]: Removed slice Slice /system/syncthing.
Feb 01 17:38:22 [PCNAME]> systemd[1]: system-syncthing.slice: Consumed 7.109s CPU time.
Feb 01 17:38:22 [PCNAME]> systemd[1]: Stopped target Network is Online.
[shutdown process continues until end]
A few more information:
uname -r
6.1.71-1-MANJARO
pamac checkupdates
Your system is up to date.
cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 25
model : 80
model name : AMD Ryzen 7 5700G with Radeon Graphics
stepping : 0
microcode : 0xa50000f
cpu MHz : 1400.000
cache size : 512 KB
So I have no idea how to continue from here. Since at the other crashes the line kernel: sched: RT throttling activated
always appeared this is currently my best bet. As far as I understand, some processes might declare themselves as real-time processes. I have never even tempered with RT things (and until now I didnât know you can seemingly mix them with a non-RT system).
So I hope that someone can point me in a direction to go.