public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: davidw@dedasys.com (David N. Welton)
To: William Park <opengeometry@yahoo.ca>
Cc: Daniel Drake <dsd@gentoo.org>,
	linux-kernel@vger.kernel.org, akpm@osdl.org,
	viro@parcelfarce.linux.theplanet.co.uk, helge.hafting@hist.no,
	davidnwelton@gmail.com
Subject: Re: rootdelay
Date: 03 May 2005 10:07:35 +0200	[thread overview]
Message-ID: <874qdkenqw.fsf@dedasys.com> (raw)
In-Reply-To: 20050429183411.GA1998@node1.opengeometry.net

William Park <opengeometry@yahoo.ca> writes:

> On Mon, Apr 25, 2005 at 11:34:23PM +0200, David N. Welton wrote:
> > > > > > http://dedasys.com/freesoftware/patches/blkdev_wakeup.patch
> 
> I patched it to 2.6.11, and it compiles okey.  On boot, it prints
> "Waiting for root device to wake us up."  then it waits for my USB
> key to register.  After USB partition info prints to screen, above
> message is printed "Waiting for root device to wake us up."  again.
> Then, it just hangs forever.

Ok, I updated to 2.6.11.8, and indeed it does have problems that
weren't there before - although in my case it can't mount the root
partition because it's not quite ready yet.  In part, it seems to be
caused by the fact that the USB start up sequence introduces a new
thread that delays the scsi_host_scan by 5 seconds, which is long
enough to cause problems.  I added some code to wait for not only the
disk name to be online, but the partition, but even that doesn't seem
to be quite enough.

Is there anyplace generic that could be hooked that will report when a
device is actually online and ready to run?  Perhaps I was just lucky
in the past with add_disk :-/

Ciao,
-- 
David N. Welton
 - http://www.dedasys.com/davidw/

Apache, Linux, Tcl Consulting
 - http://www.dedasys.com/

  reply	other threads:[~2005-05-03  8:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 18:05 rootdelay David N. Welton
2005-04-01 18:27 ` rootdelay Daniel Drake
2005-04-25  9:45   ` rootdelay David N. Welton
2005-04-25 14:42     ` rootdelay William Park
2005-04-25 21:34       ` rootdelay David N. Welton
2005-04-29 18:34         ` rootdelay William Park
2005-05-03  8:07           ` David N. Welton [this message]
2005-05-03 11:13             ` rootdelay David Welton
2005-04-26 10:11 ` rootdelay Pekka Enberg
2005-04-26 19:54   ` rootdelay David N. Welton
2005-04-27  8:01     ` rootdelay Pekka Enberg

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=874qdkenqw.fsf@dedasys.com \
    --to=davidw@dedasys.com \
    --cc=akpm@osdl.org \
    --cc=davidnwelton@gmail.com \
    --cc=dsd@gentoo.org \
    --cc=helge.hafting@hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opengeometry@yahoo.ca \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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