On Tue, 28 Nov 2006, Bill Gatliff wrote: > Guys: > > > I'm trying to get USB pen drives working on a 2.4.26/PPC-based embedded > system. Unfortunately, at the moment a kernel upgrade to something less > ancient isn't an option. :( > > I can't rule out a hardware problem, but the drive I'm testing with will > successfully enumerate--- which suggests that the bus is at least > marginally stable: > > ... > usb-storage: USB Mass Storage device detected > usb-storage: Endpoints: In: 0xc1fee9d0 Out: 0xc1fee9e4 Int: 0xc1fee9f8 > (Period 1) > usb-storage: New GUID 0d7d16000000074b1a1701a2 > usb-storage: GetMaxLUN command result is 1, data is 0 > usb-storage: Transport: Bulk > usb-storage: Protocol: Transparent SCSI > ... > Vendor: Model: USB DISK 20X Rev: PMAP > Type: Direct-Access ANSI SCSI revision: 02 > ... > SCSI device sda: 1970176 512-byte hdwr sectors (1009 MB) > sda: Write Protect is off > Partition check: > /dev/scsi/host0/bus0/target0/lun0:<7>usb-storage: queuecommand() called > p1 > WARNING: USB Mass Storage data integrity not assured > USB Mass Storage device found at 3 > ... > > The device in question is a PNY Attache' 1GB. The linux-usb-devel > archives suggest this device has a checkered past but at the moment, > it's the only device I'm testing with. > > I have been unable to successfully mount the device, and the following > text captures the debug output. In summary, it always hangs at a > READ_10 with usb_stor_transfer_partial() returning a -84: > > ... > usb-storage: Command READ_10 (10 bytes) > usb-storage: 28 00 00 00 00 40 00 00 08 00 00 00 > usb-storage: Bulk command S 0x43425355 T 0xf Trg 0 LUN 0 L 4096 F 128 CL 10 > usb-storage: Bulk command transfer result=0 > usb-storage: usb_stor_transfer_partial(): xfer 4096 bytes > usb-storage: usb_stor_bulk_msg() returned -84 xferred 1408/4096 > usb-storage: usb_stor_transfer_partial(): unknown error > usb-storage: Bulk data transfer result 0x2 > usb-storage: Attempting to get CSW... > usb-storage: command_abort() called > > I can't figure out what the -84 says the problem is. Does anyone have > any suggestions? The device will mount on my Linux workstation (2.6.x) > just fine.
USB error codes are explained in the source file Documentation/usb/error-codes.txt. 84 is EILSEQ, which indicates an invalid bit stream was received from the device (bad CRC, invalid bit-stuffing, etc.). It could be a cable-level hardware problem. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
