|| ||Arjan van de Ven <arjan-wEGCiKHe2LqWVfeAwA7xHQ-AT-public.gmane.org> |
|| ||Mark Lord <lkml-gsilrlXbHYg-AT-public.gmane.org> |
|| ||Re: USB storage no-boot regression (bisected) |
|| ||Wed, 15 Apr 2009 07:30:01 -0700|
|| ||Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w-AT-public.gmane.org>, Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A-AT-public.gmane.org>,
Linux USB kernel mailing list <linux-usb-u79uwXL29TY76Z2rM5mHXA-AT-public.gmane.org>,
Alan Stern <stern-nwvwT67g6+6dFdvTe/nMLpVzexx5G7lz-AT-public.gmane.org>,
"Rafael J. Wysocki" <rjw-KKrjLPT3xs0-AT-public.gmane.org>|
|| ||Article, Thread
On Wed, 15 Apr 2009 10:25:05 -0400
Mark Lord <lkml-gsilrlXbHYg@public.gmane.org> wrote:
> Greg KH wrote:
> > ..
> > The issue is that you were just lucky that your machine worked
> > properly previously. My boxes with the same type of setup didn't,
> > so I quickly realized what the root delay boot option was for. You
> > need to just do the same thing here, there's nothing else we can do.
> Bad excuse.
> SATA drives also take variable amounts of time to "show up" at boot.
> Perhaps Jeff should customize libata for your and Arjan's exact
> setups, just to help with understanding the point here. :)
the difference is that with sata you know when you are done and have all
possible drives. No so much much with USB. So with SATA we can, and do,
wait for the scan to complete at the right point in the boot.
> The speed ups are fine (and welcome), but we really now need
> Arjan to follow-up with a patch to have the kernel *by default*
> wait a little longer for the rootfs to show up.
> Not forever, just a few seconds to compensate for the regression.
The whole kernel boots in half a second!
for this case, which is unfortunately not detectable by the kernel,
there is the rootwait option.
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)