[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20171213192758.GA24992@dell12.lru.li>
Date: Wed, 13 Dec 2017 20:27:58 +0100
From: Georg Sauthoff <mail@...rg.so>
To: qat-linux@...el.com
Cc: Giovanni Cabiddu <giovanni.cabiddu@...el.com>,
Salvatore Benedetto <salvatore.benedetto@...el.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Pablo Marcos Oltra <pablo.marcos.oltra@...el.com>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Encrypt selftest fails with qat_c3xxx
Hello,
running Fedora 27 on an Intel Atom C3758 CPU Supermicro system
(A2SDi-8C+-HLN4F) I've noticed that crypto selftests fail when the
qat_c3xxx module is loaded (it is loaded, by default). That means that
stuff like `modprobe dm-crypt`, `cryptsetup benchmark` and `cryptsetup
luksOpen` fail.
The kernel log then contains the following messages:
alg: akcipher: encrypt test failed. err -22
alg: akcipher: test 1 failed for pkcs1pad(qat-rsa,sha256), err=-22
When I blacklist the qat_c3xxx/intel_qat modules the crypto works
as expected.
I can reproduce this issue with 4.14.3-300.fc27.x86_64,
kernel-4.13.16-302.fc27.x86_64 and kernel-4.13.9-300.fc27.x86-64.
See also my report in the Fedora bug tracker:
https://bugzilla.redhat.com/show_bug.cgi?id=1522962#c5
The loaded firmware has this checksum:
md5sum /lib/firmware/qat_c3xxx_mmp.bin
fb7deea913d87aed7676222269a593e6 /lib/firmware/qat_c3xxx_mmp.bin
Is this an issue with the driver, the firmware or does the QAT
co-processor need some additional setup?
Best regards
Georg
--
'(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) Please also check the log file at "/dev/null" for additional information.'
(Fedora 21, gdm-Xorg)
Powered by blists - more mailing lists