From: Ben Hutchings <ben@decadent.org.uk>
To: Herbert Xu <herbert@gondor.apana.org.au>, 485070-done@bugs.debian.org
Cc: Ralf Jung <ralfjung-e@gmx.de>,
linux-crypto@vger.kernel.org, katzj@redhat.com
Subject: Re: Bug#485070: cryptsetup: "FATAL" padlock_{aes,sha} error during boot
Date: Sat, 30 Jul 2011 11:15:03 +0200 [thread overview]
Message-ID: <1312017303.2677.7.camel@deadeye> (raw)
In-Reply-To: <20110730061307.GA24394@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Version: 3.7-pre2-1
On Sat, 2011-07-30 at 14:13 +0800, Herbert Xu wrote:
> Ralf Jung <ralfjung-e@gmx.de> 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.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-07-30 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 12:03 cryptsetup: "FATAL" padlock_{aes,sha} error during boot Ralf Jung
2011-07-30 6:13 ` Herbert Xu
2011-07-30 9:15 ` Ben Hutchings [this message]
2011-07-30 11:50 ` [PATCH] crypto: padlock-aes - Make module loading even quieter when hardware is missing Jonathan Nieder
2011-08-03 6:08 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1312017303.2677.7.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=485070-done@bugs.debian.org \
--cc=herbert@gondor.apana.org.au \
--cc=katzj@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=ralfjung-e@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox