[Pkg-cryptsetup-devel] Bug#466573: Bug#466573: cryptsetup: 2.6.25-rc2 does not boot due to "Error allocating crypto tfm"

[David Härdeman]

On Tue, February 19, 2008 23:38, Didier Raboud wrote:
...
> $ ls -la /tmp/init-2.6.25/lib/modules/2.6.25-rc2-amd64/kernel/crypto/
> total 93
> drwxr-xr-x 2 didier didier  1024 2008-02-19 23:31 .
> drwxr-xr-x 8 didier didier  1024 2008-02-19 23:31 ..
> -rw-r--r-- 1 didier didier 33060 2008-02-19 23:31 aes_generic.ko
> -rw-r--r-- 1 didier didier 11778 2008-02-19 23:31 cbc.ko
> -rw-r--r-- 1 didier didier 25958 2008-02-19 23:31 crypto_blkcipher.ko
> -rw-r--r-- 1 didier didier 16658 2008-02-19 23:31 sha256_generic.ko
> $ ls -la /tmp/init-2.6.24/lib/modules/2.6.24-1-amd64/kernel/crypto/
> total 80
> drwxr-xr-x 2 didier didier  1024 2008-02-19 23:32 .
> drwxr-xr-x 8 didier didier  1024 2008-02-19 23:32 ..
> -rw-r--r-- 1 didier didier 30873 2008-02-19 23:32 aes_generic.ko
> -rw-r--r-- 1 didier didier 15406 2008-02-19 23:32 blkcipher.ko
> -rw-r--r-- 1 didier didier 11712 2008-02-19 23:32 cbc.ko
> -rw-r--r-- 1 didier didier 15584 2008-02-19 23:32 sha256_generic.ko
> --------
>
> So it seems that the same modules are loaded on both initramfs'es..

If cryptsetup fails three times, the boot should continue, initramfs-tools
should panic cause there is no root device setup, and you should be
dropped into a shell. Could you please do that and then check which
modules are loaded by using lsmod (or if not available, "cat
/proc/modules"). Also the same list for the working system after it has
booted would be nice for comparison.

Also, could you provide me with the same directory listings as above but
for the real file system (i.e. /lib/modules/working-version/kernel/crypto
and /lib/modules/broken-version/kernel/crypto).

-- 
David Härdeman