Comment 52 for bug 283759

Did a little more investigating into this - error -19 is 'ENODEV' or 'No such device' so obviously the problem is that the device is being pulled away, the driver noticing it (hence the error -19) and then not handling it properly.

@Andy - any ideas as to what we can try to find out how come the device is being disconnected?

As I see it, there are two problems:

a) The device disappears for unknown reasons, and
b) The driver bombs when trying to deal with that situation

The 2 are actually unrelated in the sense that fixing either of them would (theoretically) solve the problem although the right thing is obviously to fix both.