usb drive not recognized, maybe timing?

[Eugene Crosser]

Kay Sievers wrote:

>>I have hal 5.0.4 running (with --retain-privileges) on kernel 2.6.13,
>>with udev 0.64. When a usb drive is inserted, hald recognizes is as
>>"usb_noserial", not as a block device with a filesystem.  I suspect that
>>it has something to do with "Cannot open" messages in the HAL debug
>>output (attached).  If I start hald when the USB drive is already
>>unserted, it *is* recognized and appears in `lshal' output.
>>
>>Now, the interesting part.  When I manually cat the sys files that hald
>>could not open, a few seconds later, most of them are in place and
>>perfectly readable.  On the other hand, if I watch dmesg, I can see that
>>there is a several seconds' pause between "usb-storage: device found at
>>20" and final "usb-storage: device scan complete" message.  Maybe hald
>>is trying to open sysfs files while the kernel did not create them yet?
> 
> 
> That should be covered by udev managing the whole hotplug process.
> Does:
>   cat /proc/sys/kernel/hotplug
> print /sbin/udevsend?

Nope, not really.  If I put /sbin/udevsend into
/proc/sys/kernel/hotplug, USB insertion information never gets to
messagebus at all, even as "usb_noserial".  This is hald output that I get:

11:14:57.248 [I] osspec.c:243: total_read=178
buf='add@/devices/pci0000:00/0000:00:11.2/usb1/1-2/1-2.2'
11:14:57.262 [I] osspec.c:243: total_read=310
buf='add@/devices/pci0000:00/0000:00:11.2/usb1/1-2/1-2.2/1-2.2:1.0'
11:14:57.276 [I] osspec.c:243: total_read=180
buf='add@/class/scsi_host/host18'
11:15:02.280 [I] osspec.c:243: total_read=240
buf='add@/devices/pci0000:00/0000:00:11.2/usb1/1-2/1-2.2/1-2.2:1.0/host18/target18:0:0/18:0:0:0'
11:15:02.299 [I] osspec.c:243: total_read=222 buf='add@/block/sdc'
11:15:02.329 [I] osspec.c:243: total_read=477 buf='add@/block/sdc/sdc1'

I'll try to investigate further...

Eugene