From: Milan Broz <mbroz@redhat.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: linux-crypto@vger.kernel.org
Subject: Re: aesni-intel as module = cryptsetup failure
Date: Sat, 07 May 2011 21:40:20 +0200 [thread overview]
Message-ID: <4DC5A024.2000400@redhat.com> (raw)
In-Reply-To: <BANLkTi=RF-FiHj5Qyh2LT5Eno+FOmvJbDw@mail.gmail.com>
On 05/07/2011 04:21 AM, Andrew Lutomirski wrote:
> I just moved my boot disk from an old machine to a new machine. The
> new machine has AES-NI and it failed to boot.
>
> The problem appears to be that aesni-intel, when loaded as a module,
> makes cryptsetup fail on an aes-xts-plain drive. The error looks
> like:
> device-mapper: reload ioctl failed: Invalid argument
> device-mapper: table: 253:0: crypt: Error allocating crypto tfm
> device-mapper: ioctl: error adding target to table
dmcrypt works with AES-NI without problem.
If it is during boot, probably just some modules are missing in your initramfs.
I remember exactly the same problem and it was caused by missing crypto/fpu.ko
kernel module, adding module to initrams explicitly
like "dracut --force --add-drivers fpu" helped in this case (on Fedora).
Milan
prev parent reply other threads:[~2011-05-07 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 2:21 aesni-intel as module = cryptsetup failure Andrew Lutomirski
2011-05-07 19:40 ` Milan Broz [this message]
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=4DC5A024.2000400@redhat.com \
--to=mbroz@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=luto@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).