mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: VomLehn <dvomlehn@cisco.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Mark Lord <lkml@rtr.ca>,
	Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>,
	Jeff Garzik <jeff@garzik.org>,
	Linux USB kernel mailing list <linux-usb@vger.kernel.org>,
	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 13:20:52 -0700	[thread overview]
Message-ID: <20090415202052.GA14325@cuplxvomd02.corp.sa.net> (raw)
In-Reply-To: <20090415130614.55b1cb28@infradead.org>

On Wed, Apr 15, 2009 at 01:06:14PM -0700, Arjan van de Ven wrote:
> For other pieces it's hard. Non-enumeratable busses just suck;
> at some point all you can do is just wait (which we have already 
> available today for anyone to do). I realize people don't want to
> just wait 4 seconds (the people who first objected to boot time
> improvements then suddenly care about boot time ;-)...

We can do better than just waiting. What we want to do is to wait
until a suitable device becomes available. For USB console, the patch
I submitted yesterday waits for the first console to be registered.
That might not be quite right, but it's a lot better than no console
at all. For network devices, we have to wait for a specific device and
I haven't had a chance to look at this. For both types of devices, we
can timeout after a reasonable interval, for some definition of reasonable.

Waiting for a suitable device preserves fast boot times, timing out allows
the system to come up enough to try to diagnose the problem.

David VomLehn

      reply	other threads:[~2009-04-15 20:21 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
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 [this message]

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=20090415202052.GA14325@cuplxvomd02.corp.sa.net \
    --to=dvomlehn@cisco.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=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

all inboxes | Powered by JetHome®