Re: Assessing USB Mass Storage devices - Debugging Info

Mark C wrote:
> Hi (again)
> 
> I have now compiled linux-2.4.19-ac2 with USB Mass Storage degugging
> Information.

A must for any debugging work :)

> If anyone can make some sence of this, I would be very gratefull for any
> more assistance :-)

> usb-storage: Bulk command S 0x43425355 T 0x12 Trg 0 LUN 0 L 255 F 128 CL
> 6
> usb-storage: Bulk command transfer result=0
> usb-storage: usb_stor_transfer_partial(): xfer 255 bytes
> usb-storage: usb_stor_bulk_msg() returned -32 xferred 0/255
> usb-storage: clearing endpoint halt for pipe 0xc0038280
> usb-storage: usb_stor_clear_halt: result=0
> usb-storage: usb_stor_transfer_partial(): unknown error

That doesn't look promissing...

> usb-storage: Bulk status result = 0
> usb-storage: Bulk status Sig 0x53425355 T 0x12 R 0 Stat 0x0
> usb-storage: -- Result from auto-sense is 0
> usb-storage: -- code: 0x70, key: 0x5, ASC: 0x24, ASCQ: 0x0
> usb-storage: Illegal Request: invalid field in CDB

Same here. could just be the WP (write protect?)
test failing.

> usb-storage: Command READ_10 (10 bytes)

Read 10 bytes.
>  sda1
Looks like it found a partition table there.
but it wasn't read by fdisk later...

> I will be doing some more searching on some of the information for
> dmesg, but to be honest most of it baffles me, as its kernel debugging
> output.

Same here. I'm not "in the know" with the lowlevel USB details.

> I will be posting this to both then usb and kernel mailing lists to try
> to get some more information.

I'm still on the kernel list. I watch there for futher info.

	-Thomas