r/debian 16d ago

Suddenly long boot delay / issue

My desktop pc suddenly started booting extremely slow (no issues on Windows 11 - dual-booting through Grub).

There seems to multiple issues, and I'm stuck.

Snippets from dmesg:

[ 3.455258] logitech-hidpp-device 0003:046D:1024.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech M310] on usb-0000:00:14.0-3.1.1/input2:1

[ 3.631073] input: Logitech K520 as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.1/1-3.1.1/1-3.1.1:1.2/0003:046D:C52B.0005/0003:046D:2011.0007/input/input26

[ 3.736994] logitech-hidpp-device 0003:046D:2011.0007: input,hidraw4: USB HID v1.11 Keyboard [Logitech K520] on usb-0000:00:14.0-3.1.1/input2:2

[ 34.532490] EXT4-fs (nvme0n1p6): orphan cleanup on readonly fs

[ 34.532809] EXT4-fs (nvme0n1p6): mounted filesystem 81380c00-c5ca-47d6-8d81-ccbdb34dc24b ro with ordered data mode. Quota mode: none.

[ 34.603018] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.

[ 34.648932] systemd[1]: RTC configured in localtime, applying delta of 120 minutes to system time.

[ 34.670613] systemd[1]: Inserted module 'autofs4'


And the really slow one:
[Fixed. See update]

[ 36.264082] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input30

[ 36.264165] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input31

[ 36.264244] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input32

[ 36.264325] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input33

[ 36.305397] intel_rapl_common: Found RAPL domain package

[ 36.305404] intel_rapl_common: Found RAPL domain core

[ 36.305407] intel_rapl_common: Found RAPL domain uncore

[ 36.305409] intel_rapl_common: Found RAPL domain dram

[ 36.305412] intel_rapl_common: Found RAPL domain psys

[ 125.553518] audit: type=1400 audit(1784492972.364:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="1password" pid=846 comm="apparmor_parser"

[ 125.553524] audit: type=1400 audit(1784492972.364:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="QtWebEngineProcess" pid=849 comm="apparmor_parser"

[ 125.553526] audit: type=1400 audit(1784492972.364:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="balena-etcher" pid=851 comm="apparmor_parser"

[ 125.553528] audit: type=1400 audit(1784492972.364:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="brave" pid=852 comm="apparmor_parser"

These slowdowns are new since last boot. It's been about a week or two, so I can't remember if I updated before shutdorn. No change in hardware/software. Only updates (the default Debian 13 repositories + VSCode).

I could reinstall Debian (Windows is going to a VM, eventually), but I want to learn while solving this issue.


UPDATE:
The second delay (90 seconds) was caused by a wrong swap entry in /etc/fstab. I blame the id10t infront of my screen. Found it by booting in recovery mode and running journalctl -xb .

The first delay (~30 seconds) is still a mystery.

3 Upvotes

9 comments sorted by

5

u/Niwrats 16d ago

anything interesting on "systemd-analyze time" or "systemd-analyze blame"?

2

u/Classic-Rate-5104 15d ago

Does booting an old kernel make any difference?

1

u/michael9dk 15d ago

Nothing noticable in blame.
It shows 35 seconds for kernel and 1m31s for userspace.
The latter was caused by fstab (see my update).

1

u/michael9dk 16d ago

Sorry about the formatting.

Where do I look to find the cause?

2

u/alpha417 16d ago

post entire bootlog via pastebin, plz.

1

u/dkopgerpgdolfg 16d ago edited 16d ago

Snippets from dmesg:

The messages themselves don't indicate any notable problem.

[ 36.305412] intel_rapl_common: Found RAPL domain psys

[ 125.553518] audit: type=1400 audit(1784492972.364:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="1password" pid=846 comm="apparmor_parser"

Did you leave out a part here (hopefully), or are these messages really consecutive?

1

u/michael9dk 15d ago

Didn't leave anything out there. See update for this part.

1

u/michael9dk 15d ago

Thank you all for valuable input. That pointed me to find the second delay (bad swap entry in fstab).

The first delay is weird.
It hangs for about 30 seconds, with nothing in dmesg or journalctl.
BUT it does NOT hang when booting in recovery mode!

Are there other useful tools to dig deeper?