Long boot (~70 seconds) on new Ubuntu install

Support and Help
,
1

Hi there!

Ubuntu Version: 24.04.3

Desktop Environment (if applicable): Default?

Problem Description:

I’ve just installed a brand new install of Ubuntu Desktop. I’ve just noticed that the boot time is surprisingly slow - roughly 70 seconds. I’ve rebooted a few times and found the wait time to be pretty consistent.

I’d normally expect the system to boot in around maybe 15 to 20 seconds, something like that.

Suspecting some sort of wait timeout, I had a look at dmesg, and there are some pretty likely looking culprits, but I don’t understand much about what dmesg is telling me here.

Relevant System Information:
Dual boot with Windows 11. W11 is on an NVMe M.2, and Ubuntu is on a SATA SSD. The SATA SSD is the primary boot device, and hands off to W11 to boot if you choose that option - this was set up automatically by the Ubuntu installer - I haven’t messed with it at all.

It’s a new system build.

The motherboard is an ASUS PRIME Z890-P WIFI.

There is also a USB connection to one of my Dell U2419HC monitors, which acts as a hub, which is where I have the dongle for the keyboard and mouse plugged in, and a Logitech HD Pro Webcam C920.

Screenshots or Error Messages:
Here’s an excerpt from dmesg - I hope I haven’t omitted anything else relevant. I can provide more from before/after this excerpt if necessary.

[    0.853853] usb 3-2: new full-speed USB device number 2 using xhci_hcd
[    0.982261] usb 3-2: config 1 has an invalid interface number: 2 but max is 1
[    0.982272] usb 3-2: config 1 has no interface number 1
[    0.983527] usb 3-2: New USB device found, idVendor=0b05, idProduct=19af, bcdDevice= 1.00
[    0.983540] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    0.983545] usb 3-2: Product: AURA LED Controller
[    0.983549] usb 3-2: Manufacturer: AsusTek Computer Inc.
[    0.983552] usb 3-2: SerialNumber: 9876543210
[    1.089861] usb 4-6: new SuperSpeed USB device number 2 using xhci_hcd
[    1.098939] ata6: SATA link down (SStatus 4 SControl 300)
[    1.100275] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.100489] ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.100551] ata7: SATA link down (SStatus 4 SControl 300)
[    1.101199] usb 4-6: New USB device found, idVendor=0451, idProduct=8440, bcdDevice= 1.00
[    1.101213] usb 4-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.102048] ata5.00: Model 'Samsung SSD 850 EVO 250GB', rev 'EMT01B6Q', applying quirks: noncqtrim zeroaftertrim
[    1.102404] ata5.00: supports DRM functions and may not be fully accessible
[    1.102413] ata5.00: ATA-9: Samsung SSD 850 EVO 250GB, EMT01B6Q, max UDMA/133
[    1.102932] hub 4-6:1.0: USB hub found
[    1.103057] ata5.00: NCQ Send/Recv Log not supported
[    1.103068] ata5.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    1.103991] hub 4-6:1.0: 4 ports detected
[    1.105091] ata5.00: Features: Trust Dev-Sleep
[    1.105640] ata5.00: supports DRM functions and may not be fully accessible
[    1.106020] ata5.00: NCQ Send/Recv Log not supported
[    1.107358] ata5.00: configured for UDMA/133
[    1.107377] ahci 0000:80:17.0: port does not support device sleep
[    1.107799] scsi 4:0:0:0: Direct-Access     ATA      Samsung SSD 850  1B6Q PQ: 0 ANSI: 5
[    1.108348] sd 4:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB)
[    1.108358] sd 4:0:0:0: [sda] Write Protect is off
[    1.108362] sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.108373] sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.108402] sd 4:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[    1.108471] sd 4:0:0:0: Attached scsi generic sg0 type 0
[    1.113253] ata8.00: ATAPI: SONY    DVD RW DRU-190S, 1.62, max UDMA/100
[    1.121621]  sda: sda1 sda2
[    1.122264] sd 4:0:0:0: [sda] supports TCG Opal
[    1.122270] sd 4:0:0:0: [sda] Attached SCSI disk
[    1.126647] ata8.00: configured for UDMA/100
[    1.130285] scsi 7:0:0:0: CD-ROM            SONY     DVD RW DRU-190S  1.62 PQ: 0 ANSI: 5
[    1.159949] sr 7:0:0:0: [sr0] scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.159960] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.173987] sr 7:0:0:0: Attached scsi CD-ROM sr0
[    1.174192] sr 7:0:0:0: Attached scsi generic sg1 type 5
[    1.212726] usb 3-4: new high-speed USB device number 3 using xhci_hcd
[    1.338539] usb 3-4: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.70
[    1.338552] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.338557] usb 3-4: Product: USB2.0 Hub
[    1.340053] hub 3-4:1.0: USB hub found
[    1.340359] hub 3-4:1.0: 4 ports detected
[    1.453824] usb 3-6: new high-speed USB device number 4 using xhci_hcd
[    1.577462] usb 3-6: New USB device found, idVendor=0451, idProduct=8442, bcdDevice= 1.00
[    1.577479] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[    1.577485] usb 3-6: SerialNumber: 1D00086127A2
[    1.578964] hub 3-6:1.0: USB hub found
[    1.579011] hub 3-6:1.0: 6 ports detected
[    1.691794] usb 3-11: new high-speed USB device number 5 using xhci_hcd
[    1.816583] usb 3-11: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.70
[    1.816613] usb 3-11: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.816618] usb 3-11: Product: USB2.0 Hub
[    1.818337] hub 3-11:1.0: USB hub found
[    1.818719] hub 3-11:1.0: 4 ports detected
[    1.877816] usb 3-6.3: new full-speed USB device number 6 using xhci_hcd
[    1.967498] usb 3-6.3: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.11
[    1.967517] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.967523] usb 3-6.3: Product: USB Receiver
[    1.967527] usb 3-6.3: Manufacturer: Logitech
[    2.076223] usb 3-14: new high-speed USB device number 7 using xhci_hcd
[    7.342469] usb 3-14: device descriptor read/64, error -110
[   23.214449] usb 3-14: device descriptor read/64, error -110
[   23.696197] usb 3-14: new high-speed USB device number 8 using xhci_hcd
[   28.846446] usb 3-14: device descriptor read/64, error -110
[   44.718457] usb 3-14: device descriptor read/64, error -110
[   44.821450] usb usb3-port14: attempt power cycle
[   44.896195] usb 3-6.4: new high-speed USB device number 9 using xhci_hcd
[   45.288238] usb 3-14: new high-speed USB device number 10 using xhci_hcd
[   45.545039] usb 3-6.4: New USB device found, idVendor=046d, idProduct=0892, bcdDevice= 0.19
[   45.545059] usb 3-6.4: New USB device strings: Mfr=0, Product=2, SerialNumber=1
[   45.545065] usb 3-6.4: Product: HD Pro Webcam C920
[   45.545069] usb 3-6.4: SerialNumber: 1EB96FDF
[   50.749479] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   56.381490] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   56.589286] usb 3-14: device not accepting address 10, error -62
[   56.968234] usb 3-14: new high-speed USB device number 11 using xhci_hcd
[   62.013370] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   67.645500] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   67.853386] usb 3-14: device not accepting address 11, error -62
[   67.853641] usb usb3-port14: unable to enumerate USB device
[   67.888689] hid: raw HID events driver (C) Jiri Kosina
[   67.897281] usbcore: registered new interface driver usbhid
[   67.897283] usbhid: USB HID core driver
[   67.900359] hid-generic 0003:0B05:19AF.0001: hiddev0,hidraw0: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:80:14.0-2/input2
[   67.900431] input: Logitech USB Receiver as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.0/0003:046D:C52B.0002/input/input3
[   67.926675] usb 3-6.5: new high-speed USB device number 12 using xhci_hcd
[   67.950954] hid-generic 0003:046D:C52B.0002: input,hidraw1: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:80:14.0-6.3/input0
[   67.951442] input: Logitech USB Receiver Mouse as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.1/0003:046D:C52B.0003/input/input4
[   67.951728] input: Logitech USB Receiver Consumer Control as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.1/0003:046D:C52B.0003/input/input5
[   68.002851] input: Logitech USB Receiver System Control as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.1/0003:046D:C52B.0003/input/input6
[   68.003014] hid-generic 0003:046D:C52B.0003: input,hiddev1,hidraw2: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:80:14.0-6.3/input1
[   68.003317] hid-generic 0003:046D:C52B.0004: hiddev2,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:80:14.0-6.3/input2
[   68.011589] usb 3-6.5: New USB device found, idVendor=0451, idProduct=82ff, bcdDevice= 1.00
[   68.011618] usb 3-6.5: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[   68.011624] usb 3-6.5: SerialNumber: 1D00086127A2
[   68.016366] hid-generic 0003:0451:82FF.0005: hiddev3,hidraw4: USB HID v1.11 Device [HID 0451:82ff] on usb-0000:80:14.0-6.5/input0
[   68.078794] usb 3-6.6: new high-speed USB device number 13 using xhci_hcd
[   68.165293] usb 3-6.6: New USB device found, idVendor=0451, idProduct=82ee, bcdDevice= 1.00
[   68.165312] usb 3-6.6: New USB device strings: Mfr=0, Product=0, SerialNumber=3
[   68.165318] usb 3-6.6: SerialNumber: 1D00086127A2
[   68.268041] logitech-djreceiver 0003:046D:C52B.0004: hiddev1,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:80:14.0-6.3/input2
[   68.373951] input: Logitech Wireless Device PID:405e Keyboard as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.2/0003:046D:C52B.0004/0003:046D:405E.0006/input/input8
[   68.375715] input: Logitech Wireless Device PID:405e Mouse as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.2/0003:046D:C52B.0004/0003:046D:405E.0006/input/input9
[   68.375832] hid-generic 0003:046D:405E.0006: input,hidraw2: USB HID v1.11 Keyboard [Logitech Wireless Device PID:405e] on usb-0000:80:14.0-6.3/input2:1
[   68.376106] input: Logitech Wireless Device PID:4088 Keyboard as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.2/0003:046D:C52B.0004/0003:046D:4088.0007/input/input13
[   68.376158] input: Logitech Wireless Device PID:4088 Mouse as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.2/0003:046D:C52B.0004/0003:046D:4088.0007/input/input14
[   68.376248] hid-generic 0003:046D:4088.0007: input,hidraw3: USB HID v1.11 Keyboard [Logitech Wireless Device PID:4088] on usb-0000:80:14.0-6.3/input2:2
[   68.429468] input: Logitech M720 Triathlon as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.2/0003:046D:C52B.0004/0003:046D:405E.0006/input/input18
[   68.429674] logitech-hidpp-device 0003:046D:405E.0006: input,hidraw2: USB HID v1.11 Keyboard [Logitech M720 Triathlon] on usb-0000:80:14.0-6.3/input2:1
[   68.477354] input: Logitech ERGO K860 as /devices/pci0000:80/0000:80:14.0/usb3/3-6/3-6.3/3-6.3:1.2/0003:046D:C52B.0004/0003:046D:4088.0007/input/input19
[   68.477523] logitech-hidpp-device 0003:046D:4088.0007: input,hidraw3: USB HID v1.11 Keyboard [Logitech ERGO K860] on usb-0000:80:14.0-6.3/input2:2

What I’ve Tried:
I wondered if this was to do with my wireless keyboard/mouse not responding or something, so tried booting without the USB dongle inserted, but it didn’t help.

I am also wondering if this is to do with USB headers on the motherboard which Ubuntu typically expects to have things attached to, but that don’t have anything attached :thinking:

2

Put here the output from: systemd-analyze time and systemd-analyze critical-chain --no-pager

1 Like
3

Hello ghostal,
I would also try to boot without everything USB connected (hub, dongle, webcam) and when the systems boots fast, try to replug them one by one and reboot between each.
Hope this helps

4

This is crazy, thanks for sharing!

5

In addition to what corradoventu requested, please also post output of

systemd-analyze blame --no-pager
6

Thanks for the responses so far.

@corradoventu see below:

alex@alex-studio-linux:~$ systemd-analyze time
Startup finished in 35.752s (firmware) + 13.397s (loader) + 1min 8.173s (kernel) + 16.111s (userspace) = 2min 13.433s 
graphical.target reached after 16.106s in userspace.
alex@alex-studio-linux:~$ systemd-analyze critical-chain --no-pager
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 @16.106s
└─multi-user.target @16.106s
  └─kerneloops.service @16.096s +9ms
    └─network-online.target @16.094s
      └─NetworkManager-wait-online.service @4.084s +12.010s
        └─NetworkManager.service @2.244s +1.817s
          └─dbus.service @2.110s +115ms
            └─basic.target @2.109s
              └─sockets.target @2.109s
                └─snapd.socket @2.094s +14ms
                  └─sysinit.target @2.093s
                    └─snapd.apparmor.service @2.058s +34ms
                      └─apparmor.service @2.001s +45ms
                        └─local-fs.target @2.000s
                          └─run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount @5.122s
                            └─run-snapd-ns.mount @4.122s
                              └─local-fs-pre.target @216ms
                                └─keyboard-setup.service @188ms +28ms
                                  └─systemd-journald.socket @185ms
                                    └─-.mount @168ms
                                      └─-.slice @168ms

@halogen2 see below:

alex@alex-studio-linux:~$ systemd-analyze blame --no-pager
12.010s NetworkManager-wait-online.service
 4.080s apt-daily.service
 2.429s plymouth-quit-wait.service
 2.305s fwupd.service
 1.817s NetworkManager.service
  809ms ua-timer.service
  803ms boot-efi.mount
  756ms apt-daily-upgrade.service
  590ms thermald.service
  521ms snapd.seeded.service
  370ms snapd.service
  321ms e2scrub_reap.service
  301ms apport.service
  246ms udisks2.service
  178ms dev-sda2.device
  172ms gnome-remote-desktop.service
  163ms accounts-daemon.service
  159ms snap-core22-2133.mount
  135ms power-profiles-daemon.service
  134ms avahi-daemon.service
  133ms polkit.service
  120ms switcheroo-control.service
  115ms dbus.service
  104ms dev-loop4.device
  102ms user@1000.service
   92ms dev-loop6.device
   92ms ModemManager.service
   89ms dev-loop5.device
   89ms dev-loop0.device
   87ms rsyslog.service
   86ms dev-loop8.device
   86ms dev-loop1.device
   85ms dev-loop3.device
   85ms dev-loop7.device
   75ms systemd-udev-trigger.service
   72ms dev-loop2.device
   70ms systemd-udevd.service
   69ms gpu-manager.service
   69ms dev-loop9.device
   69ms dev-loop10.device
   62ms update-notifier-download.service
   62ms systemd-resolved.service
   48ms gdm.service
   46ms grub-common.service
   45ms systemd-journal-flush.service
   45ms plymouth-start.service
   45ms apparmor.service
   40ms secureboot-db.service
   38ms systemd-journald.service
   38ms upower.service
   38ms systemd-logind.service
   35ms systemd-modules-load.service
   34ms fwupd-refresh.service
   34ms snapd.apparmor.service
   33ms systemd-timesyncd.service
   31ms sysstat.service
   30ms wpa_supplicant.service
   29ms systemd-tmpfiles-clean.service
   28ms keyboard-setup.service
   27ms cups.service
   22ms grub-initrd-fallback.service
   21ms colord.service
   19ms systemd-oomd.service
   19ms bolt.service
   18ms systemd-tmpfiles-setup.service
   18ms systemd-fsck@dev-disk-by\x2duuid-859A\x2dC052.service
   17ms systemd-sysctl.service
   15ms systemd-remount-fs.service
   14ms snapd.socket
   13ms dev-loop11.device
   13ms systemd-tmpfiles-setup-dev-early.service
   12ms plymouth-read-write.service
   11ms systemd-binfmt.service
   10ms snap-bare-5.mount
   10ms snap-canonical\x2dlivepatch-364.mount
   10ms snap-core22-2045.mount
    9ms snap-firefox-6565.mount
    9ms snap-firmware\x2dupdater-167.mount
    9ms kerneloops.service
    8ms snap-gnome\x2d42\x2d2204-202.mount
    8ms systemd-rfkill.service
    7ms sysstat-collect.service
    7ms rtkit-daemon.service
    7ms snap-gtk\x2dcommon\x2dthemes-1535.mount
    6ms proc-sys-fs-binfmt_misc.mount
    6ms systemd-random-seed.service
    6ms user-runtime-dir@1000.service
    6ms alsa-restore.service
    6ms dev-hugepages.mount
    6ms dev-mqueue.mount
    6ms sys-kernel-debug.mount
    6ms snap-snap\x2dstore-1270.mount
    5ms sys-kernel-tracing.mount
    5ms systemd-update-utmp.service
    5ms systemd-user-sessions.service
    5ms snap-snapd-24792.mount
    4ms openvpn.service
    4ms snap-snapd-25202.mount
    4ms systemd-tmpfiles-setup-dev.service
    4ms snap-snapd\x2ddesktop\x2dintegration-315.mount
    4ms systemd-update-utmp-runlevel.service
    4ms kmod-static-nodes.service
    4ms console-setup.service
    3ms modprobe@configfs.service
    3ms swap.img.swap
    3ms modprobe@drm.service
    3ms modprobe@fuse.service
    2ms modprobe@dm_mod.service
    2ms ufw.service
    2ms modprobe@loop.service
    2ms modprobe@efi_pstore.service
    2ms sys-fs-fuse-connections.mount
    2ms sys-kernel-config.mount
    1ms motd-news.service
    1ms setvtrgb.service
alex@alex-studio-linux:~$

I’ll try unplugging all USB connections now and report my findings.

7

I unplugged the monitor USB hub connection, so this time there were no USB connections on the motherboard IO panel, and no USB headers in use on the board itself (including case front panel connections, etc), while booting up.

Same behaviour observed - roughly 70 seconds to boot.

  • systemd-analyze time:

    Startup finished in 33.968s (firmware) + 13.388s (loader) + 1min 7.022s (kernel) + 11.179s (userspace) = 2min 5.559s 
graphical.target reached after 11.174s in userspace.

  • systemd-analyze critical-chain --no-pager

    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 @11.174s
└─multi-user.target @11.174s
  └─kerneloops.service @11.165s +9ms
    └─network-online.target @11.153s
      └─NetworkManager-wait-online.service @4.121s +7.031s
        └─NetworkManager.service @2.295s +1.810s
          └─dbus.service @2.170s +116ms
            └─basic.target @2.168s
              └─sockets.target @2.168s
                └─snapd.socket @2.145s +23ms
                  └─sysinit.target @2.143s
                    └─systemd-resolved.service @2.080s +62ms
                      └─systemd-tmpfiles-setup.service @2.043s +22ms
                        └─local-fs.target @2.040s
                          └─run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount @5.161s
                            └─run-snapd-ns.mount @4.157s
                              └─local-fs-pre.target @230ms
                                └─systemd-tmpfiles-setup-dev.service @225ms +4ms
                                  └─systemd-tmpfiles-setup-dev-early.service @195ms +12ms
                                    └─kmod-static-nodes.service @189ms +4ms
                                      └─systemd-journald.socket @185ms
                                        └─system.slice @166ms
                                          └─-.slice @166ms

  • systemd-analyze blame --no-pager

    7.031s NetworkManager-wait-online.service
3.418s plymouth-quit-wait.service
1.810s NetworkManager.service
 842ms boot-efi.mount
 543ms thermald.service
 493ms snapd.seeded.service
 364ms snapd.service
 316ms e2scrub_reap.service
 299ms apport.service
 263ms udisks2.service
 207ms dev-sda2.device
 170ms gnome-remote-desktop.service
 165ms accounts-daemon.service
 130ms power-profiles-daemon.service
 128ms polkit.service
 126ms avahi-daemon.service
 117ms dev-loop6.device
 117ms dev-loop4.device
 116ms dbus.service
 109ms switcheroo-control.service
 100ms user@1000.service
  98ms dev-loop5.device
  95ms dev-loop7.device
  94ms dev-loop2.device
  91ms ModemManager.service
  88ms dev-loop1.device
  86ms dev-loop10.device
  86ms dev-loop0.device
  86ms rsyslog.service
  77ms systemd-udev-trigger.service
  73ms dev-loop3.device
  70ms dev-loop9.device
  69ms dev-loop8.device
  68ms dev-loop11.device
  65ms gpu-manager.service
  65ms systemd-journal-flush.service
  63ms systemd-udevd.service
  62ms systemd-resolved.service
  57ms plymouth-start.service
  47ms grub-common.service
  46ms gdm.service
  45ms apparmor.service
  38ms secureboot-db.service
  37ms systemd-logind.service
  36ms snapd.apparmor.service
  36ms systemd-journald.service
  35ms upower.service
  35ms keyboard-setup.service
  34ms wpa_supplicant.service
  33ms packagekit.service
  32ms systemd-modules-load.service
  32ms sysstat.service
  31ms cups.service
  23ms snapd.socket
  22ms systemd-tmpfiles-setup.service
  22ms bolt.service
  21ms systemd-oomd.service
  21ms systemd-timesyncd.service
  20ms colord.service
  20ms systemd-random-seed.service
  20ms grub-initrd-fallback.service
  19ms systemd-sysctl.service
  19ms systemd-remount-fs.service
  19ms systemd-fsck@dev-disk-by\x2duuid-859A\x2dC052.service
  13ms systemd-binfmt.service
  13ms snap-bare-5.mount
  13ms plymouth-read-write.service
  13ms snap-canonical\x2dlivepatch-364.mount
  12ms snap-core22-2045.mount
  12ms systemd-tmpfiles-setup-dev-early.service
  12ms snap-core22-2133.mount
  12ms snap-firefox-6565.mount
  11ms snap-firmware\x2dupdater-167.mount
  10ms snap-gnome\x2d42\x2d2204-202.mount
   9ms kerneloops.service
   8ms snap-snap\x2dstore-1270.mount
   8ms snap-gtk\x2dcommon\x2dthemes-1535.mount
   8ms snap-snapd-25202.mount
   8ms snap-snapd-24792.mount
   7ms proc-sys-fs-binfmt_misc.mount
   7ms alsa-restore.service
   7ms dev-hugepages.mount
   7ms user-runtime-dir@1000.service
   6ms rtkit-daemon.service
   6ms dev-mqueue.mount
   6ms sys-kernel-debug.mount
   6ms sys-kernel-tracing.mount
   6ms snap-snapd\x2ddesktop\x2dintegration-315.mount
   5ms systemd-user-sessions.service
   4ms systemd-tmpfiles-setup-dev.service
   4ms systemd-rfkill.service
   4ms systemd-update-utmp.service
   4ms systemd-update-utmp-runlevel.service
   4ms openvpn.service
   4ms kmod-static-nodes.service
   3ms modprobe@configfs.service
   3ms modprobe@drm.service
   3ms ufw.service
   3ms console-setup.service
   3ms modprobe@fuse.service
   2ms sys-fs-fuse-connections.mount
   2ms modprobe@dm_mod.service
   2ms modprobe@loop.service
   2ms modprobe@efi_pstore.service
   2ms swap.img.swap
   2ms sys-kernel-config.mount
   1ms setvtrgb.service

  • Relevant-looking part of dmesg

    [    1.109545] sd 4:0:0:0: [sda] Attached SCSI disk
[    1.112313] ata8.00: configured for UDMA/100
[    1.116613] scsi 7:0:0:0: CD-ROM            SONY     DVD RW DRU-190S  1.62 PQ: 0 ANSI: 5
[    1.155462] sr 7:0:0:0: [sr0] scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.155474] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.170380] sr 7:0:0:0: Attached scsi CD-ROM sr0
[    1.170754] sr 7:0:0:0: Attached scsi generic sg1 type 5
[    1.175186] r8169 0000:84:00.0 enp132s0: renamed from eth0
[    1.214827] usb 3-4: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.70
[    1.214840] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.214845] usb 3-4: Product: USB2.0 Hub
[    1.216394] hub 3-4:1.0: USB hub found
[    1.216714] hub 3-4:1.0: 4 ports detected
[    1.330767] usb 3-11: new high-speed USB device number 4 using xhci_hcd
[    1.455633] usb 3-11: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.70
[    1.455646] usb 3-11: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.455651] usb 3-11: Product: USB2.0 Hub
[    1.457161] hub 3-11:1.0: USB hub found
[    1.457459] hub 3-11:1.0: 4 ports detected
[    1.572682] usb 3-14: new high-speed USB device number 5 using xhci_hcd
[    6.831648] usb 3-14: device descriptor read/64, error -110
[   22.703481] usb 3-14: device descriptor read/64, error -110
[   23.186171] usb 3-14: new high-speed USB device number 6 using xhci_hcd
[   28.335431] usb 3-14: device descriptor read/64, error -110
[   44.207519] usb 3-14: device descriptor read/64, error -110
[   44.311371] usb usb3-port14: attempt power cycle
[   44.690175] usb 3-14: new high-speed USB device number 7 using xhci_hcd
[   49.727590] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   55.359469] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   55.567320] usb 3-14: device not accepting address 7, error -62
[   55.946155] usb 3-14: new high-speed USB device number 8 using xhci_hcd
[   60.991500] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   66.623477] xhci_hcd 0000:80:14.0: Timeout while waiting for setup device command
[   66.831234] usb 3-14: device not accepting address 8, error -62
[   66.831461] usb usb3-port14: unable to enumerate USB device
[   66.866803] hid: raw HID events driver (C) Jiri Kosina
[   66.871629] usbcore: registered new interface driver usbhid
[   66.871631] usbhid: USB HID core driver
[   66.875525] hid-generic 0003:0B05:19AF.0001: hiddev0,hidraw0: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:80:14.0-2/input2
[   66.959627] EXT4-fs (sda2): mounted filesystem 4f42c65b-ecfe-4198-bd6f-1cf401265788 ro with ordered data mode. Quota mode: none.
[   67.045845] systemd[1]: Inserted module 'autofs4'
[   67.076004] systemd[1]: systemd 255.4-1ubuntu8.11 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[   67.076011] systemd[1]: Detected architecture x86-64.
[   67.077231] systemd[1]: Hostname set to <alex-studio-linux>.
8

You have 33.968s (firmware) + 13.388s (loader) + 1min 7.022s (kernel)
which doesn’t appear in systemd-analyze and may be hardware dependent, then Ubuntu only takes 11-16 seconds.
For that first part I have no idea what to recommend.

9

An update and a conclusion (to some extent):

I plugged in all the front panel internal connectors and booted the system, and this time, it booted in around 15 seconds.

For the sake of curiosity, I unplugged the three connections I had just made, and rebooted again (as before) and interestingly, the system again booted in ~15 seconds. I’ve rebooted a few times now, and the problem appears to have gone away:

  • systemd-analyze time

    Startup finished in 11.267s (firmware) + 4.811s (loader) + 2.499s (kernel) + 15.836s (userspace) = 34.414s 
graphical.target reached after 15.831s in userspace.

  • systemd-analyze critical-chain --no-pager

    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 @15.831s
└─multi-user.target @15.831s
  └─kerneloops.service @15.820s +10ms
    └─network-online.target @15.818s
      └─NetworkManager-wait-online.service @4.074s +11.743s
        └─NetworkManager.service @2.284s +1.778s
          └─dbus.service @2.144s +122ms
            └─basic.target @2.142s
              └─sockets.target @2.142s
                └─snapd.socket @2.130s +11ms
                  └─sysinit.target @2.129s
                    └─systemd-resolved.service @2.065s +63ms
                      └─systemd-tmpfiles-setup.service @2.044s +18ms
                        └─local-fs.target @2.041s
                          └─run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount @5.120s
                            └─run-snapd-ns.mount @4.108s
                              └─local-fs-pre.target @224ms
                                └─keyboard-setup.service @197ms +26ms
                                  └─systemd-journald.socket @194ms
                                    └─-.mount @172ms
                                      └─-.slice @173ms

  • systemd-analyze blame --no-pager

    11.743s NetworkManager-wait-online.service
 3.041s plymouth-quit-wait.service
 1.778s NetworkManager.service
  834ms boot-efi.mount
  537ms thermald.service
  534ms snapd.seeded.service
  499ms snapd.service
  331ms e2scrub_reap.service
  304ms apport.service
  234ms udisks2.service
  191ms dev-sda2.device
  173ms gnome-remote-desktop.service
  173ms accounts-daemon.service
  142ms power-profiles-daemon.service
  142ms polkit.service
  141ms avahi-daemon.service
  141ms bluetooth.service
  126ms switcheroo-control.service
  124ms dev-loop6.device
  122ms dev-loop7.device
  122ms dbus.service
  118ms systemd-journal-flush.service
   95ms user@1000.service
   93ms ModemManager.service
   92ms dev-loop3.device
   89ms rsyslog.service
   86ms dev-loop2.device
   84ms dev-loop4.device
   80ms dev-loop5.device
   79ms dev-loop1.device
   78ms systemd-udev-trigger.service
   72ms plymouth-start.service
   66ms gpu-manager.service
   65ms dev-loop0.device
   64ms dev-loop8.device
   63ms dev-loop11.device
   63ms dev-loop9.device
   63ms systemd-resolved.service
   62ms dev-loop10.device
   60ms update-notifier-download.service
   58ms grub-common.service
   50ms systemd-udevd.service
   48ms secureboot-db.service
   45ms sysstat.service
   44ms systemd-logind.service
   43ms apparmor.service
   41ms systemd-journald.service
   40ms snapd.apparmor.service
   39ms gdm.service
   38ms systemd-modules-load.service
   32ms upower.service
   27ms cups.service
   26ms keyboard-setup.service
   26ms wpa_supplicant.service
   24ms systemd-oomd.service
   23ms colord.service
   23ms systemd-timesyncd.service
   19ms systemd-random-seed.service
   18ms systemd-fsck@dev-disk-by\x2duuid-859A\x2dC052.service
   18ms systemd-tmpfiles-setup.service
   17ms systemd-sysctl.service
   17ms grub-initrd-fallback.service
   16ms systemd-remount-fs.service
   16ms bolt.service
   13ms snap-bare-5.mount
   12ms snap-canonical\x2dlivepatch-364.mount
   12ms plymouth-read-write.service
   12ms systemd-tmpfiles-setup-dev-early.service
   12ms snap-core22-2045.mount
   11ms snap-core22-2133.mount
   11ms snapd.socket
   11ms snap-firefox-6565.mount
   11ms systemd-binfmt.service
   10ms snap-firmware\x2dupdater-167.mount
   10ms kerneloops.service
    9ms snap-gnome\x2d42\x2d2204-202.mount
    8ms snap-gtk\x2dcommon\x2dthemes-1535.mount
    7ms snap-snap\x2dstore-1270.mount
    7ms rtkit-daemon.service
    7ms user-runtime-dir@1000.service
    6ms dev-hugepages.mount
    6ms alsa-restore.service
    6ms dev-mqueue.mount
    6ms proc-sys-fs-binfmt_misc.mount
    6ms snap-snapd-24792.mount
    6ms sys-kernel-debug.mount
    5ms sys-kernel-tracing.mount
    5ms snap-snapd-25202.mount
    5ms systemd-update-utmp.service
    4ms snap-snapd\x2ddesktop\x2dintegration-315.mount
    4ms systemd-tmpfiles-setup-dev.service
    4ms kmod-static-nodes.service
    4ms systemd-update-utmp-runlevel.service
    4ms modprobe@configfs.service
    4ms systemd-user-sessions.service
    3ms swap.img.swap
    3ms openvpn.service
    3ms modprobe@drm.service
    3ms ufw.service
    3ms console-setup.service
    3ms modprobe@dm_mod.service
    3ms modprobe@efi_pstore.service
    3ms systemd-rfkill.service
    3ms modprobe@fuse.service
    3ms modprobe@loop.service
    2ms sys-fs-fuse-connections.mount
    2ms sys-kernel-config.mount
    1ms setvtrgb.service

  • USB messages in dmesg:

    [    0.864732] usb 3-2: new full-speed USB device number 2 using xhci_hcd
[    0.992665] usb 3-2: config 1 has an invalid interface number: 2 but max is 1
[    0.992678] usb 3-2: config 1 has no interface number 1
[    0.993856] usb 3-2: New USB device found, idVendor=0b05, idProduct=19af, bcdDevice= 1.00
[    0.993873] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    0.993879] usb 3-2: Product: AURA LED Controller
[    0.993883] usb 3-2: Manufacturer: AsusTek Computer Inc.
[    0.993886] usb 3-2: SerialNumber: 9876543210

...

[    1.107726] usb 3-4: new high-speed USB device number 3 using xhci_hcd

...

[    1.232853] usb 3-4: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.70
[    1.232866] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.232871] usb 3-4: Product: USB2.0 Hub
[    1.234356] hub 3-4:1.0: USB hub found
[    1.234656] hub 3-4:1.0: 4 ports detected
[    1.348727] usb 3-11: new high-speed USB device number 4 using xhci_hcd
[    1.473768] usb 3-11: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=60.70
[    1.473782] usb 3-11: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.473787] usb 3-11: Product: USB2.0 Hub
[    1.475376] hub 3-11:1.0: USB hub found
[    1.475675] hub 3-11:1.0: 4 ports detected
[    1.535794] usb 3-4.3: new full-speed USB device number 5 using xhci_hcd
[    1.614609] usb 3-4.3: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.11
[    1.614623] usb 3-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.614629] usb 3-4.3: Product: USB Receiver
[    1.614634] usb 3-4.3: Manufacturer: Logitech
[    1.724360] usb 3-14: new high-speed USB device number 6 using xhci_hcd
[    1.852580] usb 3-14: New USB device found, idVendor=13d3, idProduct=3602, bcdDevice= 1.00
[    1.852596] usb 3-14: New USB device strings: Mfr=5, Product=6, SerialNumber=7
[    1.852600] usb 3-14: Product: Wireless_Device
[    1.852621] usb 3-14: Manufacturer: MediaTek Inc.
[    1.852625] usb 3-14: SerialNumber: 000000000
[    1.868435] hid: raw HID events driver (C) Jiri Kosina
[    1.877186] usbcore: registered new interface driver usbhid
[    1.877188] usbhid: USB HID core driver
[    1.880451] hid-generic 0003:0B05:19AF.0001: hiddev0,hidraw0: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller] on usb-0000:80:14.0-2/input2
[    1.880538] input: Logitech USB Receiver as /devices/pci0000:80/0000:80:14.0/usb3/3-4/3-4.3/3-4.3:1.0/0003:046D:C52B.0002/input/input3

...

It seems that the device at usb 3-14 wasn’t responding correctly previously, but now is. It’s worth noting that this was the first time I had plugged anything into these headers. I have listed the specific headers below for any potential future travelers who may find the information useful.

dmesg info for usb 3-14 from a successful boot:

new high-speed USB device number 6 using xhci_hcd
New USB device found, idVendor=13d3, idProduct=3602, bcdDevice= 1.00
New USB device strings: Mfr=5, Product=6, SerialNumber=7
Product: Wireless_Device
Manufacturer: MediaTek Inc.
SerialNumber: 000000000

So, as a vague theory, perhaps the device at usb 3-14, or its relationship with the motherboard, starts out in an unusual state when first manufactured, before a device is plugged into the headers? Not sure what to make of the Product: Wireless_Device info though - the motherboard has onboard wireless, but it seems odd that connecting USB headers would make this work. Perhaps there is some indirect electronic dependency. In any case, this looks like it’s probably an (apparently temporarily) hardware quirk.

For reference, the new connections I made were:

  • 20 pin USB 5Gbps plug in header labelled U5G_910 on the motherboard
  • 9 pin USB 2.0 plug in header labelled USB_E12 on the motherboard
  • HD Audio plug in the header labelled F_PANEL on the motherboard (unlikely that this one is related…)

Thanks for your help @corradoventu, @halogen2 and @yvesd2.

1 Like
10

Is your power supply big enough? This might be power drainage issues…

11

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