Absurd boot time (because of hundreds of dev-tty.device and sys-device-platform)

English Install/Boot/Login
1

Hey guys. I’ve installed another distro in dual boot and both works fine, except TW takes two minutes to boot.

Here’s what systemd-analyse tells me:

Startup finished in 6.072s (firmware) + 5.664s (loader) + 761ms (kernel) + 5.055s (initrd) + 1min 35.185s (userspace) = 1min 52.741s 
graphical.target reached after 1min 34.869s in userspace.

Here’s what systemd-analyze blame tells me:

5.368s dev-ttyS11.device
5.367s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device
5.365s dev-ttyS20.device
5.368s dev-ttyS11.device
5.368s dev-ttyS11.device
5.367s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device
5.365s dev-ttyS20.device
5.365s sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device
5.360s dev-ttyS4.device
5.360s sys-devices-pci0000:00-0000:00:16.3-0000:00:16.3:0-0000:00:16.3:0.0-tty-ttyS4.device
5.359s dev-ttyS0.device
5.359s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
5.358s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
5.358s dev-ttyS2.device
5.356s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
5.356s dev-ttyS1.device
5.354s dev-ttyS10.device
5.354s sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device
5.353s sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device
5.353s dev-ttyS12.device
5.351s sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device
5.351s dev-ttyS18.device
5.350s sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device
5.350s dev-ttyS27.device
5.344s sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device
5.344s dev-ttyS22.device
5.342s sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device
5.342s dev-ttyS14.device
5.341s dev-ttyS17.device
5.341s sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device
5.340s dev-ttyS24.device
5.340s sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device
5.336s dev-ttyS19.device
5.336s sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device
5.335s dev-ttyS3.device
5.335s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
5.334s dev-ttyS15.device
5.334s sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device
5.334s dev-ttyS23.device
5.334s sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device
5.333s dev-ttyS13.device
5.333s sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device
5.331s dev-ttyS30.device
5.331s sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device
5.331s dev-ttyS25.device
5.331s sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device
5.328s dev-ttyS26.device
5.328s sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device
5.328s dev-ttyS16.device
5.328s sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device
5.328s sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device
5.328s dev-ttyS7.device
5.327s sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device
5.327s dev-ttyS9.device
5.326s sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device
5.326s dev-ttyS21.device
5.325s dev-ttyS5.device
5.325s sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device
5.314s sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device
5.314s dev-ttyS28.device
5.313s sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device
5.313s dev-ttyS8.device
5.309s sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device
5.309s dev-ttyS29.device
5.307s sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device
5.307s dev-ttyS31.device
5.306s sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device
5.306s dev-ttyS6.device
4.834s sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda1.device
4.834s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2\x2dpart1.device
4.834s dev-disk-by\x2dpartuuid-3a5688a7\x2dc933\x2d43b3\x2d864e\x2dd1ad0f35c694.device
4.834s dev-disk-by\x2did-scsi\x2d35002538d00000000\x2dpart1.device
4.834s dev-disk-by\x2ddiskseq-1\x2dpart1.device
4.834s dev-disk-by\x2dpartlabel-EFI\x5cx20system\x5cx20partition.device
4.834s dev-disk-by\x2did-wwn\x2d0x5002538d00000000\x2dpart1.device
4.834s dev-disk-by\x2did-ata\x2dSAMSUNG_MZ7LN512HMJP\x2d000L7_S2X9NX0H700876\x2dpart1.device
4.834s dev-disk-by\x2duuid-3696\x2dD623.device
4.834s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2.0\x2dpart1.device
4.834s dev-sda1.device
4.834s dev-disk-by\x2dlabel-SYSTEM_DRV.device
4.803s dev-disk-by\x2dpartuuid-216e64da\x2d25da\x2d4fba\x2d809c\x2d8a00c10b9068.device
4.803s dev-disk-by\x2duuid-c3276dc1\x2d059f\x2d4fc0\x2d9d7e\x2da5c8803883b9.device
4.803s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2.0\x2dpart2.device
4.803s dev-disk-by\x2did-scsi\x2d35002538d00000000\x2dpart2.device
4.803s dev-sda2.device
4.803s sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda2.device
4.803s dev-disk-by\x2ddiskseq-1\x2dpart2.device
4.803s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2\x2dpart2.device
4.803s dev-disk-by\x2did-ata\x2dSAMSUNG_MZ7LN512HMJP\x2d000L7_S2X9NX0H700876\x2dpart2.device
4.803s dev-disk-by\x2did-wwn\x2d0x5002538d00000000\x2dpart2.device
4.767s dev-disk-by\x2dpartuuid-522ffc1c\x2df670\x2d407e\x2dbcef\x2d381dd97566d2.device
4.767s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2.0\x2dpart3.device
4.767s dev-disk-by\x2did-wwn\x2d0x5002538d00000000\x2dpart3.device
4.767s dev-disk-by\x2did-ata\x2dSAMSUNG_MZ7LN512HMJP\x2d000L7_S2X9NX0H700876\x2dpart3.device
4.767s dev-disk-by\x2duuid-3af10c7d\x2d156b\x2d4815\x2d91e1\x2d560c81b1fd68.device
4.767s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2\x2dpart3.device
4.767s dev-disk-by\x2did-scsi\x2d35002538d00000000\x2dpart3.device
4.767s dev-sda3.device
4.767s sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda3.device
4.767s dev-disk-by\x2ddiskseq-1\x2dpart3.device
4.732s sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda-sda4.device
4.732s dev-disk-by\x2did-ata\x2dSAMSUNG_MZ7LN512HMJP\x2d000L7_S2X9NX0H700876\x2dpart4.device
4.732s dev-disk-by\x2duuid-5ce7e1ca\x2d3330\x2d465d\x2d8c09\x2dbf658972b3e7.device
4.732s dev-disk-by\x2did-scsi\x2d35002538d00000000\x2dpart4.device
4.732s dev-disk-by\x2dpartlabel-debian.device
4.732s dev-disk-by\x2ddiskseq-1\x2dpart4.device
4.732s dev-disk-by\x2did-wwn\x2d0x5002538d00000000\x2dpart4.device
4.732s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2.0\x2dpart4.device
4.732s dev-sda4.device
4.732s dev-disk-by\x2dpartuuid-e1aafb89\x2d36fc\x2d4ea2\x2d91ae\x2d87c64390ef7c.device
4.732s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2\x2dpart4.device
4.714s dev-disk-by\x2did-wwn\x2d0x5002538d00000000.device
4.714s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2.device
4.714s dev-disk-by\x2ddiskseq-1.device
4.714s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d2.0.device
4.714s dev-disk-by\x2did-ata\x2dSAMSUNG_MZ7LN512HMJP\x2d000L7_S2X9NX0H700876.device
4.714s dev-disk-by\x2did-scsi\x2d35002538d00000000.device
4.714s dev-sda.device
4.714s sys-devices-pci0000:00-0000:00:17.0-ata2-host1-target1:0:0-1:0:0:0-block-sda.device
3.380s dracut-initqueue.service
2.125s sys-devices-pci0000:00-0000:00:02.0-drm-card1-card1\x2deDP\x2d1-intel_backlight.device
1.271s vboxdrv.service
1.207s initrd-switch-root.service
1.148s NetworkManager.service
1.138s prime-select.service
 953ms postfix.service
 698ms systemd-journal-flush.service
 684ms firewalld.service
 647ms display-manager.service
 576ms ModemManager.service
 480ms apparmor.service
 396ms augenrules.service
 395ms dracut-pre-udev.service
 394ms polkit.service
 371ms smartd.service
 312ms tlp.service
 294ms avahi-daemon.service
 282ms systemd-logind.service
 281ms \x2esnapshots.mount
 274ms boot-grub2-i386\x2dpc.mount
 270ms boot-grub2-x86_64\x2defi.mount
 265ms chronyd.service
 262ms home.mount
 255ms bluetooth.service
 244ms opt.mount
 239ms cups.service
 238ms user@1000.service
 228ms boot-efi.mount
 228ms systemd-udev-trigger.service
 212ms dbus.service
 201ms sound-extra.service
 200ms systemd-backlight@backlight:intel_backlight.service
 198ms systemd-backlight@leds:tpacpi::kbd_backlight.service
 183ms systemd-random-seed.service
 182ms kbdsettings.service
 165ms root.mount
 155ms upower.service
 144ms srv.mount
 144ms systemd-journald.service
 127ms wpa_supplicant.service
 122ms systemd-vconsole-setup.service
 120ms usr-local.mount
 117ms plymouth-quit-wait.service
 108ms systemd-udevd.service
 106ms mcelog.service
 106ms var.mount
 101ms plymouth-start.service
 101ms lvm2-monitor.service
  97ms systemd-fsck@dev-disk-by\x2duuid-3696\x2dD623.service
  91ms alsa-restore.service
  86ms rtkit-daemon.service
  85ms accounts-daemon.service
  77ms issue-generator.service
  75ms dracut-shutdown.service
  74ms dracut-cmdline.service
  54ms systemd-tmpfiles-setup.service
  53ms systemd-tmpfiles-setup-dev-early.service
  50ms udisks2.service
  49ms systemd-fsck-root.service
  48ms dev-hugepages.mount
  47ms dev-mqueue.mount
  46ms auditd.service
  46ms sys-kernel-debug.mount
  44ms sys-kernel-tracing.mount
  42ms systemd-binfmt.service
  39ms kmod-static-nodes.service
  39ms plymouth-switch-root.service
  36ms NetworkManager-wait-online.service
  34ms systemd-remount-fs.service
  34ms modprobe@configfs.service
  34ms modprobe@fuse.service
  31ms modprobe@drm.service
  27ms plymouth-read-write.service
  26ms initrd-cleanup.service
  26ms sys-kernel-config.mount
  25ms wtmpdb-update-boot.service
  24ms systemd-modules-load.service
  23ms initrd-parse-etc.service
  23ms systemd-tmpfiles-setup-dev.service
  23ms vboxautostart-service.service
  21ms tmp.mount
  20ms systemd-user-sessions.service
  19ms proc-sys-fs-binfmt_misc.mount
  18ms kernel-sysctl.service
  16ms modprobe@efi_pstore.service
  16ms systemd-sysctl.service
  14ms initrd-udevadm-cleanup-db.service
  14ms sys-fs-fuse-connections.mount
  12ms user-runtime-dir@1000.service

I shoud mention that it happened after I installed another distro in dual boot. I’ve tried reinstalling grub, restoring the EFI partition to an earlier backup, nothing changed. Any idea what all these tty-device and sys-device-platform are?

2

systemd-analyze critical-chain should make it easier to identify what’s to blame for unreasonable boot time.

3

It gave me this:

graphical.target @1min 35.103s
└─multi-user.target @1min 35.103s
  └─cron.service @1min 35.102s
    └─postfix.service @1min 34.075s +998ms
      └─time-sync.target @1min 34.048s
        └─chronyd.service @1min 33.782s +265ms
          └─network.target @1min 33.740s
            └─NetworkManager.service @1min 32.780s +959ms
              └─network-pre.target @1min 32.777s
                └─wpa_supplicant.service @1min 33.802s +117ms
                  └─dbus.service @1min 31.346s +330ms
                    └─basic.target @1min 31.301s
                      └─sockets.target @1min 31.301s
                        └─pcscd.socket @1min 31.301s
                          └─sysinit.target @1min 31.298s
                            └─auditd.service @1min 31.249s +47ms
                              └─systemd-tmpfiles-setup.service @1min 31.155s +60ms
                                └─local-fs.target @1min 31.138s
                                  └─tmp.mount @1min 31.109s +26ms
                                    └─local-fs-pre.target @1.213s
                                      └─systemd-tmpfiles-setup-dev.service @1.195s +17ms
                                        └─systemd-tmpfiles-setup-dev-early.service @1.132s +34ms
                                          └─kmod-static-nodes.service @1.042s +69ms
                                            └─systemd-journald.socket
                                              └─system.slice
                                                └─-.slice
4

Here’s a 90s gap suggesting possible filesystem issue(s). Please paste your fstab here.

5

Here you go:

UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /                       btrfs  defaults                      0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /var                    btrfs  subvol=/@/var                 0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /usr/local              btrfs  subvol=/@/usr/local           0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /srv                    btrfs  subvol=/@/srv                 0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /root                   btrfs  subvol=/@/root                0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /opt                    btrfs  subvol=/@/opt                 0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /home                   btrfs  subvol=/@/home                0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /boot/grub2/i386-pc     btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=8aeafe0f-8dba-4c3a-9cb0-0b21598ea5ab  swap                    swap   defaults                      0  0
UUID=c3276dc1-059f-4fc0-9d7e-a5c8803883b9  /.snapshots             btrfs  subvol=/@/.snapshots          0  0
UUID=3696-D623                             /boot/efi               vfat   utf8                          0  2

This is written in /etc/fstab. I don’t see anything abnormal.

6

I don’t see anything either, and since I don’t use btrfs, I have nothing to suggest WRT your TW installation’s filesystem. What other OS(es) is/are installed? And on what filesystem type(s)? Did you look in journalctl -b for fail or error messages?

7

@BobLeRigoleur when you installed the supplementary OS, did you share the same swap and format it there? That can lead to some issues with UUID’s…

Can you check the output from cat /proc/cmdline at verify the resume entry if present is the same. Also check the suplementary OS for swap fstab and cmdline info…

Also when using blame, make sure you post the first entries seen as sometime there are things lurking there for maintenance.

You also have a number of default entries that you may wish to disable mask for example are you using a smart card, not sure why cron is running as this has been superseded by systemd timers…

1 Like
8

The problem is with tmp.mount:

3400g:~ # journalctl -b -u tmp.mount -o short-monotonic 
[    5.568760] 3400g systemd[1]: Mounted Temporary Directory /tmp.
3400g:~ #

Hosts 3400g mounts it with further ado. Provide more information on your host.

9

Thanks for your help guys but I ended up restoring a clonezilla backup from before the dual boot, probably my best shot given I found nobody with a smiliar problem.

10

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