-------- Forwarded Message -------- From: Ben Hutchings <ben@decadent.org.uk> To: Ralf Jung <ralfjung-e@gmx.de> Subject: Re: cryptsetup: strange padlock_aes error during boot Date: Sat, 30 Jul 2011 12:52:11 +0200 On Sat, 2011-07-30 at 12:29 +0200, Ralf Jung wrote: > Hi Ben, > > thanks a lot for dealing with this issue so quickly. I am however slightly > confused, since according to > http://packages.qa.debian.org/m/module-init-tools.html > the current version of module-init-tools is 3.16, and it is also the one I > have installed here. I read once that bugs are marked as fixed in the > bugtracker when the fix hits the package archives. Does your comment mean it > has been fixed long ago, or is there another version scheme? > > Sorry if this is a stupid question, I'm new to Debian bug management. Not a stupid question. 'aes' is an alias for multiple modules that implement AES: $ grep '^alias aes ' /lib/modules/3.0.0-1-amd64/modules.alias alias aes aes_x86_64 alias aes aesni_intel alias aes aes_generic alias aes padlock_aes modprobe attempts to insert all of these modules, and some of them will fail because they require specific processors. But it shouldn't report an error unless *all* of them fail. This was the original bug and is fixed. But for some reason there is not a single alias for the modules that implement SHA-1: $ grep '^alias sha1 ' /lib/modules/3.0.0-1-amd64/modules.alias alias sha1 sha1_generic $ grep '^alias sha1-all ' /lib/modules/3.0.0-1-amd64/modules.alias alias sha1-all padlock_sha So this is a different bug. I've unmerged and reopened #568008 which refers to padlock_sha. Ben.
Attachment:
signature.asc
Description: This is a digitally signed message part