Hi all,
after installing Manjaro, everything works fine. However, as soon as I run all the available updates, following symptoms appear:
- the boot time after logging in takes a long time
- after syspending the system, it does not wake up anymore
- seemingly random things take a very long time to complete or hang completely, e.g.
sudo desgorinxi --full --admin --filter --width(only runninginxiworks fine
I would be very happy about any suggestions of how to solve these problems.
Here are a few infos about my system.
inxi --full --admin --filter --width QUIT ✘ 25s
System:
Kernel: 6.11.10-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.11-x86_64
root=UUID=2af16c25-4ce7-4283-9d8c-1834f2d55f95 rw quiet splash apparmor=1
security=apparmor udev.log_priority=3
Desktop: GNOME v: 47.2 tk: GTK v: 3.24.43 wm: gnome-shell
tools: gsd-screensaver-proxy dm: GDM v: 47.0 Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG STRIX B650E-F GAMING WIFI v: Rev 1.xx
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3057 date: 10/29/2024
CPU:
Info: model: AMD Ryzen 7 9700X bits: 64 type: MT MCP arch: N/A level: v4
note: check family: 0x1A (26) model-id: 0x44 (68) stepping: 0
microcode: 0xB404023
Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
smt: enabled cache: L1: 640 KiB desc: d-8x48 KiB; i-8x32 KiB L2: 8 MiB
desc: 8x1024 KiB L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 2991 min/max: 600/5581 boost: enabled scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 2991 2: 2991 3: 2991
4: 2991 5: 2991 6: 2991 7: 2991 8: 2991 9: 2991 10: 2991 11: 2991 12: 2991
13: 2991 14: 2991 15: 2991 16: 2991 bogomips: 121427
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
This is where the command stops.
systemd-analyze blame INT ✘ 1m 15s
7min 30.811s fprintd.service
30.755s upower.service
5.347s plymouth-quit-wait.service
2.302s systemd-fsck@dev-disk-by\x2duuid-47dca427\x2da852\x2d41f9\x2db636\x2d4dfbbfaa68df.service
2.029s systemd-journald.service
727ms NetworkManager.service
258ms dev-nvme0n1p3.device
146ms user@1000.service
140ms apparmor.service
124ms lvm2-monitor.service
122ms systemd-tmpfiles-setup-dev-early.service
120ms systemd-udev-trigger.service
85ms udisks2.service
71ms power-profiles-daemon.service
67ms systemd-remount-fs.service
66ms systemd-journal-flush.service
65ms colord.service
64ms systemd-tmpfiles-setup.service
61ms systemd-userdbd.service
60ms systemd-timesyncd.service
54ms systemd-random-seed.service
54ms systemd-journal-catalog-update.service
54ms accounts-daemon.service
52ms pamac-daemon.service
51ms home.mount
51ms systemd-update-utmp.service
50ms systemd-timedated.service
46ms ldconfig.service
45ms modprobe@dm_mod.service
45ms bluetooth.service
45ms modprobe@loop.service
42ms user-runtime-dir@1000.service
41ms rtkit-daemon.service
37ms systemd-fsck@dev-disk-by\x2duuid-9BC3\x2dF721.service
36ms systemd-rfkill.service
36ms boot-efi.mount
32ms dev-disk-by\x2ddiskseq-3\x2dpart2.swap
30ms ModemManager.service
29ms tmp.mount
28ms systemd-vconsole-setup.service
24ms systemd-udevd.service
22ms wpa_supplicant.service
21ms polkit.service
16ms plymouth-start.service
15ms dbus-broker.service
14ms systemd-logind.service
14ms systemd-hostnamed.service
13ms systemd-sysusers.service
12ms plymouth-read-write.service
9ms systemd-modules-load.service
9ms cups.service
7ms ufw.service
7ms systemd-tmpfiles-setup-dev.service
7ms dev-hugepages.mount
7ms dev-mqueue.mount
6ms sys-kernel-debug.mount
6ms gdm.service
6ms sys-kernel-tracing.mount
systemd-analyze critical-chain upower.service ✔ 29s
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
upower.service +30.755s
└─basic.target @3.180s
└─dbus-broker.service @3.164s +15ms
└─dbus.socket @3.163s
└─sysinit.target @3.161s
└─systemd-timesyncd.service @3.101s +60ms
└─systemd-tmpfiles-setup.service @3.035s +64ms
└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @3.083s
systemd-analyze critical-chain fprintd.service ✔
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
fprintd.service +7min 30.811s
└─basic.target @3.180s
└─dbus-broker.service @3.164s +15ms
└─dbus.socket @3.163s
└─sysinit.target @3.161s
└─systemd-timesyncd.service @3.101s +60ms
└─systemd-tmpfiles-setup.service @3.035s +64ms
└─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @3.083s
Running
sudo systemctl status run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount
takes a long time and returns
Unit run-credentials-systemdx2dtmpfilesx2dsetup.service.mount could not be found.
This is already the second time I installed Manjaro. The first time, everything looked very similar, except for the fprintd.service not taking so much time.
Thank you in advance for any recommendations!
EDIT:
After some more digging, it might have to do something with a faulty swap configuration?
sudo swapon --show
NAME TYPE SIZE USED PRIO
/dev/nvme0n1p2 partition 19,5G 0B -2
Takes a long time to finally show the output.
Filesystem Size Used Avail Use% Mounted on
dev 16G 0 16G 0% /dev
run 16G 2,3M 16G 1% /run
efivarfs 128K 33K 91K 27% /sys/firmware/efi/efivars
/dev/nvme0n1p3 209G 11G 187G 6% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-journald.service
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-udev-load-credentials.service
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-sysctl.service
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-sysusers.service
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-vconsole-setup.service
tmpfs 16G 18M 16G 1% /tmp
/dev/nvme0n1p1 511M 292K 511M 1% /boot/efi
/dev/nvme1n1p1 1,8T 583G 1,2T 34% /home
tmpfs 1,0M 0 1,0M 0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs 3,1G 308K 3,1G 1% /run/user/1000
I don’t think I have seen so many tmpfs filesystems on my old Manjaro installation.
And this is my /etc/fstab file
# <SNIP>
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=9BC3-F721 /boot/efi vfat umask=0077 0 2
UUID=2af16c25-4ce7-4283-9d8c-1834f2d55f95 / ext4 defaults,noatime 0 1
UUID=47dca427-a852-41f9-b636-4dfbbfaa68df /home ext4 defaults,noatime 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
