I've just upgraded from 3.9.0-rc6 because I needed new versions of ZFS On Linux (because of a unknown problem with the previous version which lead to it refusing to load). I also have zfs-crypto by zfsrogue and when trying to mount a crypted filesystem, I get: filesystem 'share/home/turbo/Crypted' can not be mounted due to error 52 cannot mount 'share/home/turbo/Crypted': Invalid argument This leads to the following in the logs: Nov 13 03:24:53 Celia modprobe: WARNING: Error inserting ghash_clmulni_intel (/lib/modules/3.12.0+scst+tf.1/kernel/arch/x86/crypto/ghash-clmulni-intel.ko): No such device Nov 13 03:24:54 Celia kernel: [ 2053.440315] spl-crypto: Cipher test 'CKM_AES_GCM' -> 'sun-gcm(aes)' successful. Nov 13 03:25:01 Celia kernel: [ 2061.223198] sha256_ssse3: Neither AVX nor SSSE3 is available/usable. Nov 13 03:25:01 Celia modprobe: WARNING: Error inserting sha256_ssse3 (/lib/modules/3.12.0+scst+tf.1/kernel/arch/x86/crypto/sha256-ssse3.ko): No such device Nov 13 03:25:01 Celia modprobe: FATAL: Error inserting padlock_sha (/lib/modules/3.12.0+scst+tf.1/kernel/drivers/crypto/padlock-sha.ko): No such device Trying to load the module sha256_ssse3 manually, I get: celia:/lib/modules/3.12.0+scst+tf.1/kernel# modprobe sha256_ssse3 FATAL: Error inserting sha256_ssse3 (/lib/modules/3.12.0+scst+tf.1/kernel/arch/x86/crypto/sha256-ssse3.ko): No such device with the following in the logs: Nov 13 03:30:15 Celia kernel: [ 2375.004027] sha256_ssse3: Neither AVX nor SSSE3 is available/usable. First time (in early spring) I tested this, when loading the sun-gcm module, I got all kinds of problems (https://github.com/zfsrogue/zfs-crypto/issues/28). Turned out I needed to load the gf128mul and ghash-generic kernel modules. So I'm assuming it's the same thing again, a module doesn't get autoloader by mod probe... Any ideas? -- Imagine you're an idiot and then imagine you're in the government. Oh, sorry. Now I'm repeating myself - Mark Twain -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
