Andy, reverting those patches indeed made the messages go away. Perhaps
I have misunderstood something (due to lack of time I didn't study them
in detail) but I though that the first of the two made the initramfs
unpacking asynchronous, so that kernel activity that would previously
have waited for the unpacking to finish was now allowed to proceed in
parallel. And it seems to me that that kernel activity includes calls
to modprobe which are triggered from the kernel code, not from the
initramfs (and/or udev).
I am currently rebuilding with the patches reapplied and the following
local change:
--- ../kmod.c 2010-08-02 00:11:14.000000000 +0200
+++ kernel/kmod.c 2010-10-14 01:21:29.275212001 +0200
@@ -120,6 +120,10 @@
wait ? UMH_WAIT_PROC : UMH_WAIT_EXEC,
NULL, NULL, NULL);
+ printk(KERN_INFO "Request to load module %s, wait=%d, ret=%d\n",
+ module_name, (int) wait, ret);
+ dump_stack();
+
atomic_dec(&kmod_concurrent);
return ret;
}
I hope that does what I want (it is a five minute patch based on quick
googling) and may provide more information about why modprobe is getting
called. By the way, is there any way to do a quick rebuild of the
kernel package when only a couple of files were changed?
To all others, the delay at boot time really doesn't seem to be related
to this error message. I'm sure though that anyone interested can find
out more about what is causing it using bootchart or something similar.
--
Maverick could not load /lib/modules/2.6.35-22-generic/modules.dep
https://bugs.launchpad.net/bugs/642421
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
