Michael S. Tsirkin wrote: > I am booting a thinkpad T60p off of an encrypted disk (with crypto > modules in initramfs). > This works fine in 2.6.24, but in both 2.6.25-rc1 and 2.6.25-rc2 > won't boot with the following messages on the console > (copied by hand, sorry about typos): > device-mapper: table: 254:0:crypt > Error allocating crypto tfm > Failed to setup dm_crypt key mapping. > check kernel for support for the aes-cbc-essiv:sha256 > cipher spec and verify that /dev/sda6 contains at least 133 sectors. > Failed to read from storage. > > git bisec points to the following commit: > > commit 3a7f6c990ad04e6f576a159876c602d14d6f7fef > dm crypt: use async crypto > > Reverting commit 3a7f6c990ad04e6f576a159876c602d14d6f7fef > on top of 2.6.25-rc2 results in a bootable configuration for me. > > .config attached. It seems that some module dependency was lost, dm-crypt with async crypto depends now on crypto_blkcipher module for this configuration. Herbert, any following change required for dm-crypt or it is only crypto subsystem issue? (With old kernel/dm-crypt it loads "blkcipher" not "crypto_blkcipher", maybe some initramdisk change required too...) Milan -- mbroz@xxxxxxxxxx --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
