Slow Boot time after one month of not using my PC

Support
1

Hi everyone,

I installed Manjaro about 3 month ago and am really happy using it, however my boot times dropped heavily after I didn’t use my computer for one month.
Manjaro is installed on a M.2 PCI-E 3.0 SSD with initial boot times of around 10 seconds. Now it takes at least 2 Minutes, sometimes even longer.
I’m quite new to Linux but from what I think it’s not a problem of the OS, the problem seems to be more on the GRUB or BIOS side.
I already reset the BIOS and updated it but the issue persists.

systemd-analyze says

Startup finished in 1min 23.194s (firmware) + 1min 27.223s (loader) + 2.985s (kernel) + 5.804s (userspace) = 2min 59.207s 
graphical.target reached after 5.803s in userspace.

all the services in systemd-analyze blame are below 3s so no issue there, I guess.
My GRUB config looks like this

# GRUB boot loader configuration
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash udev.log_priority=3"

journalctl --boot --priority=3 gives me

Okt 05 11:03:53 PJM kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Okt 05 11:03:53 PJM kernel: x86/cpu: SGX disabled by BIOS.
Okt 05 11:03:53 PJM kernel: 
Okt 05 11:03:55 PJM kernel: usb usb1-port9: connect-debounce failed
Okt 05 11:03:58 PJM kernel: usb 1-9: device descriptor read/64, error -71
Okt 05 11:03:59 PJM kernel: usb 1-9: device descriptor read/64, error -71
Okt 05 11:04:00 PJM kernel: usb 1-9: device descriptor read/64, error -71
Okt 05 11:04:00 PJM kernel: usb 1-9: device descriptor read/64, error -71
Okt 05 11:04:01 PJM kernel: usb 1-9: device not accepting address 7, error -71
Okt 05 11:04:02 PJM kernel: usb 1-9: device not accepting address 8, error -71
Okt 05 11:04:02 PJM kernel: usb usb1-port9: unable to enumerate USB device
Okt 05 11:04:03 PJM kernel: usb 1-9: device descriptor read/64, error -71
Okt 05 11:04:03 PJM kernel: usb 1-9: device descriptor read/64, error -71
Okt 05 11:04:04 PJM kernel: usb 1-9: device not accepting address 11, error -71
Okt 05 11:04:06 PJM kernel: usb usb1-port9: Cannot enable. Maybe the USB cable is bad?
Okt 05 11:04:06 PJM kernel: usb usb1-port9: unable to enumerate USB device
Okt 05 11:04:06 PJM kernel: usb 1-5: 1:1: cannot get freq at ep 0x81
Okt 05 11:04:06 PJM kernel: usb 1-5: 2:1: cannot get freq at ep 0x2
Okt 05 11:04:08 PJM kernel: usb 1-5: 2:1: cannot get freq at ep 0x2
Okt 05 11:04:31 PJM pulseaudio[929]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Okt 05 11:08:15 PJM pulseaudio[929]: ALSA weckte uns auf, um neue Daten auf das Gerät zu schreiben, doch es gab nichts zum Schreiben!
Okt 05 11:08:15 PJM pulseaudio[929]: Dies ist höchstwahrscheinlich ein Fehler im ALSA-Treiber »snd_usb_audio«. Bitte melden Sie diesen Fehler den ALSA-Entwicklern.
Okt 05 11:08:15 PJM pulseaudio[929]: Wir wurden durch das POLLOUT-Set geweckt, allerdings lieferte ein anschließender snd_pcm_avail() den Wert 0 oder einen anderen Wert < min_avail.

(sorry for the German pulseaudio output)
There’s my inxi -Fza just for reference

System:
  Kernel: 6.5.5-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5-x86_64
    root=UUID=d7653467-1ce3-4b5a-9a98-8081e3a2d1c2 rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: Z170 PRO GAMING v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 3805
    date: 05/16/2018
CPU:
  Info: model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S
    gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
    model-id: 0x5E (94) stepping: 3 microcode: 0xF0
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 828 high: 1026 min/max: 800/4200 scaling:
    driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 1026
    5: 800 6: 800 7: 800 8: 800 bogomips: 64026
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: gather_data_sampling status: Vulnerable: No microcode
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: retbleed mitigation: IBRS
  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: IBRS, IBPB: conditional, STIBP: conditional,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GA104 [GeForce RTX 3060] vendor: Micro-Star MSI
    driver: nvidia v: 535.113.01 alternate: nouveau,nvidia_drm non-free: 535.xx+
    status: current (as of 2023-09) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-23 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.0 chip-ID: 10de:2487
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.87x11.85")
    s-diag: 610mm (24")
  Monitor-1: Unknown-1 mapped: DP-1 res: 1920x1080 hz: 60 dpi: 93
    size: 527x296mm (20.75x11.65") modes: 1920x1080
  API: EGL v: 1.5 hw: drv: nvidia platforms: gbm: drv: nvidia
  API: OpenGL v: 4.6.0 vendor: nvidia v: 535.113.01 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    memory: 11.72 GiB
  API: Vulkan v: 1.3.264 layers: 5 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3060 driver: nvidia v: 535.113.01
    device-ID: 10de:2487 surfaces: xcb,xlib
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:a170 class-ID: 0403
  Device-2: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228b
    class-ID: 0403
  Device-3: RODE Microphones RØDE NT-USB Mini
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-5:4 chip-ID: 19f7:0015 class-ID: 0300
    serial: <filter>
  API: ALSA v: k6.5.5-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 0.3.80 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.71 TiB used: 264.45 GiB (15.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
    model: WD Blue SN570 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 234110WD temp: 33.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 840 PRO Series
    size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 6B0Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD5000AZRX-00L4HB0 size: 465.76 GiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 1A01 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 750 EVO 250GB
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 915.53 GiB (98.32%)
    used: 264.45 GiB (28.9%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 292 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 14.9 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A gpu: nvidia temp: 43 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
  Processes: 230 Uptime: 44m wakeups: 0 Memory: total: 16 GiB
  available: 15.57 GiB used: 4.76 GiB (30.6%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: 1353 pm: pacman pkgs: 1347 libs: 456 tools: pamac pm: flatpak
  pkgs: 6 Shell: Zsh v: 5.9 default: Bash v: 5.1.16 running-in: konsole
  inxi: 3.3.30
2

Do you use bluetooth devices? Do you have a hardware switch to enable/disable bluetooth? It seems to me that the wait is caused by

GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

This line suggests that the bluetooth service tries to run but fails after a long wait. However, your network inxi shows no bluetooth hardware, only an ethernet adapter.

If you have bluetooth devices try to find the hardware switch that enables/disables bluetooth an set it to ‘on’. Check also in your bios if bluetooth is enabled, sometimes bios can lose settings on older hardware if the cmos battery that should hold these settings is weak and the machine was off power for a long time.

If you do not have any bluetooh devices and do not plan to use any disable the bluetooth service or even better open pamac GUI, search for ‘blue’ and remove all installed bluetooth packages apart from bluez-libs (it’s needed by networkmanager and pulse-audio).

3

Three months can be considered a long time; depending on the state of your CMOS battery prior to the last time the machine was started.

Add a new battery to your shopping list, anyway, in case it’s needed. CMOS batteries tend to suffer equally from non-use as they do from extended use. Cheers.

4

I indeed had a Bluetooth USB dongle plugged into my computer. Unplugging solved the issue. Thanks a lot!
I’m gonna get a new CMOS battery as well. Mine has been in since 2017 or so…

1 Like
5

It’s tricky to give an “expiry date” for them, depends on many factors like bios, manufacturer, date of manufacture etc.

A good way to keep an eye on them is to set the bios time exactly to internet time and occasionally check; if it’s off by seconds after a couple of month (and maybe some time unplugged) the cmos is ok, if it’s off by minutes or more it should be replaced.

6

Although, I’m sure there are applications that will signal a problem as soon as BIOS time is out of sync; much like an alarm clock. :slightly_smiling_face:

7

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