padlock-sha.ko fails to load since 2.6.28-2-generic

[Ambricka]

Description: Ubuntu jaunty (development branch)
Release: 9.04
Linux nattbrygga 2.6.28-2-generic #3-Ubuntu SMP Thu Dec 4 21:49:06 UTC 2008 i686 GNU/Linux

With the new kernel via padlock-sha fails to load:

petter@nattbrygga:~$ sudo modprobe -v padlock-sha
insmod /lib/modules/2.6.28-2-generic/kernel/drivers/crypto/padlock-sha.ko

It hangs, and does just nothing. Hitting ctrl-c gives some interesting information.

[Marco Chiappero (mchiappero)]

I can confirm this.
Well, I haven't tried Jaunty yet but using the last vanilla I'm experiencing the same issue (and same syslog output).
It should be notified upstream.

[Taru Karttunen (taruti)]

Fixed in upstream:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a760a6656e6f00bb0144a42a048cf0266646e22c

[Justin Chudgar (justinzane)]

I can confirm with 2.6.28-12-generic. Same warning as previously attached. Apparently the upstream fix has not been added to recent kernel builds.

[simovaris (sercet)]

This bug also present in karmic with latest updates.

Occassionally, rather sendomly, it boots normally though and prompts for cryptdisks' passwords and other times it gives original bug reporter's error and it does not prompt for cryptdisks' passwords these times.

[Jeremy Foshee (jeremyfoshee)]

Hi Ambricka,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 305934

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[J.D. (fungs)]

I just want to add that I also experienced this with a recent backports kernel on Debian Lenny (). It seems like the padlock-sha modules loads the kernel generic sha module as fallback. I had the following aliases set:

alias aes padlock_aes
alias sha1 padlock_sha

Removing the sha1->padlock_sha alias made the module load fine at boot time and /proc/crypto looks nice without failing selftests. This seems to be a change from earlier kernel versions, where this alias was recommended to be set by some tutorials.

[J.D. (fungs)]

kernel version = 2.6.32-bpo.5-686