modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.38-9-generic/kernel/drivers/crypto/padlock-sha.ko): No such device

I think this is meant to be looked at as a kernel bug, not a cryptsetup bug; reassigning to the kernel, please reassign back if I've misunderstood.

Yes this is kernel bug.
Kernel tries to autoload drivers for crypt accelerators (here VIA Padlock) but such device is not avalible on that system.
The message is benign, sw implementation is used instead.

I'm also affected by the bug, I'm using the same encrypted home directory since at least 10.04.

Here are a few lines from syslog that may be relevant (as far as I understand what's happening) :
May 9 21:01:31 schambrin-laptop kernel: [ 16.555026] Intel AES-NI instructions are not detected.
May 9 21:01:31 schambrin-laptop kernel: [ 16.565269] padlock_aes: VIA PadLock not detected.
May 9 21:01:31 schambrin-laptop kernel: [ 16.584529] padlock_sha: VIA PadLock Hash Engine not detected.
May 9 21:01:31 schambrin-laptop kernel: [ 16.604880] device-mapper: table: 252:0: crypt: Device lookup failed
May 9 21:01:31 schambrin-laptop kernel: [ 16.605440] device-mapper: ioctl: error adding target to table
May 9 21:01:31 schambrin-laptop kernel: [ 16.633795] device-mapper: ioctl: Unable to rename non-existent device, cryptswap1_unformatted to cryptswap1
May 9 21:01:31 schambrin-laptop kernel: [ 20.568130] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
May 9 21:01:31 schambrin-laptop kernel: [ 32.621565] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)

and later many of these :
May 9 21:02:05 schambrin-laptop kernel: [ 66.786117] Valid eCryptfs headers not found in file header region or xattr region
May 9 21:02:05 schambrin-laptop kernel: [ 66.786122] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO

Stepho.

I have this problem too. Is blacklisting the module a bad idea?
Thanks

Same message here, system doesn't boot anymore. This is f***ing serious!

System:

11.04 64 bit, crypted home directory.

Ok, forget my comment for this issue.
After leaving the system alone for a couple of minutes it had been started and it seems that the padlock issue wasn't the cause because after looking at syslog I saw that this message occurs everytime when booting but doesn't cause a delay.
It rather seems to be a problem with ntp synching:

...
Jun 12 23:20:24 pc NetworkManager[987]: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 12 23:20:31 pc kernel: [ 198.670027] eth0: no IPv6 routers present
Jun 12 23:20:32 pc ntpdate[1254]: adjust time server 91.189.94.4 offset -0.406334 sec
Jun 12 23:25:30 pc kernel: [ 497.243444] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jun 12 23:25:30 pc kernel: [ 497.244409] SGI XFS Quota Management subsystem
...

I'm really surprised that time server adjusting interrupts the whole boot process, but that's another issue...

This bug is missing log files that will aid in dianosing the problem. From a terminal window please run:

apport-collect 779912

and then change the status of the bug back to 'New'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

 i ran ubuntustudio 11.04 on recovery mode after failing to boot successfully on normal mode following the addition of 2 ide hard disks to the system.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Same issue for me. I am using 2.6.38-11-generic and /home and swap encryption.

I see
modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.38-11-generic/kernel/drivers/crypto/padlock-sha.ko): No such device
during boot up.

I just updated yesterday and then added "hash=ripemd160,size=256" to /etc/crypttab:

# cat /etc/crypttab
# <target name> <source device> <key file> <options>
cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256,hash=ripemd160,size=256
#EOF

I did it because in output of apt-get i notice, that hash and size should be specified for cryptsetup to work properly.
It seems that swap is encrypted and works properly:

# cryptsetup status cryptswap1
/dev/mapper/cryptswap1 is active and is in use.
  type: PLAIN
  cipher: aes-cbc-essiv:sha256
  keysize: 256 bits
  device: /dev/sda3
  offset: 0 sectors
  size: 6297480 sectors
  mode: read/write

# free -m
             total used free shared buffers cached
Mem: 2004 1886 117 0 78 905
-/+ buffers/cache: 902 1101
Swap: 3074 51 3023

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

also having this problem (10.04.4 LTS). Ready to give further information if necessary.