I think that the delay is also a separate issue, as I saw that even with the mainline kernel which doesn't seem to have this issue.
Assuming that reverting the patches I mentioned above fixes the issue, the next thing would be to find who is calling modprobe at the wrong moment. If anyone knows which kernel function can be called to insert a current stack trace into the kernel log they would save me from searching for it. Presumably inserting a synchronisation point at the right place (which the stack trace should show) would delay the modprobe until modules.dep is available. -- 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
