Your message dated Sat, 30 Jul 2011 11:15:03 +0200
with message-id <1312017303.2677.7.camel@deadeye>
and subject line Re: Bug#485070: cryptsetup: "FATAL" padlock_{aes,sha} error
during boot
has caused the Debian Bug report #485070,
regarding linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such
device
to be marked as done.This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 485070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485070 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: linux-image-2.6.32-trunk-amd64 Version: 2.6.32-5 Every time I boot - and I'm using crypto file systems - I get the series of messages (copied from bootlog): Starting early crypto disks...sda2_crypt (starting)... Unlocking the disk /dev/sda2 (sda2_crypt) Enter passphrase: modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-trunk-amd64/kernel/drivers/crypto/padlock-sha.ko): No such device Key slot 0 unlocked. Any ideas what this FATAL error is about and whether it is a problem? Julian
--- End Message ---
--- Begin Message ---Version: 3.7-pre2-1 On Sat, 2011-07-30 at 14:13 +0800, Herbert Xu wrote: > Ralf Jung <[email protected]> wrote: > > Hi, > > > > as per request of Jonathan at http://bugs.debian.org/cgi- > > bin/bugreport.cgi?bug=485070, I am reporting the mentioned bug to this list > > as > > well: > > > > With current Debian testing (Kernel 2.6.39), I am getting this error on > > each > > boot: > > FATAL: Error inserting padlock_sha (/lib/modules/2.6.39-2- > > amd64/kernel/drivers/crypto/padlock-sha.ko): No such device > > I understand it is harmless, but it should still be fixed since it > > irritates > > users suggesting something is seriously going wrong. > > That message comes from user-space and needs to be fixed there. Right, it comes from modprobe. Fixed in module-init-tools version 3.5, commit cdafffbadc5831ad56fe00ecd420ca9c36e9474f ("don't warn noisely if loading multiple module aliases"). Ben.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
