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 cryptsetup: strange padlock_aes error during boot
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: cryptsetup
Version: 2:1.0.6-1
Severity: normal
While my system is booting up, I get this message:
Starting early crypto disks...swap1 (starting).
[ 32.073333] padlock: VIA PadLock not detected.
modprobe: WARNING: Error inserting padlock_aes
(/lib/modules/2.6.25-2-686/kernel/drivers/crypto/padlock-aes.ko): No such device
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.24-4 The Linux Kernel Device Mapper use
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.24-4 The Linux Kernel Device Mapper use
ii libpopt0 1.10-3 lib for parsing cmdline parameters
ii libuuid1 1.40.8-2 universally unique id library
cryptsetup recommends no packages.
-- no debconf information
--- 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 ---
