Date: Sun, 29 Mar 2009 09:11:48 -0700
From: Arjan van de Ven <arjan@infradead.org>
To: Thomas =?UTF-8?B?QsOkY2hsZXI=?= <thomas@archlinux.org>
Cc: linux-kernel@vger.kernel.org,
       Thomas =?UTF-8?B?QsOkY2hsZXI=?= <thomas@archlinux.org>
Subject: Re: fastboot/async and initramfs: How am I supposed to know when
 devices are finished initializing?
Message-ID: <20090329091148.16a618bf@infradead.org>
In-Reply-To: <49CF9BA1.5030400@archlinux.org>
References: <49CF9BA1.5030400@archlinux.org>
Organization: Intel
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1332
Lines: 34

On Sun, 29 Mar 2009 18:02:41 +0200
Thomas Bächler <thomas@archlinux.org> wrote:

> Okay, I have this problem in 2.6.29 with the "fastboot" option and in 
> today's linux-2.6.git.
> 
> In initramfs, we run the following commands:
>      /sbin/udevd --daemon
>      /sbin/udevadm trigger
>      /sbin/udevadm settle
> Among other things, this loads the ata_piix on my machine. On older 
> kernels I could assume that after these commands, /dev/sda* existed

not if you have CONFIG_SCSI_SCAN_ASYNC set though..

> and I could immediately access them (in my case, I run cryptsetup on 
> /dev/sda6). But now, the devices don't exist here, but are only
> created a second or so later. As a result, the initramfs script has
> already bailed out as it couldn't find /dev/sda6 and assumed that the
> hard drive didn't exist.

the CONFIG_SCSI_WAIT_SCAN method (basically loading that module to wait
for the scans to finish) will work for you......


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/