Quoting Sandra Schlichting <littlesandr...@gmail.com>:
I think you are using wrong module argument, type= instead of mode=. Try
'modprobe tcrypt sec=2 mode=402' instead.
Thanks. I would never have thought of that =)
Now it preforms the test, but gives this interesting error:
[root@amd ~]# modprobe tcrypt sec=2 mode=402
Message from syslogd@amd at Dec 28 14:01:05 ...
kernel:[ 5508.698788] BUG: soft lockup - CPU#0 stuck for 22s!
[modprobe:3416]
Tcrypt does all work in module init, which can take long time and
therefore triggers 'soft lockup' warning.
Possible solutions are:
1. Build kernel with CONFIG_LOCKUP_DETECTOR option disabled,
2. Boot kernel with 'nowatchdog' argument,
3. Ignore warning.
ERROR: could not insert 'tcrypt': Resource temporarily unavailable
Tcrypt fails to load after running tests, that's expected.
-Jussi
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
