On 16 September 2014 22:01, Romain Francoise <[email protected]> wrote:
> On Mon, Sep 15, 2014 at 10:36:46AM +0200, Romain Francoise wrote:
>> I upgraded from v3.16 to v3.17-rc5 and the ctr-aes-aesni encryption test
>> fails, which makes my IPsec tunnels unhappy (see trace below). Before I
>> start bisecting (2cddcc7df8fd3 is probably my first guess), is this
>> already known?
>
>> Sep 15 08:07:56 silenus kernel: [ 35.137145] alg: skcipher: Test 4 failed
>> on encryption for ctr-aes-aesni [...]
I do not get the above message on a SandyBridge i7-2620M, even though
the module makes use of the "by8" variant on my system, too:
[ 0.340626] AVX version of gcm_enc/dec engaged.
[ 0.340627] AES CTR mode by8 optimization enabled
[ 0.341273] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
> Update: reverting 2cddcc7df8 ("crypto: aes - AES CTR x86_64 "by8" AVX
> optimization") fixes this. This machine is Sandy Bridge (Core i7-2600),
> and the problem doesn't seem to occur with the exact same kernel image
> on Ivy Bridge (Xeon E3-1240v2).
Can you please provide the full kernel log and /proc/cpuinfo of those
machines? It would be interesting to know which variant was used on
those machines -- the new "by8" or the old one.
Thanks,
Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
