public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, 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>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: USB storage no-boot regression (bisected)
Date: Wed, 15 Apr 2009 11:49:45 -0400	[thread overview]
Message-ID: <49E60219.9080103@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0904151146210.3072-100000@iolanthe.rowland.org>

Alan Stern wrote:
> On Wed, 15 Apr 2009, Alan Cox wrote:
> 
>> Why should every user suffer a slower boot and a poorer resume time ?
>>
>> Instead make the root fs mounting look like this
>>
>>
>> 	while(my_rootfs_hasnt_appeared_and_i_am_sad()) {
>> 		wait_on(&new_disk_discovery);
>> 	}
>>
>> and poke the queue whenever we add a relevant device.
>>
>> That way if you are booting off an initrd you can finish the SATA probe
>> in parallel to getting userspace ticking over.
>>
>> On what is nowdays essentially a hot plug system it all needs turning
>> this way up - eg RAID volumes should assemble and come online as the
>> drives are discovered not at some fixed point later in userspace.
> 
> Indeed, something like this should also be used for 
> resume-from-hibernation, to wait for the swap device.
..

It just needs a way to set a finite timeout, so that server room
equipment can auto-panic-reboot and try again if a device has died.

-ml

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

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 21:06 USB storage no-boot regression (bisected) 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 [this message]
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=49E60219.9080103@rtr.ca \
    --to=lkml@rtr.ca \
    --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=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