Bug 549351

Summary: modprobe: FATAL: Error inserting padlock_sha
Product: [openSUSE] openSUSE 11.2 Reporter: Harald Koenig <koenig>
Component: KernelAssignee: Jeff Mahoney <jeffm>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Minor    
Priority: P4 - Low CC: douglagm, mmarek, t.rother
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Harald Koenig 2009-10-22 20:01:27 UTC 
after update from 11.1 to 11.2 RC2 using a encrypted /home/ parition I get the following FATAL error msg.  from boot.msg:

Loading console font lat9w-16.psfu  -m trivial G0:loadable
doneLoading keymap assuming iso-8859-15 euro
Loading /usr/share/kbd/keymaps/i386/qwerty/us.map.gz
doneStart Unicode mode
donePlease enter passphrase for cr_home: Please enter passphrase for cr_home: Please enter passphrase for cr_home: Please enter passphrase for cr_home: modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.31.3-1-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device

Please enter passphrase for cr_home: cr_home...done
Comment 1 Ren Sheng Zhu 2009-10-23 06:50:20 UTC 
It seems to be related to kernel, so I assign it to kernel-maintainers@forge.provo.novell.com.
Comment 2 Harald Koenig 2009-11-15 17:03:32 UTC 
still happens with 11.2 (2.6.31.5-0.1-default)
Comment 3 Jeff Mahoney 2009-12-02 22:00:05 UTC 
It's a fatal error for modprobe but not for the system. It just means that you don't have the requisite hardware for that driver. Since there is currently no automated way to autoload those drivers based on the hardware profile, it attempts to load it for all hardware.
Comment 4 Jeff Mahoney 2009-12-02 23:15:34 UTC 
What's happening is that when the dm-crypt module requests a sha1 instance, the crypto API initializes it. It then tries to load any drivers that might be better suited but depend on the generic implementation as a fallback. It uses request_module to do that, which calls modprobe -q <modulename>. modprobe -q views -ENOENT as ignorable but not -ENODEV, so it issues the fatal error.

Potential solutions to this include making request_module call modprobe -qa instead or creating a new request_modules that calls it with -qa.
Comment 5 Gregg Douglas 2010-02-18 18:53:02 UTC 
Hi,

Is there are fix to this ? I installed the novell-ipsec-tools and novell-nortelplugins. when I try to connect to the VPN via the Network manager I get the following in /var/log/message : 

modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.31.12-0.1-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device
kernel: [   84.584451] padlock: VIA PadLock Hash Engine not detected.
modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.31.12-0.1-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device
.
.
.
kernel: [   86.050676] nvpn[3252]: segfault at 18 ip 000000000040860a sp 00007fffd0874c10 error 4 in nvpn[400000+10000]

I tried adding in /lib/modules/2.6.31.12-0.1-desktop/modules.alias:
alias sha256_generic padlock_sha
and 
alias padlock_sha sha256_generic

Neither worked

Regards
Gregg
Comment 6 Jeff Mahoney 2010-02-18 19:47:25 UTC 
Gregg, please file your report as a separate bug against nvpn. This issue, despite the "FATAL", is not actually fatal and will not cause application issues.
Comment 7 Jeff Mahoney 2011-01-24 21:29:42 UTC 
This is duplicate of bnc#467014.

*** This bug has been marked as a duplicate of bug 467014 ***