El 19/03/13 18:48, Jan Engelhardt escribió:

mv modprobe modprobe.bin cat >modprobe <<-EOF #!/bin/sh echo "Args: $@" >>/tmp/modprobe.log.$$ ps aufwwx >>/tmp/modprobe.log.$$ exec modprobe.bin "$@" EOF

yeah, that hack might work too :-) I was looking for a less hackish way though .. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 19/03/13 23:15, Carlos E. R. escribió:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Tuesday, 2013-03-19 at 18:06 -0300, Cristian Rodríguez wrote:

...

In about 3 machines I have the following annoying log message:

modprobe[1062]: FATAL: Error inserting padlock_sha (/lib/modules/3.9.0-rc3-1-desktop/kernel/drivers/crypto/padlock-sha.ko): No such device

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) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----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-----

On Wed, Mar 20, 2013 at 6:14 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Wednesday, 2013-03-20 at 07:48 +0400, Andrey Borzenkov wrote:

...

Do you have encrypted filesystems?

Yes, I do.

loading of module is triggered by cryptsetup. It does not load it itself, but may be internally kernel probes for all crypto providers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2013-03-20 at 14:38 -0300, Cristian Rodríguez wrote:

El 20/03/13 11:32, Andrey Borzenkov escribió:

...

...

Yes, I do.

loading of module is triggered by cryptsetup. It does not load it itself, but may be internally kernel probes for all crypto providers.

Yes, but this is not an internal probe and none of the machines where is see this msg has encrypted filesystems.

Interesting. So you and I get the message for different reasons. Or... is there a reason the kernel or whatever probes for encrypted filesystems when there is none? - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlFKPJEACgkQtTMYHG2NR9UQWQCeJJaDJooZ23F37b82YwlwE8Kv 3u0Ani2jI2aQkrjkaRSzn7K0a2px51Ze =4AFn -----END PGP SIGNATURE-----

El 20/03/13 20:44, Yamaban escribió:

On my old Evergreen 11.2 box I do not see the error in my logs (neither boot.msg nor allmessages) and I have changed my /etc/sysconfig/kernel to reflect my hardware (INITRD_MODULES, MODULES_LOADED_ON_BOOT) and rebuild the initrd-file, that may be a point to look for.

Also the files in: /etc/modprobe.d/* esp. /etc/modprobe.d/99-local.conf

are worth a look, as everything I did not need, I've disabled. Most of it via "alias xxxxx off" or "install xxxx /bin/true" on 99-local.conf.

No, it is not a customization. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 26/03/13 23:25, Jan Engelhardt escribió:

And now check with

udevadm info --export-db | grep x86cpu:

Got 00AA in it?

nope. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, 27 Mar 2013 03:33, Carlos E. R. wrote:

On Wednesday, 2013-03-27 at 03:25 +0100, Jan Engelhardt wrote:

...

On Wednesday 2013-03-20 03:29, Cristian Rodríguez wrote:

...

...

"something" is doing probes the wrong way from the wrong reason. that's all.

Let's see..

$ modinfo padlock-sha filename: /lib/modules/3.7.10-jng11-desktop/kernel/drivers/crypto/padlock-sha.ko [...] alias: x86cpu:vendor:*:family:*:model:*:feature:*00AA*

And now check with

udevadm info --export-db | grep x86cpu:

Got 00AA in it?

Telcontar:~ # modinfo padlock-sha filename: /lib/modules/3.1.10-1.19-desktop/kernel/drivers/crypto/padlock-sha.ko alias: sha256-padlock alias: sha1-padlock alias: sha256-all alias: sha1-all author: Michal Ludvig license: GPL description: VIA PadLock SHA1/SHA256 algorithms support. srcversion: DFE445F053B7F98B381D760 depends: vermagic: 3.1.10-1.19-desktop SMP preempt mod_unload modversions Telcontar:~ # udevadm info --export-db | grep x86cpu Telcontar:~ #

Is that what you expect?

Interesting is, that in the Evergreen 11.2 kernel, the "depends" field is filled: filename: /lib/modules/2.6.31.14-0.8-desktop/kernel/drivers/crypto/padlock-sha.ko .... srcversion: CB8D3DBB1F83B3770836EA3 depends: crypto_algapi vermagic: 2.6.31.14-0.8-desktop SMP preempt mod_unload modversions Can't say when (time/kernel-version) this changed. - Yamaban.

On Wed, Mar 27, 2013 at 05:14:43AM +0100, Jan Engelhardt wrote:

Well, the depends line is not all that important.

(As for SUSE configs, crypto_algapi likely moved from =m to =y.)

Yes, it looks like this happened between 11.2 and 11.3: commit 370c3abfa759e7a5c216c906f21cd6f818eb3055 Author: Jiri Kosina Date: Tue Jan 19 14:22:14 2010 +0100 - Update config files: set CONFIG_CRYPTO_HMAC=y to avoid regression from SLE11 (bnc#571501). Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org