Hello,
With regard to:
>** odd entry in dmesg: "alg: hash: Test 3 failed for mv-sha1"
>
>dmesg reveals some slightly concerning messages:
>[ 35.120866] alg: hash: Test 3 failed for mv-sha1
>[ 35.120895] 00000000: 10 bf d7 00 71 0b bb 83 3a 26 d0 97 13 05 99 f5
>[ 35.120910] 00000010: 3a 92 53 3c
>[ 35.216233] alg: hash: Test 1 failed for mv-hmac-sha1
>[ 35.216262] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24
>[ 35.216277] 00000010: b7 c3 16 0c
>This happens on all three machines. Not sure if this is a problem?
This is indeed a problem. I see the same thing on TS-212P with
MV88F6282 CPU running the 3.16 kernel. What it means is that the driver for the hardware crypto engine in the Feroceon failed a self-test (i.e. the cryptographic output is incorrect) and will be disabled. mv_sha1 remains present in /proc/crypto, but any attempt to use it will immediately fall-back to sha1_arm (asm software mode).
For me this is a severe loss of functionality, as the crypto engine is a selling point of those CPUs.
This is likely an upstream bug in mv_cesa.c or the surrounding code. I strongly suspect that more devices with Kirkwood/Feroceon/Armada 300 CPUs are affected.
Should I file a separate bug to track this?
Best regards,
Jan