|
Gilles Roy
|
Re: Question about an error message from enum-device/enum-usb after disconnecting the iPod
|
|
Gilles Roy
05/14/2009 10:10 PM
post29493
|
Re: Question about an error message from enum-device/enum-usb after disconnecting the iPod
> ustatus=0x2000004 ulen=0
> ustatus=0x2000004 ulen=0
These are the iPod driver attempting to receive packets. It takes some amount of milliseconds before the USB stack
notifies the iPod driver that the device is removed (it uses a callback mechanism, the iPod driver doesn't try to
interpret the exact meaning of the errors). If the callback comes a bit later, you see more of these logs. You can
safely ignore them. If you want to see what the status means, look into "sys/usbdi.h", you can see USDB_STATUS_* defines
, some for high bits and some for lower bits.
> RECV: EIO, errno=19
> UMOUNT:
Then you see these logs because the iPod driver finally realizes that the iPod is gone. These are again logs from the
iPod driver.
> Unable to find removal id '512'
> Unable to find removal id '513'
These last set of logs are are from the enumerator. It tries to slay some processes which it spawned, but those
processes are already gone. For example, io-audio self terminates so it should always print at least one of those
messages. I didn't expect the iPod driver to terminate itself though, could you be launching anything else when an iPod
is inserted? One thing you can try is to start the enumerator on the command line with verbosity, it should print what
the remove id are (i.e. it will show what it launches and the associated ID):
slay enum-devices enum-usb
enum-device -vvvvv &
Regards,
Gilles
|
|
|
|
|
