From: Georg Sauthoff <mail@georg.so>
To: qat-linux@intel.com
Cc: Giovanni Cabiddu <giovanni.cabiddu@intel.com>,
Salvatore Benedetto <salvatore.benedetto@intel.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Pablo Marcos Oltra <pablo.marcos.oltra@intel.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Encrypt selftest fails with qat_c3xxx
Date: Wed, 13 Dec 2017 20:27:58 +0100 [thread overview]
Message-ID: <20171213192758.GA24992@dell12.lru.li> (raw)
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)
reply other threads:[~2017-12-13 19:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171213192758.GA24992@dell12.lru.li \
--to=mail@georg.so \
--cc=davem@davemloft.net \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pablo.marcos.oltra@intel.com \
--cc=qat-linux@intel.com \
--cc=salvatore.benedetto@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®