Dear maintainer, I reopened this bug, as I think that there is a regression in current versions, because the observed behavior is the same as in this bug report (and in #485070), i.e. there is an alarming message on boot without showing a problem otherwise. I think the problem is well described in #107.
This is the relevant journal output: > systemd-modules-load[153]: Inserted module 'dm_crypt' > systemd-modules-load[153]: Inserted module 'aes_i586' > systemd-modules-load[153]: Failed to insert 'aesni_intel': No such device > systemd-modules-load[153]: Failed to insert 'padlock_aes': No such device > systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE > systemd[1]: Failed to start Load Kernel Modules. > systemd[1]: Unit systemd-modules-load.service entered failed state. This is the alias: > # modprobe --resolve-alias aes > aes_i586 > aesni_intel > padlock_aes So I guess, that -- as desribed in #107 -- loading of the alias aes is requested. But although aes_i586 can be loaded (verified with lsmod), modprobe seems to return 1 leading to the error messages above and the failure of the service (verified with fish shell, so $status is bash's $?): > # modprobe --verbose aes; echo $status > insmod /lib/modules/3.16.0-4-686-pae/kernel/arch/x86/crypto/aesni-intel.ko > modprobe: ERROR: could not insert 'aesni_intel': No such device > insmod /lib/modules/3.16.0-4-686-pae/kernel/drivers/crypto/padlock-aes.ko > modprobe: ERROR: could not insert 'padlock_aes': No such device > 1 modprobe is part of the kmod package, which is installed in version 18-3. Kind regards Patrick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org