Comment 10 for bug 1623383

Still happened, even without any modules getting loaded by that service. Maybe the specific service is a red-herring and its something else which just shows there because the service is in the critical path. For making things more clear, here the messages related to it from boot -1 (a failed one) and 0 (a successful one):

ubuntu@s2lp4:~$ journalctl -b-1|grep modules-load
Sep 22 08:13:54 s2lp4 systemd[582]: systemd-modules-load.service: Executing: /lib/systemd/systemd-modules-load
Sep 22 08:13:54 s2lp4 systemd-modules-load[582]: apply: /etc/modules-load.d/modules.conf
Sep 22 13:15:44 s2lp4 systemd[1]: systemd-modules-load.service: Failed to send unit remove signal for systemd-modules-load.service: Transport endpoint is not connected
Sep 22 13:15:44 s2lp4 systemd[1]: systemd-modules-load.service: Changed dead -> exited
Sep 22 13:15:45 s2lp4 systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected

ubuntu@s2lp4:~$ journalctl -b0|grep modules-load
Sep 22 23:44:44 s2lp4 systemd[1613]: systemd-modules-load.service: Executing: /lib/systemd/systemd-modules-load
Sep 22 23:44:44 s2lp4 systemd-modules-load[1613]: apply: /etc/modules-load.d/modules.conf
Sep 22 23:44:48 s2lp4 systemd[1]: Got cgroup empty notification for: /system.slice/systemd-modules-load.service
Sep 22 23:44:48 s2lp4 systemd[1]: systemd-modules-load.service: cgroup is empty