Hi Alan,
Yes, I realize that a flaky cable definitely is a possibility.
However, as I always saw the first part in syslog (this particular
example is from now, when it started working) like the following:
usb 1-1: new high speed USB device using ehci_hcd and address 17
usb 1-1: configuration #1 chosen from 1 choice
usb-storage: USB Mass Storage device detected
usb-storage: -- associate_dev
usb-storage: Vendor: 0x0402, Product: 0x5621, Revision: 0x0106
usb-storage: Interface Subclass: 0x06, Protocol: 0x50
usb-storage: Transport: Bulk
usb-storage: Protocol: Transparent SCSI
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: *** thread sleeping.
usb-storage: device found at 17
usb-storage: waiting for device to settle before scanning
usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1
usb-storage: GetMaxLUN command result is 1, data is 0
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
<snip>
It looked like the HW was consistent in its behaviour, but without
knowing what it means, I can see it start being different from this and
on (the following taken from my first posting when it didn't yet work):
usb-storage: Status code -32; transferred 0/36
My thoughts then becomes:
Is it possible to distinguish such a failure from a bad implementation
of a device's USB stack?
If it is, it would be great to also be told in some way that doesn't
require me to know USB so intimately.
E.g.: Connection Error: You seem to have a bad cable
Registration Error: There are problems with registering the
device. It may have a bad XYZ command processing
I mean, I do have trouble decoding these lines:
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F 128 Trg 0 LUN 0 CL 6
But then, what do I know :-)
Thanks,
Peter
Alan Stern wrote:
On Sun, 10 Feb 2008, Peter Rasmussen wrote:
Could it be that the HW is flaky? It isn't a new disk.
There could be flaky cable connections.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
