On Thu, 26 Mar 2009, Alan Stern wrote: > > > Speeding up initialization of USB devices appears to have created race > > > conditions for consoles and auto-configured network devices. > What you really need is a way to wait until the devices have been > registered. How about polling in a loop before running the initramsfs > setup routine? Sorry, I missed the part about this being needed for a kernel-command-line driven IP autoconfig. I'm not so sure that adding a call to async_synchronize_full() will help. The asynchronous USB probe routines will return before the root hub's children have been detected, because detection occurs in a separate thread (khubd). In fact, the meaning of the ip= parameter isn't really clear. To what network interface is it supposed to apply? The first one? But what if the first one hasn't been detected yet when the autoconfig code runs? Maybe the ip_auto_config stuff should be changed so that it is invoked when the first (non-loopback) interface is registered, instead of at a predefined point during the system startup. At any rate this doesn't seem to be a USB problem, or at least, not a bug in the USB stack. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
