Hide Forgot
Description of problem: sometimes I can see padlock: VIA PadLock not detected. error in dmesg and I am unable to connect to vpn server via openswan. Do not know any further details but I think it can be connected to some aes encryption modules. padlock: VIA PadLock not detected. padlock: VIA PadLock Hash Engine not detected. padlock: VIA PadLock not detected. Version-Release number of selected component (if applicable): Lenovo-T410 kernel-2.6.32-119.el6.i686 NetworkManager-0.8.1-7.el6.i686 NetworkManager-openswan-0.8.0-6.20100411git.el6.i686 How reproducible: from time to time, reboot helps, restarting of NM, ipsec also help sometimes Steps to Reproduce: don't know the exact reproducer.. but some playing with nm-applet (executing it from command line) and service NM restart should do it Actual results: sometimes cannot connect to vpn Expected results: be able to connect every time Additional info:
I can see slightly different message now: padlock: VIA PadLock not detected. padlock: VIA PadLock Hash Engine not detected. padlock: VIA PadLock not detected. alg: No test for cipher_null (cipher_null-generic) alg: No test for ecb(cipher_null) (ecb-cipher_null) alg: No test for digest_null (digest_null-generic) alg: No test for compress_null (compress_null-generic) ^^ unsuccessful timeed out login NET: Unregistered protocol family 15 NET: Registered protocol family 15 padlock: VIA PadLock not detected. padlock: VIA PadLock Hash Engine not detected. padlock: VIA PadLock not detected. alg: No test for authenc(hmac(sha1),cbc(aes)) (authenc(hmac(sha1-generic),cbc(aes-asm))) ^^ few seconds after but successful
could you please provide more information about this bz, like your detailed system information? These messages are generated in kernel, and are not related to Openswan at all. Do you have any issues with your networking interface? I think the right people for this issue may be either kernel or NM guys.
I am not able to reproduce it, and havent got back info from the reporter, so proposing it for 6.2.