Laptop suddenly takes minutes to log into

hey, yesterday i started my laptop and everything was fine, after rebooting (i have not changed any packages in that session, just browsed the web a bit) it suddenly takes minutes to log into. I have no idea why it does this… The hardened kernel does not boot at all and both the zen and plain linux kernel have this problem
inxi:

System:
  Kernel: 6.7.4-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: hpet avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
    root=UUID=d16ddc96-5d12-402f-bbcb-9fa585484f0b rw rootflags=subvol=@
    cryptdevice=UUID=3c647ba3-56c7-43a5-bafc-5f6213b05312:luks-3c647ba3-56c7-43a5-bafc-5f6213b05312
    root=/dev/mapper/luks-3c647ba3-56c7-43a5-bafc-5f6213b05312
    rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 info: frameworks
    v: 5.115.0 wm: kwin_x11 with: latte-dock vt: 2 dm: SDDM Distro: Garuda
    base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 82C7 v: Lenovo V15-ADA
    serial: <superuser required> Chassis: type: 10 v: Lenovo V15-ADA
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: No DPK serial: <superuser required>
    part-nu: LENOVO_MT_82C7_BU_idea_FM_V15-ADA uuid: <superuser required>
    UEFI: LENOVO v: E8CN30WW date: 07/28/2021
Battery:
  ID-1: BAT0 charge: 18.5 Wh (58.5%) condition: 31.6/35.3 Wh (89.5%)
    power: 5.8 W volts: 7.5 min: 7.6 model: CPT-COS L16C2PB1 type: Li-poly
    serial: <filter> status: discharging cycles: 231
CPU:
  Info: model: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx bits: 64
    type: MT MCP arch: Zen/Zen+ note: check gen: 1 level: v3 note: check
    built: 2019 process: GF 12nm family: 0x17 (23) model-id: 0x18 (24)
    stepping: 1 microcode: 0x8108109
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
    desc: 1x4 MiB
  Speed (MHz): avg: 1458 high: 2100 min/max: 1400/2100 boost: enabled
    scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1223 2: 2100
    3: 1400 4: 1400 5: 1346 6: 1400 7: 1400 8: 1400 bogomips: 33551
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
    vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:15d8
    class-ID: 0300 temp: 36.0 C
  Device-2: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1:2 chip-ID: 13d3:5a08
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: BOE Display 0x0812 built: 2018 res: 1920x1080
    hz: 60 dpi: 142 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.5-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Vega 8 Graphics
    (radeonsi raven LLVM 16.0.6 DRM 3.57 6.7.4-arch1-1) device-ID: 1002:15d8
    memory: 1.95 GiB unified: no
  API: Vulkan v: 1.3.276 layers: 8 device: 0 type: integrated-gpu name: AMD
    Radeon Vega 8 Graphics (RADV RAVEN) driver: mesa radv v: 23.3.5-arch1.1
    device-ID: 1002:15d8 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.3.5-arch1.1 (LLVM
    16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 03:00.1 chip-ID: 1002:15de class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo
    driver: snd_pci_acp3x v: kernel alternate: snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.7.4-arch1-1 status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Lenovo driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 bus-ID: 02:00.0 chip-ID: 168c:003e class-ID: 0280
  IF: wlp2s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-2:3
    chip-ID: 0cf3:e300 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: disabled
    rfk-block: hardware: no software: yes address: N/A
Drives:
  Local Storage: total: 700.51 GiB used: 293.89 GiB (42.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: MZALQ512HALU-000L2 size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: BL2QFXV7 temp: 20.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Crucial model: CT240BX500SSD1
    size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 041 scheme: GPT
Partition:
  ID-1: / raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 293.89 GiB (62.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-3c647ba3-56c7-43a5-bafc-5f6213b05312
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 1.4 MiB (0.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 293.89 GiB (62.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-3c647ba3-56c7-43a5-bafc-5f6213b05312
  ID-4: /var/log raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 293.89 GiB (62.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-3c647ba3-56c7-43a5-bafc-5f6213b05312
  ID-5: /var/tmp raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 293.89 GiB (62.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-3c647ba3-56c7-43a5-bafc-5f6213b05312
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 17.44 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-48d04c79-6793-4578-a7bd-b7f3baa922dc
Sensors:
  System Temperatures: cpu: 36.1 C mobo: N/A gpu: amdgpu temp: 36.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 20 GiB note: est. available: 17.44 GiB used: 3.16 GiB (18.1%)
  Processes: 277 Power: uptime: 7m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.94 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
    tool: systemctl
  Packages: 1769 pm: pacman pkgs: 1713 libs: 438 tools: paru pm: flatpak
    pkgs: 56 Compilers: gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.0
    running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
  System install date:     2022-06-18
  Last full system update: 2024-02-15
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio
  Windows dual boot:       No/Undetected
  Failed units:            

here is my journalctl log from that session:

Please provide also

systemd-analyze blame
systemd-analyze critical-chain
1 Like

blame:

6.247s systemd-cryptsetup@luks\x2d48d04c79\x2d6793\x2d4578\x2da7bd\x2db7f3baa922dc.service
1.483s linux-modules-cleanup.service
1.231s systemd-journal-flush.service
 841ms dev-mapper-luks\x2d3c647ba3\x2d56c7\x2d43a5\x2dbafc\x2d5f6213b05312.device
 438ms systemd-modules-load.service
 343ms systemd-udev-trigger.service
 326ms [email protected]
 300ms systemd-remount-fs.service
 252ms upower.service
 252ms NetworkManager.service
 218ms lvm2-monitor.service
 205ms udisks2.service
 194ms systemd-journald.service
 182ms boot-efi.mount
 163ms systemd-vconsole-setup.service
 139ms [email protected]
 138ms dev-zram0.swap
 136ms power-profiles-daemon.service
 128ms systemd-fsck@dev-disk-by\x2duuid-3AD8\x2d2551.service
 124ms usbguard-dbus.service
 119ms polkit.service
 117ms usbguard.service
 112ms ModemManager.service
  97ms [email protected]
  96ms sys-fs-fuse-connections.mount
  89ms [email protected]
  88ms avahi-daemon.service
  85ms systemd-logind.service
  83ms systemd-udevd.service
  82ms systemd-tmpfiles-setup-dev.service
  80ms [email protected]
  78ms systemd-timesyncd.service
  77ms systemd-tmpfiles-setup.service
  70ms modprobe@dm_mod.service
  68ms systemd-oomd.service
  67ms systemd-sysctl.service
  64ms systemd-binfmt.service
  62ms plymouth-quit.service
  57ms dbus.service
  55ms home.mount
  53ms [email protected]
  53ms plymouth-quit-wait.service
  52ms root.mount
  51ms plymouth-start.service
  48ms plymouth-read-write.service
  48ms srv.mount
  47ms systemd-rfkill.service
  47ms kmod-static-nodes.service
  46ms systemd-cryptsetup@luks\x2d3c647ba3\x2d56c7\x2d43a5\x2dbafc\x2d5f6213b05312.service
  46ms systemd-random-seed.service
  45ms systemd-tmpfiles-setup-dev-early.service
  44ms var-cache.mount
  43ms [email protected]
  42ms var-log.mount
  41ms systemd-backlight@backlight:amdgpu_bl1.service
  40ms var-tmp.mount
  40ms garuda-pacman-snapshot-reject.service
  39ms sys-kernel-tracing.mount
  38ms proc-sys-fs-binfmt_misc.mount
  37ms sys-kernel-debug.mount
  36ms dev-hugepages.mount
  36ms dev-mqueue.mount
  34ms systemd-user-sessions.service
  34ms systemd-tmpfiles-clean.service
  32ms garuda-pacman-lock.service
  28ms systemd-update-utmp.service
  26ms sys-kernel-config.mount
  18ms tmp.mount
  16ms rtkit-daemon.service
  14ms dev-mapper-luks\x2d48d04c79\x2d6793\x2d4578\x2da7bd\x2db7f3baa922dc.swap

critical-chain:

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.

graphical.target @8.684s
└─sddm.service @8.684s
  └─plymouth-quit.service @8.594s +62ms
    └─systemd-user-sessions.service @8.537s +34ms
      └─network.target @8.533s
        └─NetworkManager.service @8.279s +252ms
          └─dbus.service @8.194s +57ms
            └─basic.target @8.172s
              └─sockets.target @8.171s
                └─[email protected] @8.170s
                  └─sysinit.target @8.118s
                    └─systemd-timesyncd.service @8.039s +78ms
                      └─systemd-tmpfiles-setup.service @7.941s +77ms
                        └─local-fs.target @7.930s
                          └─tmp.mount @7.910s +18ms
                            └─swap.target @7.908s
                              └─dev-mapper-luks\x2d48d04c79\x2d6793\x2d4578\x2da7bd\x2db7f3baa922dc.swap @7.889s +14ms
                                └─blockdev@dev-mapper-luks\x2d48d04c79\x2d6793\x2d4578\x2da7bd\x2db7f3baa922dc.target @7.876s
                                  └─systemd-cryptsetup@luks\x2d48d04c79\x2d6793\x2d4578\x2da7bd\x2db7f3baa922dc.service @1.628s +6.247s
                                    └─dev-disk-by\x2duuid-48d04c79\x2d6793\x2d4578\x2da7bd\x2db7f3baa922dc.device @1.556s

edit: i just restarted my laptop and used my phone to time the startup time, it came to an total of just shy of 3 minutes and 50 seconds, roughly 20 seconds of those were spend by the system waiting for me to enter passwords

There is something I’m missing / strange here (I don’t see “long times”).
Let’s see the “normal”

systemd-analyze

It could be a matter of (boot)loader, maybe solvable reinstalling the grub and/or checking efibootmgr, or firmware (and this is the point where we can do less).

2 Likes
Startup finished in 3.112s (firmware) + 40.856s (loader) + 18.497s (kernel) + 12.465s (userspace) = 1min 14.932s
graphical.target reached after 11.110s in userspace.

still over two minutes missing in that time tho

This is definitely too much.
Maybe try reinstalling the grub.
Edit: no, sorry, not really too much with LUKS

1 Like

Just check /etc/fstab with your lsblk -f
Did you remove “hard disks” or has one been formatted?

1 Like

the point in time where i can enter the password to log into my laptop (not the luks one, the “normal” one) feels normal, the time from entering the password until i have an usable environment is what takes so long

those entries seem okay, and i don’t think i have ever connected an actual hard drisk to my laptop, i think it should have only seen m.2 ssd’s and sata ssd’s

is there anything for me to do to get it to log in at normal speed again?

Keep It Tidy

Make the effort to put things in the right place, so that we can spend more time discussing and less cleaning up. So:

  • Don’t start a topic in the wrong category.
  • Don’t cross-post the same thing in multiple topics.

* Don’t post no-content replies.

Try live ISO, also slow?
Create new user, search the WWW …

3 Likes

If you truly did nothing - no updates, and didn’t mess with any settings from one day to the next - that says to me you have some bit of hardware failing. Something is dying, something came loose, bad connection, failing drive, etc.

Computers are stupid. Their startup process will always be exactly the same unless SOMETHING changes. So if it’s not software, it must be hardware.

3 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.