Package: linux-image-armmp-lpae Version: 4.19+104 Severity: normal Dear Maintainer,
after upgrading from 4.9.144-3 to 4.19+104 I am not able to mount cryptsetup devices anymore. # cryptsetup luksOpen /dev/lvm-foo/crypto foo Enter passphrase for /dev/lvm-foo/crypto: device-mapper: reload ioctl on failed: No such file or directory Failed to setup dm-crypt key mapping for device /dev/lvm-foo/crypto. Check that kernel supports aes-xts-plain64 cipher (check syslog for more info). device-mapper: remove ioctl on temporary-cryptsetup-3150 failed: No such device or address device-mapper: table ioctl on failed: No such device or address The output of dmesg is: device-mapper: table: 253:8: crypt: Error allocating crypto tfm device-mapper: ioctl: error adding target to table The respective LUKS header of the cryptsetup device looks like this: # cryptsetup luksDump /dev/lvm-foo/crypto LUKS header information for /dev/lvm-foo/crypto Version: 1 Cipher name: aes Cipher mode: xts-plain64 Hash spec: sha1 Payload offset: 4096 MK bits: 256 ... Maybe the lack of the "aes-xts-plain64" cipher is related to the following? # dpkg -L linux-image-4.9.0-8-armmp-lpae | grep aes /lib/modules/4.9.0-8-armmp-lpae/kernel/drivers/crypto/omap-aes.ko # dpkg -L linux-image-4.19.0-4-armmp-lpae | grep aes [no output] I am using a BananaPi M1 board. Thank you for your time! Cheers, Lars
