On Sat, 10 Jul 2004, Florian Schmitt wrote: > Hello, > > it seems that my kernel (2.4.7-bk20) doesn't like my new usb stick :-( > I've attached the related kernel logs. Perhaps someone can make sense of it? > Any suggestions would be greatly appreciated ;-) > > bye, > Flo > > - From /var/log/messages:
> Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 > value=0000 index=00 len=1 > Jul 10 10:33:35 phoenix kernel: usb-storage: GetMaxLUN command result is -32, data > is 0 The device doesn't like GetMaxLUN. While not unheard of, it is unusual. > Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_control_msg: rq=01 rqtype=02 > value=0000 index=82 len=0 > Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_clear_halt: result = 0 > Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_control_msg: rq=01 rqtype=02 > value=0000 index=01 len=0 > Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_clear_halt: result = 0 > Jul 10 10:33:35 phoenix kernel: usb-storage: *** thread sleeping. > Jul 10 10:33:35 phoenix kernel: scsi0 : SCSI emulation for USB Mass Storage devices > Jul 10 10:33:35 phoenix kernel: usb-storage: queuecommand called > Jul 10 10:33:35 phoenix kernel: usb-storage: *** thread awakened. > Jul 10 10:33:35 phoenix kernel: usb-storage: Command INQUIRY (6 bytes) > Jul 10 10:33:35 phoenix kernel: usb-storage: 12 00 00 00 24 00 > Jul 10 10:33:35 phoenix kernel: usb-storage: Bulk Command S 0x43425355 T 0x1 L 36 F > 128 Trg 0 LUN 0 CL 6 > Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 31 > bytes > Jul 10 10:33:35 phoenix kernel: usb-storage: Status code 0; transferred 31/31 > Jul 10 10:33:35 phoenix kernel: usb-storage: -- transfer complete > Jul 10 10:33:35 phoenix kernel: usb-storage: Bulk command transfer result=0 > Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 36 > bytes > Jul 10 10:33:35 phoenix kernel: usb-storage: Status code 0; transferred 13/36 Then it sends back 13 bytes instead of 36 for the INQUIRY data. I wouldn't be surprised if those 13 bytes contain a CSW. Of course, there's no reason for the device to send a CSW at this time -- in fact it's illegal to do so. > Jul 10 10:33:35 phoenix kernel: usb-storage: -- short transfer > Jul 10 10:33:35 phoenix kernel: usb-storage: Bulk data transfer result 0x1 > Jul 10 10:33:35 phoenix kernel: usb-storage: Attempting to get CSW... > Jul 10 10:33:35 phoenix kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 13 > bytes > Jul 10 10:33:35 phoenix kernel: usb-storage: Status code -75; transferred 13/13 > Jul 10 10:33:35 phoenix kernel: usb-storage: -- babble This is probably the 36 bytes of INQUIRY data, sent when the computer was expecting only a 13-byte CSW. That creates a babble condition. Your USB controller appears to be made by VIA, and their controllers have the unfortunate habit of shutting down when they receive a babble packet. >From this point on, nothing at all works. My guess is that your new USB stick is broken. Try to exchange it for one that works properly. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
