Comment 1 for bug 180472

On Sat, Jan 05, 2008 at 02:31:21AM -0000, Grant Grundler wrote:
> If I connect the device while hald is running, I get the follow dmesg
> output. Eveything is good up to "Attached scsi generic sg1 type 0"
> output. "reset" is because hald is doing something and results in the
> deivce going "offline". As noted above, stopping hald allows me to read
> from the device.
...
> root@mb500:/etc/udev/rules.d # ls -l /dev/sdb*
> brw-rw---- 1 root plugdev 8, 16 2008-01-04 17:13 /dev/sdb
> brw-rw---- 1 root plugdev 8, 17 2008-01-04 17:13 /dev/sdb1
>
> and I conclude udev is working correctly.

Sorry - this is wrong. Somehow I messed up when trying to triag this bug.
udev by itself (without hald) causes the "device offline" issues.
I tried to reproduce this with udev running and discovered it was
happening anyway. So I can't explain how I reached the conclusion
that it was hald. Perhaps there are other problems with hald as well
that caused the same sometimes or interactions with udev or the
same kernel code invoked by udev.

Issues with booting newer kernels on my laptop have made it difficult
to track down exactly which command sent to the device is causing problems.
Once I track that down, we can decide if this bug should be re-assigned
to udev package or whatever is appropriate. It will probably take another
week since I very little time outside of work to track this down.

again, my apologies for the (likely) misdiagnosis,
grant