By adding rootdelay=20 on the command line, the problem does not show.
It is not very satisfying though, since the casual user will not dive
into the initrd to read the script init and see that you can set this
variable on the command line.

Is there no event that can be caught once all devices have been
registered ?






--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1299259707.6353.7.camel@moraes.localdomain">http://lists.debian.org/1299259707.6353.7.camel@moraes.localdomain

On Fri, 2011-03-04 at 18:28 +0100, Pascal BERNARD wrote:
> By adding rootdelay=20 on the command line, the problem does not show.
> It is not very satisfying though, since the casual user will not dive
> into the initrd to read the script init and see that you can set this
> variable on the command line.
>
> Is there no event that can be caught once all devices have been
> registered ?

No, in general there is no such thing as 'once all devices have been
registered'. For example USB enumeration is totally asynchronous.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.