On 03/19/18 17:00, François Patte wrote: > That was a good idea: yes sometimes I update my machine before stopping > it. Yesterday, as there were a new kernel, I updated the system and > waited until the whole process finished (using top to watch this update > process) and today, in the boot logs, I get: > > mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find > module 'vboxdrv' > mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find > module 'vboxnetflt' > mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find > module 'vboxnetadp' > mars 19 09:17:30 dipankar systemd-modules-load[226]: Failed to find > module 'vboxpci' > mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module > 'vboxdrv' > mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module > 'vboxnetflt' > mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module > 'vboxnetadp' > mars 19 09:17:32 dipankar systemd-modules-load[812]: Inserted module > 'vboxpci' > mars 19 09:17:32 dipankar audit[1]: SERVICE_START pid=1 uid=0 > auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 > msg='unit=systemd-modules-load comm="systemd" > exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' > > Only 2 seconds between the time modules are not found and the time these > modules are inserted... > > Strange! Too bad the log isn't very detailed. It sounds as if systemd-modules-load is looking first in one place for the modules and not finding them. Then, moving on to a second location and finding them. What are the contents of /etc/modules-load.d/*.conf and /usr/lib/modules-load.d/*.conf ? -- Conjecture is just a conclusion based on incomplete information. It isn't a fact.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
