My system thinks it is booting quickly. journlctl -k reports:
-- Logs begin at Wed 2018-10-24 20:44:45 CDT, end at Fri 2018-10-26 21:52:05 CDT. -- Oct 26 20:53:11 Neurosprite kernel: Linux version 4.15.0-38-generic (buildd@lcy01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:59 Oct 26 20:53:11 Neurosprite kernel: Command line: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=UUID=d22f3d07-d029-4bb9-8157-44c0a42bb7d5 ro Oct 26 20:53:11 Neurosprite kernel: KERNEL supported cpus: Oct 26 20:53:11 Neurosprite kernel: Intel GenuineIntel Oct 26 20:53:11 Neurosprite kernel: AMD AuthenticAMD Oct 26 20:53:11 Neurosprite kernel: Centaur CentaurHauls Oct 26 20:53:11 Neurosprite kernel: x86/fpu: x87 FPU will use FXSAVE Oct 26 20:53:11 Neurosprite kernel: e820: BIOS-provided physical RAM map: Oct 26 20:53:11 Neurosprite kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable Oct 26 20:53:11 Neurosprite kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved Oct 26 20:53:11 Neurosprite kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved Oct 26 20:53:11 Neurosprite kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cfdeffff] usable Oct 26 20:53:11 Neurosprite kernel: BIOS-e820: [mem 0x00000000cfdf0000-0x00000000cfdf0fff] ACPI NVS Oct 26 20:53:11 Neurosprite kernel: BIOS-e820: [mem 0x00000000cfdf1000-0x00000000cfdfffff] ACPI data Oct 26 20:53:11 Neurosprite kernel: BIOS-e820: [mem 0x00000000cfe00000-0x00000000cfefffff] reserved O : : Oct 26 20:53:14 Neurosprite kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready Oct 26 20:53:16 Neurosprite kernel: r8169 0000:03:00.0 enp3s0: link up Oct 26 20:53:16 Neurosprite kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready Oct 26 20:53:18 Neurosprite kernel: usblp0: removed Oct 26 20:53:18 Neurosprite kernel: usblp 8-2:1.0: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0028 Oct 26 20:53:19 Neurosprite kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff windo Oct 26 20:53:19 Neurosprite kernel: caller os_map_kernel_space.part.7+0xda/0x120 [nvidia] mapping multiple BARs Oct 26 20:53:25 Neurosprite kernel: rfkill: input handler disabled
that is 12 seconds. Looking at systemd-analyze blame I find:
7.102s configure-printer@usb-008-002.service 2.349s NetworkManager-wait-online.service 1.594s dev-sdb5.device 732ms fwupd.service 709ms snapd.service 558ms lvm2-pvscan@8:50.service 488ms udisks2.service 316ms systemd-journal-flush.service 304ms openvpnas.service 294ms dev-loop0.device 283ms dev-loop2.device 271ms dev-loop1.device 266ms dev-loop8.device 264ms systemd-logind.service 260ms dev-loop6.device 259ms dev-loop3.device 257ms dev-loop9.device 250ms dev-loop13.device 246ms dev-loop4.device 237ms dev-loop5.device 236ms dev-loop10.device 234ms NetworkManager.service 230ms dev-loop11.device 229ms dev-loop7.device 226ms dev-loop12.device 177ms dev-mapper-centos\x2dswap.swap 161ms systemd-udevd.service 157ms snap-gnome\x2dsystem\x2dmonitor-57.mount 156ms snap-core-5662.mount 147ms systemd-resolved.service 146ms networkd-dispatcher.service : :
Consistent with 12 seconds. Except, it takes well over 5 minutes before any of this starts!
Removing "splash" and "quiet" from /etc/default/grub I get 2 lines on a purple background
Loading linux-4.15.0-38-generic... Loading initial ramdisk...
And then 5 minutes later it actually boots.
The system is a fresh install on an SSD. Once running, it runs fast. The boot logs don't even start until after the problem is over.
This is not the same problem others have listed - it does not hang, and the actual booting goes quickly when it starts going. It just does not start for 5 minutes. Anyone have any ideas on why?
Thanks, Mike