[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#568008: marked as done (linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device)

Your message dated Sat, 24 Apr 2021 04:38:39 -0700 (PDT)
with message-id <6084033f.1c69fb81.cf57.315f@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #568008,
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 owner@bugs.debian.org
immediately.)


-- 
568008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568008
Debian Bug Tracking System
Contact owner@bugs.debian.org 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 --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: