Comment 5 for bug 66423

I can still confirm this on Hardy:
Apr 23 00:57:08 amalthea NetworkManager: <info> Supplicant state changed: 1
Apr 23 00:57:32 amalthea modprobe: WARNING: Not loading blacklisted module ipv6
Apr 23 00:57:33 amalthea last message repeated 7 times
Apr 23 00:59:01 amalthea last message repeated 6 times
Apr 23 00:59:18 amalthea last message repeated 47 times
Apr 23 01:01:28 amalthea NetworkManager: <info> Supplicant state changed: 0
Apr 23 01:01:29 amalthea NetworkManager: <info> Supplicant state changed: 1
Apr 23 01:03:46 amalthea NetworkManager: <info> Supplicant state changed: 0
Apr 23 01:03:50 amalthea NetworkManager: <info> Supplicant state changed: 1
Apr 23 01:04:26 amalthea modprobe: WARNING: Not loading blacklisted module ipv6
Apr 23 01:04:28 amalthea last message repeated 12 times
Apr 23 01:07:25 amalthea modprobe: WARNING: Not loading blacklisted module ipv6
Apr 23 01:07:25 amalthea last message repeated 2 times

In fact, it's even worse than in the original bug, since these are multiple calls to modprobe *per second*.
I don't know if these calls have anything to do with the NetworkManager messages (another kind of syslog spam).

I've attached the output of one of the "ps xaufwwww" in Roland's script above.
It doesn't tell too much, though, because modprobe is called from [khelper] in [kthreadd], so I suppose it's the kernel autoloader. (?)

PS: Does the performance and syslog spam effect of 248 calls to modprobe in two minutes ...
Apr 23 01:24:34 amalthea modprobe: WARNING: Not loading blacklisted module ipv6
Apr 23 01:24:56 amalthea last message repeated 184 times
Apr 23 01:26:05 amalthea last message repeated 52 times
Apr 23 01:26:37 amalthea last message repeated 11 times
... qualify this bug to be a little more urgent.