Error Inserting /lib/padlock.ko
#1 2008-03-22 19:46:22 Snork Member Registered: 2007-06-28 Posts: 11 Sorta Fixed: Warning: Error inserting padlock_aes .. No such device Since upgrading to 2.6.24.x kernel I've been seeing this on boot with encrypted swap (an old Great Quality PC I bought at Fry's a few years ago:modprobe: Warning: Error inserting padlock_aes (/lib/modules/2.6.24-ARCH/kernel/drivers/crypto/padlock-aes.ko): No such devicemodprobe: Warning: Error inserting padlock_sha (/lib/modules/2.6.24-ARCH/kernel/drivers/crypto/padlock-sha.ko): No such deviceMy /etc/cryptab:swap /dev/sda2 SWAP -c aes-cbc-essiv:sha256 -s 256I had no problems with the 2.6.22 or 2.6.23 kernels.I found a reference on the web to entries in modules.alias, so did some looking: awk '/aes|sha/ && !/pci/' /lib/modules/2.6.23-ARCH/modules.alias alias sha384 sha512alias sha256-generic sha256alias sha1-generic sha1alias sha256-padlock padlock_shaalias sha1-padlock padlock_shaalias aes-padlock padlock_aesalias aes aes_i586 grep padlock /lib/modules/2.6.23-ARCH/modules.aliasalias sha256-padlock padlock_shaalias sha1-padlock padlock_shaalias aes-padlock padlock_aes awk '/aes|sha/ && !/pci/' /lib/modules/2.6.24-ARCH/modules.alias alias sha256 sha256_genericalias sha384 sha512alias aes aes_genericalias sha1 sha1_genericalias sha256-padlock padlock_shaalias sha1-padlock padlock_shaalias sha256 padlock_shaalias sha1 padlock_shaalias aes padlock_aesalias aes aes_i586 grep padlock /lib/modules/2.6.24-ARCH/modules.aliasalias sha256-padlock padlock_shaalias sha1-padlock padlock_shaalias sha256 padlock_shaalias sha1 padlock_shaalias aes padlock_aes# The "fix"cp /lib/modules/2.6.24-ARCH/modules.alias ~/BU.modules.alias.buvi /lib/modules/2.6.24-ARCH/modules.aliasDELETE:alias sha256 padlock_shaalias sha1 padlock_shaCHANGE:al
when load lnet-selftestAgile Board ExportXMLWordPrintable Details Type: Bug Status: Open Priority: Major Resolution: Unresolved Affects Version/s: Lustre 2.3.0 Fix Version/s: None Labels: None Environment: CentOS 6.2 Severity: 3 Rank (Obsolete): 4051 Description After building the master branch (Jul. 4/12), I wanted to run an LNet Selftest. When I enter "modprobe lnet-selftest", there is about a 10 second pause before the load completes. When I look at the logs to see why, I see this: Jul 4 https://bbs.archlinux.org/viewtopic.php?id=45833 13:31:50 localhost kernel: LNet: HW CPU cores: 2, npartitions: 1 Jul 4 13:31:50 localhost kernel: alg: No test for crc32 (crc32-table) Jul 4 13:31:50 localhost kernel: alg: No test for adler32 (adler32-zlib) Jul 4 13:31:50 localhost kernel: alg: No test for crc32 (crc32-pclmul) Jul 4 13:31:54 localhost kernel: padlock: VIA PadLock https://jira.hpdd.intel.com/browse/LU-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel Hash Engine not detected. Jul 4 13:31:54 localhost modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32.lustre23/kernel/drivers/crypto/padlock-sha.ko): No such device Jul 4 13:31:59 localhost kernel: LNet: Added LNI 10.211.55.16@tcp [8/256/0/180] Jul 4 13:31:59 localhost kernel: LNet: Accept secure, port 988 It seems to be tripping up on loading padlock_sha.ko. This bug appears to have been introduced by LU-1201. Activity All Comments History Activity Ascending order - Click to sort in descending order Doug Oucharek created issue - 04/Jul/12 4:39 PM Hide Permalink Alexander Boyko added a comment - 06/Jul/12 2:24 AM - edited >>there is about a 10 second pause before the load completes because libcfs run performance test for supported crypto hash algo. This data should be used for best default algorithm selection for osc-ost interaction. >>padlock: VIA PadLock Hash Engine not detected. The messages come up because you don't have hardware support for encryption. >>Jul 4 13:31:54 localhost modprobe: FATAL: Error inserting
15:39:45 UTC PermalinkRaw Message I too am experiencing it with a fresh install of 10.04 http://kernel-bugs.narkive.com/uDmHHkWR/bug-206129-re-warning-during-boot-warning-error-inserting-padlock-sha-lib-modules-2-6-24-12-generic- LTS:modprobe: FATAL: Error inserting padlock_sha(/lib/modules/2.6.32-23-server/kernel/drivers/crypto/padlock-sha.ko): Nosuch device--Warning http://forums.fedoraforum.org/showthread.php?t=224883 during boot: WARNING: Error inserting padlock_sha (/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such devicehttps://bugs.launchpad.net/bugs/206129You received this bug notification because you are a member of KernelBugs, which is subscribed to linux in ubuntu. lbz error inserting 2010-08-01 18:11:10 UTC PermalinkRaw Message Same problem as #48 on 10.04 LTS server 32-bit.--Warning during boot: WARNING: Error inserting padlock_sha (/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such devicehttps://bugs.launchpad.net/bugs/206129You received this bug notification because you are a member of KernelBugs, which is error inserting /lib/padlock.ko subscribed to linux in ubuntu. Jan Groenewald 2010-10-04 10:40:55 UTC PermalinkRaw Message Confirmed on lucid 64bit server0 root at oystercatcher:/var/log#cat daemon.log|grep shaAug 23 16:52:12 oystercatcher modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-24-server/kernel/drivers/crypto/padlock-sha.ko): No such deviceSep 1 08:34:56 oystercatcher modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-24-server/kernel/drivers/crypto/padlock-sha.ko): No such deviceSep 20 10:29:07 oystercatcher modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-24-server/kernel/drivers/crypto/padlock-sha.ko): No such deviceOct 4 11:57:26 oystercatcher modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-24-server/kernel/drivers/crypto/padlock-sha.ko): No such deviceOct 4 12:33:17 oystercatcher modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-24-server/kernel/drivers/crypto/padlock-sha.ko): No such device0 root at oystercatcher:/var/log#uname -aLinux oystercatcher 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 16:05:42 UTC 2010 x86_64 GNU/Linux0 root at oystercatcher:/var/log#lsb_release -dDescription: Ubuntu 10.04.1 LTS0 root
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Using Fedora FATAL: Error inserting padlock_sha with 2.6.29.5-191 kernel FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 25th June 2009, 06:48 AM jwmueller Offline Registered User Join Date: Sep 2008 Posts: 168 FATAL: Error inserting padlock_sha with 2.6.29.5-191 kernel I updated the latest kernel and other new maintenance tonight and started getting this error at boot... doesn't appear to be hindering anything. My encrypted partitions (luks, ext4) still open and are accessible. modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.29.5-191.fc11.i586/kernel/drivers/crypto/padlock-sha.ko): No such device See similar errors reported on ubuntu forums... with various recommended workarounds... update/add an alias, blacklist a module, fresh install I haven't tried any yet... need the system for work tomorrow so leaving it as-is for now. Comments? Suggestions for F11? Anyone else seeing this? jw jwmueller View Public Profile Find all posts by jwmueller #2 26th June 2009, 04:07 AM jwmueller Offline Registered User Join Date: Sep 2008 Posts: 168 I've blacklisted module padlock-sha and the error message has gone away. jwmueller View Public Profile Find all posts by jwmueller #3 23rd July 2009, 07:31 PM jontis Offline Registered User Join Date: Jun 2009 Posts: 35 Yes. I have the same error. Everything seems to work though... I just exchanged a hard drive and set up new encrypted volumes on it for /home and /swap. / is still on the old CF-card. I thought it was just my own newbie tweaking of crypttab that generated the error but google finds the same problem for other people with recent kernels. I'm running 2.6.29.5-191.fc11.x86_64 As everything still seems to work, my plan is to just hope it goes away with upcoming updates jontis View Public Profile Find all posts by jontis #4 23rd July 2009, 07:45 PM Nokia Offline Registered User Join Date: Aug 2006 Location: /dev/realm/{Abba,Carpenters,...stage} Posts: 3,285 Check for a newer kernel Code: su yum clean all && yum install yum-presto yum-plugi