[Bug 642421] Re: Maverick could not load /lib/modules/2.6.35-22-generic/modules.dep

[Andy Whitcroft]

@Michael -- nominally the patches you are suspicious of would make it
more likely the files are present than without them as the unpacking
starts sooner.  I could see how the error might be triggered if the
probe occurs in parallel with the unpack, however before the patches the
modprobe would have failed as modprobe itself would also not be present
before the patches; though it might be quieter.  We would then expect
udev to sort out the situation when it does its coldplug phase.  But I
would be interested in the results of your testing, please report back
your testing with those patches reverted.  If they do affect the result
I can help to add the syncronisation to the probe routine as the next
step.

Overall I am pretty cirtain that this error is purely cosmetic in nature
and would encourage those who have other issues (after this error)
should also file separate bugs for those issues, its unlikely this error
is the cause of them.

While it is undesirable that this error is emitted so prominantly during
boot on any system, even had this error been on the release teams radar,
it is unlikely it would have been a release blocker as it does not seem
to affect functionality, nor does it affect a large percentage of the
install base.  All of the release team and the development teams run the
development release for the entire time it is being created, and QA test
the release on the hardware they have available, and personally I have
boot tested the final release code on all the H/W I have and none of it
triggers this error.  Every release has some bugs that is unavoidable,
and why we also produce stable release updates to address them.

-- 
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 Kernel
Bugs, which is subscribed to linux in ubuntu.