mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Mark Lord <lkml@rtr.ca>
Cc: Greg KH <greg@kroah.com>, Jeff Garzik <jeff@garzik.org>,
	Linux USB kernel mailing list <linux-usb@vger.kernel.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: USB storage no-boot regression (bisected)
Date: Wed, 15 Apr 2009 12:58:13 -0700	[thread overview]
Message-ID: <20090415125813.34c9a151@infradead.org> (raw)
In-Reply-To: <49E5FF48.3030809@rtr.ca>

On Wed, 15 Apr 2009 11:37:44 -0400
Mark Lord <lkml@rtr.ca> wrote:

> Arjan van de Ven wrote:
> > On Wed, 15 Apr 2009 10:25:05 -0400
> > Mark Lord <lkml@rtr.ca> 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.
> > 
> > seconds!!!!!
> > The whole kernel boots in half a second!
> ..
> 
> Oh, absolutely I agree.
> 
> That's why I'm not suggesting a DELAY
> but rather a TIMEOUT (where it keeps trying up until the timeout).

This exists today. It's just not something Jeff chose to use ;)
(because he didn't need to)

> 
> For desktop, it should really just wait forever,
> but I can understand situations (server room)
> where that would be a Really Bad Idea.

it's called rootwait and such :)


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-04-15 19:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 21:06 Jeff Garzik
2009-04-15  1:38 ` Arjan van de Ven
2009-04-15  2:30   ` Jeff Garzik
2009-04-15  2:44     ` Arjan van de Ven
2009-04-15  2:48       ` Jeff Garzik
2009-04-15  3:09         ` Arjan van de Ven
2009-04-15  8:40     ` Alan Cox
2009-04-15  1:49 ` Greg KH
2009-04-15  2:35   ` Jeff Garzik
2009-04-15  2:46     ` Arjan van de Ven
2009-04-15  5:09     ` Greg KH
2009-04-15 13:46       ` Jeff Garzik
2009-04-15 14:25       ` Mark Lord
2009-04-15 14:30         ` Arjan van de Ven
2009-04-15 15:37           ` Mark Lord
2009-04-15 19:58             ` Arjan van de Ven [this message]
2009-04-15 21:55               ` Mark Lord
2009-04-16  1:32                 ` Arjan van de Ven
2009-04-16  2:14                   ` Mark Lord
2009-04-16  2:54                     ` Greg KH
2009-04-16 10:51                       ` Alan Cox
2009-04-16 13:34                         ` Arjan van de Ven
2009-04-16 13:49                           ` Mark Lord
2009-04-16  2:17                   ` Hal Murray
2009-04-16  3:42                   ` Jeff Garzik
2009-04-15 15:01         ` Alan Cox
2009-04-15 15:47           ` Alan Stern
2009-04-15 15:49             ` Mark Lord
2009-04-15 17:06               ` VomLehn
2009-04-15 17:32                 ` Alan Cox
2009-04-15 20:06                   ` Arjan van de Ven
2009-04-15 20:20                     ` VomLehn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090415125813.34c9a151@infradead.org \
    --to=arjan@infradead.org \
    --cc=greg@kroah.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome