You are not logged in.
Im on a fresh arch install, I checked htop right now and my 100%+ CPU is taken by " /usr/lib/systemd/systemd-journald " .
Last edited by Acehub (2024-10-26 14:02:42)
Offline
somehow issue is fixed now. I booted into windows, then restarted and then booted into arch and now its running smoothly.
Last edited by Acehub (2024-10-26 12:40:04)
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Also see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Check the previous journal ("sudo journalctl -b -1"), something has likely been spamming it and journald is simply not very good at handling this kind of overload.
Offline
If it happens again, in a separate console, do a "journalctl -f" to follow the journal messaging. "ctrl-c" to exit.
Check journal disk usage.
journalctl --disk-usage
Check messages with priority: emerg, alert, crit, and err. Change boot number as needed (journalctl --list-boots).
journalctl --boot=-1 --priority=3
Check for failed units. When a unit fails it may retry multiple times.
systemctl --failed
Check startup for units that may be clogging up the startup process for some reason. Not perfect, but it could help.
systemd-analyze blame or systemd-analyze critical-chain
Offline
Noted, thanks!
The issue occurs ONLY if I shutdown my laptop, and boot straight into linux. Currently I first boot into windows first then do reboot, and then finally boot into windows.
Offline