Booting takes long time issue

Varen · August 14, 2024, 6:33pm

so this is the output of a boot without any USB Devices connected - at all. Just Ethernet + Screens:

Blame:

3.133s systemd-journald.service
2.518s upower.service
 799ms \x2esnapshots.mount
 758ms NetworkManager.service
 303ms systemd-modules-load.service
 274ms dev-nvme1n1p2.device
 107ms systemd-udev-trigger.service
  99ms systemd-journal-flush.service
  99ms user@1000.service
  82ms systemd-vconsole-setup.service
  67ms udisks2.service

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 @4.372s
└─sddm.service @4.372s
  └─systemd-user-sessions.service @4.366s +3ms
    └─network.target @4.366s
      └─wpa_supplicant.service @4.342s +23ms
        └─basic.target @3.561s
          └─dbus-broker.service @3.543s +17ms
            └─dbus.socket @3.540s
              └─sysinit.target @3.540s
                └─systemd-timesyncd.service @3.494s +45ms
                  └─systemd-tmpfiles-setup.service @3.431s +62ms
                    └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @3.459s

cricitcal-chain systemd-journald.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.

systemd-journald.service +3.133s
└─systemd-journald.socket @190ms
  └─-.mount @157ms
    └─-.slice @157ms

journalctl -b output:

Aug 14 20:22:40 NALX kernel: nvme nvme0: pci function 0000:02:00.0
Aug 14 20:22:40 NALX kernel: nvme nvme1: pci function 0000:05:00.0
Aug 14 20:22:40 NALX kernel: nvme nvme0: D3 entry latency set to 10 seconds
Aug 14 20:22:40 NALX kernel: nvme nvme0: 16/0/0 default/read/poll queues
Aug 14 20:22:40 NALX kernel:  nvme0n1: p1 p2 p3 p4 p5 p6
Aug 14 20:22:40 NALX kernel: nvme nvme1: 16/0/0 default/read/poll queues
Aug 14 20:22:40 NALX kernel:  nvme1n1: p1 p2
Aug 14 20:22:40 NALX kernel: xhci_hcd 0000:0a:00.0: hcc params 0x0200ef81 hci version 0x110 quirks 0x0000000200000010
Aug 14 20:22:40 NALX kernel: xhci_hcd 0000:0a:00.0: xHCI Host Controller
Aug 14 20:22:40 NALX kernel: xhci_hcd 0000:0a:00.0: new USB bus registered, assigned bus number 2
Aug 14 20:22:40 NALX kernel: xhci_hcd 0000:0a:00.0: Host supports USB 3.2 Enhanced SuperSpeed
Aug 14 20:22:43 NALX kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.10
Aug 14 20:22:43 NALX kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 14 20:22:43 NALX kernel: usb usb1: Product: xHCI Host Controller
Aug 14 20:22:43 NALX kernel: usb usb1: Manufacturer: Linux 6.10.4-1-cachyos-eevdf xhci-hcd
Aug 14 20:22:43 NALX kernel: usb usb1: SerialNumber: 0000:0a:00.0
Aug 14 20:22:43 NALX kernel: hub 1-0:1.0: USB hub found
Aug 14 20:22:43 NALX kernel: hub 1-0:1.0: 12 ports detected

dmesg:

[    6.577012] systemd-journald[417]: Received client request to flush runtime journal.
[    6.633783] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 41
[    9.652890] block nvme1n1: No UUID available providing old NGUID
[    9.752773] igc 0000:08:00.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[   12.186252] usbcore: registered new interface driver snd-usb-audio
[   12.226819] Bluetooth: Core ver 2.22
[   12.226837] NET: Registered PF_BLUETOOTH protocol family
[   12.226838] Bluetooth: HCI device and connection manager initialized
[   12.226843] Bluetooth: HCI socket layer initialized
[   12.226844] Bluetooth: L2CAP socket layer initialized
[   12.226847] Bluetooth: SCO socket layer initialized
[   12.241048] usbcore: registered new interface driver btusb
[   12.257433] Bluetooth: hci0: HW/SW Version: 0x008a008a, Build Time: 20240716163633
[   33.083896] Bluetooth: hci0: Device setup in 20354358 usecs
[   33.083902] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   33.369339] Bluetooth: hci0: AOSP extensions version v1.00
[   33.369345] Bluetooth: hci0: AOSP quality report is supported
[   58.820039] usb 5-2.4: new full-speed USB device number 3 using xhci_hcd

idk, I feel out of luck somehow… thinking about giving EOS a shot and see how (if?) it behaves differently.

BIOS is up to date as well, idk what more it could be (other than a HW failure of the USB Bus, but a bit suspicious, since its working absolutely fine once booted)…

Varen · August 14, 2024, 8:37pm

it seems solved. I started up just now, had a Kernel Update (to 6.10.5-1) rebooted and…its gone!

825ms \x2esnapshots.mount
756ms NetworkManager.service
316ms systemd-modules-load.service
256ms dev-nvme1n1p2.device
105ms user@1000.service
103ms systemd-udev-trigger.service
 89ms systemd-vconsole-setup.service
 80ms systemd-tmpfiles-setup-dev-early.service
 79ms upower.service
 69ms udisks2.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.

systemd-journald.service +64ms
└─systemd-journald.socket @183ms
  └─-.mount @165ms
    └─-.slice @165ms

and no strange timegaps in dmesg / journalctl -b

seems like t’was a kernel issue somehow

anyways:
Thank you very much for taking your time and looking into it and trying to help. Very very very much appreciated!

@ricklinux
Wanted to mark the post as solved, but I don’t seem to have the rights to edit my original post anymore? maybe you can help me out?

ricklinux · August 14, 2024, 9:01pm

Just mark your last post as the solution.

pebcak · August 14, 2024, 9:12pm

Where did you get that from?

It is not even in the Testing repo yet.

Varen · August 14, 2024, 9:18pm

it’s the cachyos (eevdf) one, they’re always ahead of the “rolling” ones … when I started using Linux, I got told to use their kernel, as it is the best in terms of (gaming) performance, so as a newb did that and was always happy with it … so yeah

pebcak · August 14, 2024, 9:21pm

I see.

It would be good then to state that when you’re asking for assistance for a system that by standard uses the kernels from the official repos. So in this case it was CachyOS’ kernel issue then not Arch/EnOS.

ricklinux · August 14, 2024, 9:22pm

I like your thinking. Most would be telling you to use lts. I like rolling or better.

Varen · August 14, 2024, 9:30pm

sincere apologies then, I stated it in the original post, that I’m using the CachyOS Kernel:

I’m not using EOS (yet? ;)) using Arch with the CachyOS Kernel (…)

Since I had the issue as well on the Standard, LTS and Zen Kernel, I didn’t feel the need to go into more detail …

pebcak · August 14, 2024, 9:34pm

I must have forgotten that. Bad memory, sorry!

Bink · August 15, 2024, 12:45am

A fair point. I think I would have come to the same conclusion

ricklinux · August 15, 2024, 1:10am

I did the same thing so don’t feel bad.

system · August 17, 2024, 1:11am

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