-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
В Wed, 20 Mar 2013 04:32:53 +0100 (CET)
"Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID:
On Tuesday, 2013-03-19 at 23:29 -0300, Cristian Rodríguez wrote:
El 19/03/13 23:15, Carlos E. R. escribió:
I have been seeing that message for years in my machines (or very similar). However, the message went to /var/log/boot.msg, where it did not bother me. Now it goes to messages.log - that's your fault for implementing systemd! :-P
Heh, no . do not shoot the messenger :)
:-)
"something" is doing probes the wrong way from the wrong reason. that's all.
That message only hints that it is not the kernel, udev or systemd trying to do something stupid (none of them fork modprobe)
I know.
But it is been happening for years, I noticed that message long ago. Have a look:
12.1 SystemV:
<5>[ 67.107370] padlock_sha: VIA PadLock Hash Engine not detected.
openSUSE 11.2 (x86_64):
<5>[ 40.091166] padlock: VIA PadLock not detected. ... <5>[ 40.109950] padlock: VIA PadLock Hash Engine not detected.
Telcontar:~ # zgrep -i padlock /other/Elessar/var/log/*bz2 /other/Elessar/var/log/messages-20100621.bz2:May 29 12:49:21 Elessar kernel: [ 4587.702886] padlock: VIA PadLock not detected. /other/Elessar/var/log/messages-20100621.bz2:May 29 12:49:21 Elessar kernel: [ 4587.732074] padlock: VIA PadLock Hash Engine not detected. /other/Elessar/var/log/messages-20100621.bz2:May 29 12:49:21 Elessar modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.31.12-0.2-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device
I see that I mentioned it on some bugzilla years ago, too.
Do you have encrypted filesystems? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlFJMYUACgkQR6LMutpd94wlmACeOlT7vb3uyZfWAkB8z7SUIsqy 4ZwAnjRBrqc6p7kChC4s2/NYLDa+Tkz3 =6cAt -----END PGP SIGNATURE-----