On Fri, Mar 03, 2017 at 03:00:26AM -0600, Nathan Royce wrote: > OK, I went ahead and enabled self tests > "CRYPTO_MANAGER_DISABLE_TESTS=n", and my system was able to boot, > albeit with failures: > ***** > Mar 02 23:14:38 server kernel: ---[ end trace 1c8a91f28cbcebf3 ]--- > Mar 02 23:14:38 server kernel: alg: skcipher: encryption failed on > test 1 for xts(ecb-aes-s5p): ret=35 > Mar 02 23:14:38 server kernel: device-mapper: table: 254:0: crypt: > Error allocating crypto tfm > Mar 02 23:14:38 server kernel: device-mapper: ioctl: error adding > target to table > Mar 02 23:14:39 server systemd-cryptsetup[234]: Failed to activate > with key file '/dev/urandom': Invalid argument > ***** > (weird that it asked for the passphrase) > > But I do question whether the root issue is related to s5p... Maybe > there is a correlation in the warning, but to me it looks like the > issue is something else. I see. Do you have ECB enabled in your config? The new XTS requires ECB to be present so that could be your problem. There is already a patch on its way to stable to add the Kconfig select on ECB. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
