On Mon, 6 Dec 2004, Eero Volotinen wrote: > Unloading ehci_hcd results same errors :( > > Debug output follows:
> ehci_hcd 0000:00:10.3: port 4 high speed > ehci_hcd 0000:00:10.3: GetStatus port 4 status 001005 POWER sig=se0 PE > CONNECT > usb 1-4: new high speed USB device using ehci_hcd and address 4 > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: port 4 high speed > ehci_hcd 0000:00:10.3: GetStatus port 4 status 001005 POWER sig=se0 PE > CONNECT > usb 1-4: device descriptor read/64, error -71 > ehci_hcd 0000:00:10.3: port 4 high speed > ehci_hcd 0000:00:10.3: GetStatus port 4 status 001005 POWER sig=se0 PE > CONNECT Looks like you still had ehci_hcd loaded when you ran this test. Never mind, I don't think it matters... > usb 1-4: new device strings: Mfr=1, Product=2, SerialNumber=3 > usb 1-4: default language 0x0409 > usb 1-4: Product: FHD-Classic > usb 1-4: Manufacturer: Freecom Technologies > usb 1-4: SerialNumber: 1000000000000000152CF > usb 1-4: hotplug > usb 1-4: adding 1-4:1.0 (config #1, interface 0) > usb 1-4:1.0: hotplug > usb-storage 1-4:1.0: usb_probe_interface > usb-storage 1-4:1.0: usb_probe_interface - got id > usb-storage: USB Mass Storage device detected > usb-storage: -- associate_dev > usb-storage: Vendor: 0x07ab, Product: 0xfccd, Revision: 0x0406 > usb-storage: Interface Subclass: 0x06, Protocol: 0x50 > usb 1-4: 05-wait_for_sys timed out on ep0in > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes > ehci_hcd 0000:00:10.3: devpath 4 ep0in 3strikes These may correspond to some of those -71 errors you saw before. I still don't know why they show up here, but I have a hunch... <snip> > usb-storage: *** thread awakened. > usb-storage: Command INQUIRY (6 bytes) > usb-storage: 12 00 00 00 ff 00 > usb-storage: Bulk Command S 0x43425355 T 0x1f L 255 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 > usb-storage: Bulk command transfer result=0 > usb-storage: usb_stor_bulk_transfer_sglist: xfer 255 bytes, 1 entries > usb-storage: Status code -121; transferred 36/255 > usb-storage: -- short read transfer > usb-storage: Bulk data transfer result 0x1 > usb-storage: Attempting to get CSW... > usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes > usb-storage: Status code -32; transferred 0/13 > usb-storage: clearing endpoint halt for pipe 0xc0010480 > usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value=0000 index=82 len=0 > ehci_hcd 0000:00:10.3: devpath 4 ep0out 3strikes > usb-storage: usb_stor_clear_halt: result = -71 > usb-storage: Bulk status result = 4 > usb-storage: -- transport indicates error, resetting > usb-storage: usb_stor_Bulk_reset called > usb-storage: usb_stor_control_msg: rq=ff rqtype=21 value=0000 index=00 len=0 > ehci_hcd 0000:00:10.3: devpath 4 ep0out 3strikes > usb-storage: Soft reset failed: -71 > usb-storage: scsi cmd done, result=0x70000 > usb-storage: *** thread sleeping. These commands, 255-byte INQUIRYs, seem to occur a large number of times in your logs. They are not generated by the regular SCSI stack, so a user program must be responsible. They are confusing your device and causing lots of problems. I don't know what other program or daemon you may have running that wants to access a new device, but I bet it's something like haldaemon or gpilot. Maybe lsof will give you a clue, if you can find a process holding open a file under /proc/bus/usb. Or you could try loading usbcore with the "usbfs_snoop=y" parameter and see what shows up in the system log. Alan Stern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
