OSC console size querying hangs at boot in some scenarios

[wreps8Owt]

systemd version the issue has been seen with

257~rc2-3 and 257~rc3-1

Used distribution

Debian GNU/Linux trixie/sid

Linux kernel version used

6.11.10-amd64

CPU architectures issue was seen on

x86_64

Component

systemd-sysv-generator

Expected behaviour you didn't see

Boot without any stop, regardless of the number of SysV services lacking a native systemd unit file.

Unexpected behaviour you saw

Depending on the number of SysV services lacking a native systemd unit file, the system may stop at Inserted module 'autofs4' and need a non-modifier key press to continue. With no key press the system may be stuck here. More present SysV services lacking a native systemd may have a higher probability to trigger this phenomenon.

Steps to reproduce the problem

1. Install many SysV services lacking a native systemd unit file.
2. reboot the system.

Additional program output to the terminal or log subsystem illustrating the issue

No response

[yuwata]

• Please try to boot with systemd.log_level=debug kernel command line option, and provide the debugging logs. Otherwise there is nothing we can do.
• Is it new in v257-rc ? Do you also observe it in v256 or older ?

[wreps8Owt]

- Is it new in v257-rc ? Do you also observe it in v256 or older ?

It did not occur in v256 or older.

[wreps8Owt]

Sometimes removing old journals under /var/log/journal/... also makes this phenomenon disappear.

[poettering]

I am pretty sure this is a red herring. Please provide full logs, otherwise this is not actionable to us.

Do you have closed source drivers (nvidia or so) on your system?

[wreps8Owt]

I am pretty sure this is a red herring. Please provide full logs, otherwise this is not actionable to us. Do you have closed source drivers (nvidia or so) on your system?

I do not haveclosed source drivers.

[shmerl]

Not sure if this is a bug in systemd but it's definitely affecting Debian specifically (unstable and testing now). I got hit by it on multiple installations. And it's somewhat random. Happens part of the times on boot.

[bluca]

Unless someone provides debug logs as requested, this is not actionable

[miraculin1]

Hi, I noticed the same problem with Debian testing. I noticed that when boot without quiet parameter the problem seems not happen(10 in a row).

Below I attached dmesg output with GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.log_level=debug nvidia-drm.modeset=1", the unexpected behavior occurs.
Snippet:

[    6.015462] PM: Image not found (code -22)
[    6.110864] EXT4-fs (nvme1n1p3): mounted filesystem faac5525-49f2-46fd-a595-509aed0b8f59 ro with ordered data mode. Quota mode: none.
[    6.198556] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[    6.230342] systemd[1]: Setting '/proc/sys/kernel/printk_devkmsg' to 'on'
[    6.230492] systemd[1]: Unable to load SELinux policy. Ignoring.
[    6.230499] systemd[1]: Smack is not enabled in the kernel.
[    6.231014] systemd[1]: The early AppArmor policy cache directory /etc/apparmor/earlypolicy/ac27e0ee.0 does not exist.
[    6.231111] systemd[1]: No IMA custom policy file /etc/ima/ima-policy, ignoring: No such file or directory
[    6.231117] systemd[1]: IPE support is disabled in the kernel, ignoring: No such file or directory
[    6.233078] systemd[1]: Loaded 'libkmod.so.2' via dlopen()
[    6.240749] systemd[1]: Loading module: autofs4
[    6.246097] systemd[1]: Inserted module 'autofs4'
[    6.246122] systemd[1]: Loading module: ip_tables
[    6.253212] systemd[1]: Inserted module 'ip_tables'
[    6.253284] systemd[1]: No virtualization found in DMI vendor table.
[    6.253313] systemd[1]: DMI BIOS Extension table does not indicate virtualization.
[    6.253345] systemd[1]: UML virtualization not found in /proc/cpuinfo.
[    6.253352] systemd[1]: Virtualization XEN not found, /proc/xen does not exist
[    6.253356] systemd[1]: No virtualization found in CPUID
[    6.253363] systemd[1]: This platform does not support /proc/device-tree
[    6.253366] systemd[1]: This platform does not support /proc/sysinfo
[    6.253370] systemd[1]: Found VM virtualization none
[    6.253495] systemd[1]: Mounting tmpfs to /dev/shm of type tmpfs with options mode=01777.
[    6.253504] systemd[1]: Mounting tmpfs (tmpfs) on /dev/shm (MS_NOSUID|MS_NODEV|MS_STRICTATIME "mode=01777")...
[    6.253560] systemd[1]: No filesystem is currently mounted on /sys/fs/cgroup.
[    6.253801] systemd[1]: Mounting cgroup2 to /sys/fs/cgroup of type cgroup2 with options nsdelegate,memory_recursiveprot.
[    6.253807] systemd[1]: Mounting cgroup2 (cgroup2) on /sys/fs/cgroup (MS_NOSUID|MS_NODEV|MS_NOEXEC "nsdelegate,memory_recursiveprot")...
[    6.253889] systemd[1]: Mounting pstore to /sys/fs/pstore of type pstore with options n/a.
[    6.253894] systemd[1]: Mounting pstore (pstore) on /sys/fs/pstore (MS_NOSUID|MS_NODEV|MS_NOEXEC "")...
[    6.253940] systemd[1]: Mounting efivarfs to /sys/firmware/efi/efivars of type efivarfs with options n/a.
[    6.253944] systemd[1]: Mounting efivarfs (efivarfs) on /sys/firmware/efi/efivars (MS_NOSUID|MS_NODEV|MS_NOEXEC "")...
[    6.266794] systemd[1]: Mounting bpf to /sys/fs/bpf of type bpf with options mode=0700.
[    6.266804] systemd[1]: Mounting bpf (bpf) on /sys/fs/bpf (MS_NOSUID|MS_NODEV|MS_NOEXEC "mode=0700")...
[    6.268686] systemd[1]: Failed to symlink /proc/self/fd to /dev/fd: File exists
[    6.268692] systemd[1]: Failed to symlink /proc/self/fd/0 to /dev/stdin: File exists
[    6.268696] systemd[1]: Failed to symlink /proc/self/fd/1 to /dev/stdout: File exists
[    6.268701] systemd[1]: Failed to symlink /proc/self/fd/2 to /dev/stderr: File exists
[    6.268787] systemd[1]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
[    6.268806] systemd[1]: Reading EFI variable /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c.
[    6.269051] systemd[1]: Reading EFI variable /sys/firmware/efi/efivars/SystemdOptions-8cf2644b-4b0b-428f-9387-6d876050dc67.
[    6.269066] systemd[1]: open("/sys/firmware/efi/efivars/SystemdOptions-8cf2644b-4b0b-428f-9387-6d876050dc67") failed: No such file or directory
[    6.271735] systemd[1]: ProtectSystem=auto selected, but not running in an initrd, skipping.
[   26.303726] systemd[1]: systemd 257~rc3-1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE)
[   26.303749] systemd[1]: CPUID func 1 0
[   26.303758] systemd[1]: CPUID result a50f00 1100800 7ed8320b 178bfbff
[   26.303767] systemd[1]: CPUID is hypervisor: no
[   26.303779] systemd[1]: Detected architecture x86-64.
[   26.312608] systemd[1]: Detected initialized system, this is not the first boot.
[   26.312623] systemd[1]: Kernel version 6.11.10-amd64, our baseline is 5.4
[   26.313113] systemd[1]: No credentials passed via fw_cfg.
[   26.313309] systemd[1]: Ignoring OEM string: Modern Preload
[   26.313375] systemd[1]: No credentials passed from initrd.
[   26.313385] systemd[1]: Acquired 0 regular credentials, 0 untrusted credentials.
[   26.314113] systemd[1]: Hostname set to <debian-xin>.
[   26.314347] systemd[1]: Successfully added address 127.0.0.1 to loopback interface
[   26.314363] systemd[1]: Successfully added address ::1 to loopback interface
[   26.314377] systemd[1]: Successfully brought loopback interface up
[   26.314756] systemd[1]: Setting '/proc/sys/net/unix/max_dgram_qlen' to '512'
[   26.314773] systemd[1]: Setting '/proc/sys/fs/file-max' to '9223372036854775807'
[   26.314796] systemd[1]: Setting '/proc/sys/fs/nr_open' to '2147483640'
[   26.314811] systemd[1]: Couldn't write fs.nr_open as 2147483640, halving it.
[   26.314820] systemd[1]: Setting '/proc/sys/fs/nr_open' to '1073741816'
[   26.314830] systemd[1]: Successfully bumped fs.nr_open to 1073741816
[   26.315401] systemd[1]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
[   26.315407] systemd[1]: Unified cgroup hierarchy is located at /sys/fs/cgroup.
[   26.349733] systemd[1]: bpf-firewall: Got EBADF when using BPF_F_ALLOW_MULTI, which indicates it is supported. Yay!
[   26.352282] systemd[1]: Loaded 'libbpf.so.1' via dlopen()
[   26.391912] systemd[1]: Loaded 'libbpf.so.1' via dlopen()
[   26.391926] systemd[1]: libbpf: prog 'sd_bind4': failed to attach to cgroup: Bad file descriptor
[   26.392220] systemd[1]: Loaded 'libbpf.so.1' via dlopen()
[   26.392229] systemd[1]: libbpf: prog 'sd_restrictif_i': failed to attach to cgroup: Bad file descriptor
[   26.392243] systemd[1]: Controller 'cpu' supported: yes
[   26.392246] systemd[1]: Controller 'cpuacct' supported: no
[   26.392250] systemd[1]: Controller 'cpuset' supported: yes
[   26.392253] systemd[1]: Controller 'io' supported: yes
[   26.392256] systemd[1]: Controller 'blkio' supported: no
[   26.392259] systemd[1]: Controller 'memory' supported: yes
[   26.392262] systemd[1]: Controller 'devices' supported: no
[   26.392265] systemd[1]: Controller 'pids' supported: yes
[   26.392268] systemd[1]: Controller 'bpf-firewall' supported: yes
[   26.392270] systemd[1]: Controller 'bpf-devices' supported: yes
[   26.392273] systemd[1]: Controller 'bpf-foreign' supported: yes
[   26.392276] systemd[1]: Controller 'bpf-socket-bind' supported: yes
[   26.392279] systemd[1]: Controller 'bpf-restrict-network-interfaces' supported: yes
[   26.392303] systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd.
[   26.489359] systemd[1]: bpf-restrict-fs: LSM BPF program attached
[   26.489421] systemd[1]: Using systemd-executor binary from '/usr/lib/systemd/systemd-executor'.
[   26.498537] systemd[1]: Disabling (error) showing of status (command line).
[   26.499740] systemd[1]: Successfully forked off '(sd-gens)' as PID 413.

Full log:
log_systemd_debug.txt

[YHNdnzj]

The symptoms sounds similar to https://bugzilla.redhat.com/show_bug.cgi?id=2325780

[YHNdnzj]

cc @keszybz have you managed to track down the problem further?

[bluca]

Hi, I noticed the same problem with Debian testing. I noticed that when boot without quiet parameter the problem seems not happen(10 in a row).

Below I attached dmesg output with GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.log_level=debug nvidia-drm.modeset=1", the unexpected behavior occurs. Snippet:

[    6.015462] PM: Image not found (code -22)
[    6.110864] EXT4-fs (nvme1n1p3): mounted filesystem faac5525-49f2-46fd-a595-509aed0b8f59 ro with ordered data mode. Quota mode: none.
[    6.198556] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[    6.230342] systemd[1]: Setting '/proc/sys/kernel/printk_devkmsg' to 'on'
[    6.230492] systemd[1]: Unable to load SELinux policy. Ignoring.
[    6.230499] systemd[1]: Smack is not enabled in the kernel.
[    6.231014] systemd[1]: The early AppArmor policy cache directory /etc/apparmor/earlypolicy/ac27e0ee.0 does not exist.
[    6.231111] systemd[1]: No IMA custom policy file /etc/ima/ima-policy, ignoring: No such file or directory
[    6.231117] systemd[1]: IPE support is disabled in the kernel, ignoring: No such file or directory
[    6.233078] systemd[1]: Loaded 'libkmod.so.2' via dlopen()
[    6.240749] systemd[1]: Loading module: autofs4
[    6.246097] systemd[1]: Inserted module 'autofs4'
[    6.246122] systemd[1]: Loading module: ip_tables
[    6.253212] systemd[1]: Inserted module 'ip_tables'
[    6.253284] systemd[1]: No virtualization found in DMI vendor table.
[    6.253313] systemd[1]: DMI BIOS Extension table does not indicate virtualization.
[    6.253345] systemd[1]: UML virtualization not found in /proc/cpuinfo.
[    6.253352] systemd[1]: Virtualization XEN not found, /proc/xen does not exist
[    6.253356] systemd[1]: No virtualization found in CPUID
[    6.253363] systemd[1]: This platform does not support /proc/device-tree
[    6.253366] systemd[1]: This platform does not support /proc/sysinfo
[    6.253370] systemd[1]: Found VM virtualization none
[    6.253495] systemd[1]: Mounting tmpfs to /dev/shm of type tmpfs with options mode=01777.
[    6.253504] systemd[1]: Mounting tmpfs (tmpfs) on /dev/shm (MS_NOSUID|MS_NODEV|MS_STRICTATIME "mode=01777")...
[    6.253560] systemd[1]: No filesystem is currently mounted on /sys/fs/cgroup.
[    6.253801] systemd[1]: Mounting cgroup2 to /sys/fs/cgroup of type cgroup2 with options nsdelegate,memory_recursiveprot.
[    6.253807] systemd[1]: Mounting cgroup2 (cgroup2) on /sys/fs/cgroup (MS_NOSUID|MS_NODEV|MS_NOEXEC "nsdelegate,memory_recursiveprot")...
[    6.253889] systemd[1]: Mounting pstore to /sys/fs/pstore of type pstore with options n/a.
[    6.253894] systemd[1]: Mounting pstore (pstore) on /sys/fs/pstore (MS_NOSUID|MS_NODEV|MS_NOEXEC "")...
[    6.253940] systemd[1]: Mounting efivarfs to /sys/firmware/efi/efivars of type efivarfs with options n/a.
[    6.253944] systemd[1]: Mounting efivarfs (efivarfs) on /sys/firmware/efi/efivars (MS_NOSUID|MS_NODEV|MS_NOEXEC "")...
[    6.266794] systemd[1]: Mounting bpf to /sys/fs/bpf of type bpf with options mode=0700.
[    6.266804] systemd[1]: Mounting bpf (bpf) on /sys/fs/bpf (MS_NOSUID|MS_NODEV|MS_NOEXEC "mode=0700")...
[    6.268686] systemd[1]: Failed to symlink /proc/self/fd to /dev/fd: File exists
[    6.268692] systemd[1]: Failed to symlink /proc/self/fd/0 to /dev/stdin: File exists
[    6.268696] systemd[1]: Failed to symlink /proc/self/fd/1 to /dev/stdout: File exists
[    6.268701] systemd[1]: Failed to symlink /proc/self/fd/2 to /dev/stderr: File exists
[    6.268787] systemd[1]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
[    6.268806] systemd[1]: Reading EFI variable /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c.
[    6.269051] systemd[1]: Reading EFI variable /sys/firmware/efi/efivars/SystemdOptions-8cf2644b-4b0b-428f-9387-6d876050dc67.
[    6.269066] systemd[1]: open("/sys/firmware/efi/efivars/SystemdOptions-8cf2644b-4b0b-428f-9387-6d876050dc67") failed: No such file or directory
[    6.271735] systemd[1]: ProtectSystem=auto selected, but not running in an initrd, skipping.
[   26.303726] systemd[1]: systemd 257~rc3-1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE)
[   26.303749] systemd[1]: CPUID func 1 0
[   26.303758] systemd[1]: CPUID result a50f00 1100800 7ed8320b 178bfbff
[   26.303767] systemd[1]: CPUID is hypervisor: no
[   26.303779] systemd[1]: Detected architecture x86-64.
[   26.312608] systemd[1]: Detected initialized system, this is not the first boot.
[   26.312623] systemd[1]: Kernel version 6.11.10-amd64, our baseline is 5.4
[   26.313113] systemd[1]: No credentials passed via fw_cfg.
[   26.313309] systemd[1]: Ignoring OEM string: Modern Preload
[   26.313375] systemd[1]: No credentials passed from initrd.
[   26.313385] systemd[1]: Acquired 0 regular credentials, 0 untrusted credentials.
[   26.314113] systemd[1]: Hostname set to <debian-xin>.
[   26.314347] systemd[1]: Successfully added address 127.0.0.1 to loopback interface
[   26.314363] systemd[1]: Successfully added address ::1 to loopback interface
[   26.314377] systemd[1]: Successfully brought loopback interface up
[   26.314756] systemd[1]: Setting '/proc/sys/net/unix/max_dgram_qlen' to '512'
[   26.314773] systemd[1]: Setting '/proc/sys/fs/file-max' to '9223372036854775807'
[   26.314796] systemd[1]: Setting '/proc/sys/fs/nr_open' to '2147483640'
[   26.314811] systemd[1]: Couldn't write fs.nr_open as 2147483640, halving it.
[   26.314820] systemd[1]: Setting '/proc/sys/fs/nr_open' to '1073741816'
[   26.314830] systemd[1]: Successfully bumped fs.nr_open to 1073741816
[   26.315401] systemd[1]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
[   26.315407] systemd[1]: Unified cgroup hierarchy is located at /sys/fs/cgroup.
[   26.349733] systemd[1]: bpf-firewall: Got EBADF when using BPF_F_ALLOW_MULTI, which indicates it is supported. Yay!
[   26.352282] systemd[1]: Loaded 'libbpf.so.1' via dlopen()
[   26.391912] systemd[1]: Loaded 'libbpf.so.1' via dlopen()
[   26.391926] systemd[1]: libbpf: prog 'sd_bind4': failed to attach to cgroup: Bad file descriptor
[   26.392220] systemd[1]: Loaded 'libbpf.so.1' via dlopen()
[   26.392229] systemd[1]: libbpf: prog 'sd_restrictif_i': failed to attach to cgroup: Bad file descriptor
[   26.392243] systemd[1]: Controller 'cpu' supported: yes
[   26.392246] systemd[1]: Controller 'cpuacct' supported: no
[   26.392250] systemd[1]: Controller 'cpuset' supported: yes
[   26.392253] systemd[1]: Controller 'io' supported: yes
[   26.392256] systemd[1]: Controller 'blkio' supported: no
[   26.392259] systemd[1]: Controller 'memory' supported: yes
[   26.392262] systemd[1]: Controller 'devices' supported: no
[   26.392265] systemd[1]: Controller 'pids' supported: yes
[   26.392268] systemd[1]: Controller 'bpf-firewall' supported: yes
[   26.392270] systemd[1]: Controller 'bpf-devices' supported: yes
[   26.392273] systemd[1]: Controller 'bpf-foreign' supported: yes
[   26.392276] systemd[1]: Controller 'bpf-socket-bind' supported: yes
[   26.392279] systemd[1]: Controller 'bpf-restrict-network-interfaces' supported: yes
[   26.392303] systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd.
[   26.489359] systemd[1]: bpf-restrict-fs: LSM BPF program attached
[   26.489421] systemd[1]: Using systemd-executor binary from '/usr/lib/systemd/systemd-executor'.
[   26.498537] systemd[1]: Disabling (error) showing of status (command line).
[   26.499740] systemd[1]: Successfully forked off '(sd-gens)' as PID 413.

Full log: log_systemd_debug.txt

Where would the problem be? There doesn't seem to be any indication that the sysv-generator is having any issue or hang?

[   26.503525] (sd-exec-[414]: About to execute /usr/lib/systemd/system-generators/systemd-sysv-generator (null)
[   26.503684] (sd-exec-[414]: Successfully forked off '(exec-inner)' as PID 428.
[   26.508819] systemd-sysv-generator[428]: Native unit for dbus.service already exists, skipping.
[   26.509381] systemd-sysv-generator[428]: Native unit for apparmor.service already exists, skipping.
[   26.509620] systemd-sysv-generator[428]: Native unit for iscsid.service already exists, skipping.
[   26.509782] systemd-sysv-generator[428]: Native unit for keyboard-setup.service already exists, skipping.
[   26.510258] systemd-sysv-generator[428]: Native unit for cron.service already exists, skipping.
[   26.510490] systemd-sysv-generator[428]: Native unit for anacron.service already exists, skipping.
[   26.511351] systemd-sysv-generator[428]: Native unit for plymouth-log.service already exists, skipping.
[   26.512173] systemd-sysv-generator[428]: Native unit for kmod.service already exists, skipping.
[   26.513863] systemd-sysv-generator[428]: Linked unit file: /usr/lib/systemd/system/hwclock.service → /dev/null
[   26.513869] systemd-sysv-generator[428]: Native unit for hwclock.service already exists, skipping.
[   26.514027] systemd-sysv-generator[428]: Native unit for console-setup.service already exists, skipping.
[   26.514234] systemd-sysv-generator[428]: Linked unit file: /usr/lib/systemd/system/cgroupfs-mount.service → /dev/null
[   26.514242] systemd-sysv-generator[428]: Native unit for cgroupfs-mount.service already exists, skipping.
[   26.514531] systemd-sysv-generator[428]: Native unit for rpcbind.service already exists, skipping.
[   26.514680] systemd-sysv-generator[428]: Native unit for bluetooth.service already exists, skipping.
[   26.514872] systemd-sysv-generator[428]: Linked unit file: /usr/lib/systemd/system/x11-common.service → /dev/null
[   26.514876] systemd-sysv-generator[428]: Native unit for x11-common.service already exists, skipping.
[   26.515035] systemd-sysv-generator[428]: Native unit for tlp.service already exists, skipping.
[   26.515075] systemd-sysv-generator[428]: Linked unit file: /usr/lib/systemd/system/nfs-common.service → /dev/null
[   26.515079] systemd-sysv-generator[428]: Native unit for nfs-common.service already exists, skipping.
[   26.515116] systemd-sysv-generator[428]: Linked unit file: /usr/lib/systemd/system/saned.service → /dev/null
[   26.515120] systemd-sysv-generator[428]: Native unit for saned.service already exists, skipping.
[   26.515267] systemd-sysv-generator[428]: Native unit for rsync.service already exists, skipping.
[   26.515836] systemd-sysv-generator[428]: Native unit for gdm3.service already exists, skipping.
[   26.515988] systemd-sysv-generator[428]: Native unit for open-iscsi.service already exists, skipping.
[   26.516175] systemd-sysv-generator[428]: Linked unit file: /usr/lib/systemd/system/alsa-utils.service → /dev/null
[   26.516180] systemd-sysv-generator[428]: Native unit for alsa-utils.service already exists, skipping.
[   26.516521] systemd-sysv-generator[428]: Native unit for plymouth.service already exists, skipping.
[   26.516670] systemd-sysv-generator[428]: Native unit for networking.service already exists, skipping.
[   26.516976] systemd-sysv-generator[428]: Native unit for lm-sensors.service already exists, skipping.
[   26.517285] systemd-sysv-generator[428]: Native unit for procps.service already exists, skipping.
[   26.517324] systemd-sysv-generator[428]: Linked unit file: /usr/lib/systemd/system/sudo.service → /dev/null
[   26.517328] systemd-sysv-generator[428]: Native unit for sudo.service already exists, skipping.
[   26.517613] systemd-sysv-generator[428]: Native unit for nvidia-persistenced.service already exists, skipping.
[   26.517940] systemd-sysv-generator[428]: Native unit for speech-dispatcher.service already exists, skipping.
[   26.518274] systemd-sysv-generator[428]: Native unit for cups.service already exists, skipping.
[   26.518895] systemd-sysv-generator[428]: Native unit for docker.service already exists, skipping.
[   26.519048] systemd-sysv-generator[428]: Native unit for exim4.service already exists, skipping.
[   26.519199] systemd-sysv-generator[428]: Native unit for cups-browsed.service already exists, skipping.
[   26.519470] systemd-sysv-generator[428]: Ignoring S01rsync symlink in rc2.d, not generating rsync.service.
[   26.519474] systemd-sysv-generator[428]: Ignoring S01tlp symlink in rc2.d, not generating tlp.service.
[   26.519478] systemd-sysv-generator[428]: Ignoring S01anacron symlink in rc2.d, not generating anacron.service.
[   26.519481] systemd-sysv-generator[428]: Ignoring S01sudo symlink in rc2.d, not generating sudo.service.
[   26.519485] systemd-sysv-generator[428]: Ignoring S01cups-browsed symlink in rc2.d, not generating cups-browsed.service.
[   26.519489] systemd-sysv-generator[428]: Ignoring S01plymouth symlink in rc2.d, not generating plymouth.service.
[   26.519492] systemd-sysv-generator[428]: Ignoring S01gdm3 symlink in rc2.d, not generating gdm3.service.
[   26.519496] systemd-sysv-generator[428]: Ignoring S01console-setup.sh symlink in rc2.d, not generating console-setup.service.
[   26.519500] systemd-sysv-generator[428]: Ignoring S01exim4 symlink in rc2.d, not generating exim4.service.
[   26.519503] systemd-sysv-generator[428]: Ignoring S01dbus symlink in rc2.d, not generating dbus.service.
[   26.519507] systemd-sysv-generator[428]: Ignoring S01cron symlink in rc2.d, not generating cron.service.
[   26.519510] systemd-sysv-generator[428]: Ignoring S01docker symlink in rc2.d, not generating docker.service.
[   26.519514] systemd-sysv-generator[428]: Ignoring S01cups symlink in rc2.d, not generating cups.service.
[   26.519518] systemd-sysv-generator[428]: Ignoring S01cgroupfs-mount symlink in rc2.d, not generating cgroupfs-mount.service.
[   26.519521] systemd-sysv-generator[428]: Ignoring S01bluetooth symlink in rc2.d, not generating bluetooth.service.
[   26.519525] systemd-sysv-generator[428]: Ignoring S01nvidia-persistenced symlink in rc2.d, not generating nvidia-persistenced.service.
[   26.519529] systemd-sysv-generator[428]: Ignoring S01saned symlink in rc2.d, not generating saned.service.
[   26.519667] systemd-sysv-generator[428]: Ignoring S01rsync symlink in rc3.d, not generating rsync.service.
[   26.519671] systemd-sysv-generator[428]: Ignoring S01tlp symlink in rc3.d, not generating tlp.service.
[   26.519674] systemd-sysv-generator[428]: Ignoring S01anacron symlink in rc3.d, not generating anacron.service.
[   26.519678] systemd-sysv-generator[428]: Ignoring S01sudo symlink in rc3.d, not generating sudo.service.
[   26.519682] systemd-sysv-generator[428]: Ignoring S01cups-browsed symlink in rc3.d, not generating cups-browsed.service.
[   26.519685] systemd-sysv-generator[428]: Ignoring S01plymouth symlink in rc3.d, not generating plymouth.service.
[   26.519689] systemd-sysv-generator[428]: Ignoring S01gdm3 symlink in rc3.d, not generating gdm3.service.
[   26.519693] systemd-sysv-generator[428]: Ignoring S01console-setup.sh symlink in rc3.d, not generating console-setup.service.
[   26.519696] systemd-sysv-generator[428]: Ignoring S01exim4 symlink in rc3.d, not generating exim4.service.
[   26.519700] systemd-sysv-generator[428]: Ignoring S01dbus symlink in rc3.d, not generating dbus.service.
[   26.519703] systemd-sysv-generator[428]: Ignoring S01cron symlink in rc3.d, not generating cron.service.
[   26.519707] systemd-sysv-generator[428]: Ignoring S01docker symlink in rc3.d, not generating docker.service.
[   26.519710] systemd-sysv-generator[428]: Ignoring S01cups symlink in rc3.d, not generating cups.service.
[   26.519714] systemd-sysv-generator[428]: Ignoring S01cgroupfs-mount symlink in rc3.d, not generating cgroupfs-mount.service.
[   26.519717] systemd-sysv-generator[428]: Ignoring S01bluetooth symlink in rc3.d, not generating bluetooth.service.
[   26.519721] systemd-sysv-generator[428]: Ignoring S01nvidia-persistenced symlink in rc3.d, not generating nvidia-persistenced.service.
[   26.519725] systemd-sysv-generator[428]: Ignoring S01saned symlink in rc3.d, not generating saned.service.
[   26.519865] systemd-sysv-generator[428]: Ignoring S01rsync symlink in rc4.d, not generating rsync.service.
[   26.519869] systemd-sysv-generator[428]: Ignoring S01tlp symlink in rc4.d, not generating tlp.service.
[   26.519872] systemd-sysv-generator[428]: Ignoring S01anacron symlink in rc4.d, not generating anacron.service.
[   26.519876] systemd-sysv-generator[428]: Ignoring S01sudo symlink in rc4.d, not generating sudo.service.
[   26.519880] systemd-sysv-generator[428]: Ignoring S01cups-browsed symlink in rc4.d, not generating cups-browsed.service.
[   26.519883] systemd-sysv-generator[428]: Ignoring S01plymouth symlink in rc4.d, not generating plymouth.service.
[   26.519887] systemd-sysv-generator[428]: Ignoring S01gdm3 symlink in rc4.d, not generating gdm3.service.
[   26.519890] systemd-sysv-generator[428]: Ignoring S01console-setup.sh symlink in rc4.d, not generating console-setup.service.
[   26.519894] systemd-sysv-generator[428]: Ignoring S01exim4 symlink in rc4.d, not generating exim4.service.
[   26.519897] systemd-sysv-generator[428]: Ignoring S01dbus symlink in rc4.d, not generating dbus.service.
[   26.519901] systemd-sysv-generator[428]: Ignoring S01cron symlink in rc4.d, not generating cron.service.
[   26.519904] systemd-sysv-generator[428]: Ignoring S01docker symlink in rc4.d, not generating docker.service.
[   26.519908] systemd-sysv-generator[428]: Ignoring S01cups symlink in rc4.d, not generating cups.service.
[   26.519912] systemd-sysv-generator[428]: Ignoring S01cgroupfs-mount symlink in rc4.d, not generating cgroupfs-mount.service.
[   26.519915] systemd-sysv-generator[428]: Ignoring S01bluetooth symlink in rc4.d, not generating bluetooth.service.
[   26.519919] systemd-sysv-generator[428]: Ignoring S01nvidia-persistenced symlink in rc4.d, not generating nvidia-persistenced.service.
[   26.519922] systemd-sysv-generator[428]: Ignoring S01saned symlink in rc4.d, not generating saned.service.
[   26.519998] systemd-sysv-generator[428]: Ignoring S01rsync symlink in rc5.d, not generating rsync.service.
[   26.520002] systemd-sysv-generator[428]: Ignoring S01tlp symlink in rc5.d, not generating tlp.service.
[   26.520005] systemd-sysv-generator[428]: Ignoring S01anacron symlink in rc5.d, not generating anacron.service.
[   26.520009] systemd-sysv-generator[428]: Ignoring S01sudo symlink in rc5.d, not generating sudo.service.
[   26.520013] systemd-sysv-generator[428]: Ignoring S01cups-browsed symlink in rc5.d, not generating cups-browsed.service.
[   26.520016] systemd-sysv-generator[428]: Ignoring S01plymouth symlink in rc5.d, not generating plymouth.service.
[   26.520020] systemd-sysv-generator[428]: Ignoring S01gdm3 symlink in rc5.d, not generating gdm3.service.
[   26.520024] systemd-sysv-generator[428]: Ignoring S01console-setup.sh symlink in rc5.d, not generating console-setup.service.
[   26.520027] systemd-sysv-generator[428]: Ignoring S01exim4 symlink in rc5.d, not generating exim4.service.
[   26.520031] systemd-sysv-generator[428]: Ignoring S01dbus symlink in rc5.d, not generating dbus.service.
[   26.520034] systemd-sysv-generator[428]: Ignoring S01cron symlink in rc5.d, not generating cron.service.
[   26.520038] systemd-sysv-generator[428]: Ignoring S01docker symlink in rc5.d, not generating docker.service.
[   26.520041] systemd-sysv-generator[428]: Ignoring S01cups symlink in rc5.d, not generating cups.service.
[   26.520045] systemd-sysv-generator[428]: Ignoring S01cgroupfs-mount symlink in rc5.d, not generating cgroupfs-mount.service.
[   26.520048] systemd-sysv-generator[428]: Ignoring S01bluetooth symlink in rc5.d, not generating bluetooth.service.
[   26.520052] systemd-sysv-generator[428]: Ignoring S01nvidia-persistenced symlink in rc5.d, not generating nvidia-persistenced.service.
[   26.520056] systemd-sysv-generator[428]: Ignoring S01saned symlink in rc5.d, not generating saned.service.
[   26.520380] (sd-exec-[414]: /usr/lib/systemd/system-generators/systemd-sysv-generator succeeded.

At what point exactly in the sequence did this hang occur?