On Wed, Oct 26, 2005 at 09:37:54AM +0200, Marco d'Itri wrote: > On Oct 26, Horms <[EMAIL PROTECTED]> wrote: > > > Just to clarify, udevd gets a bunch of events and tries to > > serialise them into modprobe calls, right? Do you think there > There is no serialization, only some throttling (IIRC it tries to run up > to 10 child processes in parallel).
Ok, but it runs modprobe, not ismod, right? > > is any chance it might be calling modprobe out of order > > for some reason. > The point is the dependencies are handled by modprobe, so the order in > which udevd loads the modules at the top of the dependency tree is not > relevant. True. > As Rusty suggested I wrapped /sbin/modprobe in a logger script, but so > far I have not been able to reproduce the bug again (which may or may > not be related, I need a few more reboots). Thanks. I'm not having any luck reproducing the problem at all. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
