Re: cold plugging

[Olivier Blin <oblin@mandriva.com>]

Kay Sievers <kay.sievers@vrfy.org> writes:

>> >6) such late uevents reach udevd after the loop ends, and then it may be 
>> >too late (but it is OK for me to ignore this for my scanner).
>> 
>> I had a similar problem with a USB Flash drive that had a delay in the 
>> driver for it to "warm up". I just had a larger delay (and less cycles) in 
>> my queue polling script and it works OK.
>
> Sure, this can happen with usb_storage. Secondary events, that arrive
> after a module has scheduled device creation and return immediately,
> have never been handled and there is no sane way to do it for udev. 
>
> I'm sure we don't want to introduce another round of sleep 1 to the
> device management, like the nightmare we had in the past. The right
> way to solve that - if you really depend on these devices at all - is
> to have certain checkpoint during boot that have the dependency on
> these devices recorded.

We've added some workarounds in Mandriva's rc.sysinit to wait for
usb/firewire devices if needed:

# wait for usb and firewire storage scanning processes to finish
[ -n "$needusbstorage" ] && while ps -eocomm | grep -q usb-stor-scan; do sleep 1; done
[ -n "$needfirewirestorage" ] && while ps -eocomm | grep -q kfwrescan; do sleep 1; done

-- 
Olivier Blin - Mandriva



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel