On Tue, 22 Aug 2006, Søren Ræbild wrote: > Here's a debug log without ehci. It worked for a while and I was able > to mount a partition and list a few directories before it failed like > before. > > Søren Ræbild
Here's the interesting part: > Aug 22 06:12:07 sioux usb-storage: queuecommand called > Aug 22 06:12:07 sioux usb-storage: *** thread awakened. > Aug 22 06:12:07 sioux usb-storage: Command READ_10 (10 bytes) > Aug 22 06:12:07 sioux usb-storage: 28 00 03 7c d1 e5 00 00 08 00 > Aug 22 06:12:07 sioux usb-storage: Bulk Command S 0x43425355 T 0x4c L > 4096 F 128 Trg 0 LUN 0 CL 10 > Aug 22 06:12:07 sioux usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > Aug 22 06:12:07 sioux usb-storage: Status code 0; transferred 31/31 > Aug 22 06:12:07 sioux usb-storage: -- transfer complete > Aug 22 06:12:07 sioux usb-storage: Bulk command transfer result=0 > Aug 22 06:12:07 sioux usb-storage: usb_stor_bulk_transfer_sglist: xfer > 4096 bytes, 1 entries Perfectly normal so far. > Aug 22 06:12:07 sioux uhci_hcd 0000:00:1d.0: wakeup_rh (auto-start) > Aug 22 06:12:07 sioux hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0002 > Aug 22 06:12:07 sioux uhci_hcd 0000:00:1d.0: port 1 portsc 0c80,00 > Aug 22 06:12:07 sioux hub 2-0:1.0: over-current change on port 1 Look at that! A different, adjacent host controller got woken up with an overcurrent condition. Just like what happened before, when you were using EHCI. There's no way the device should be able to do that; I can't see how it could arise at all unless there's a hardware flaw on the motherboard. > Aug 22 06:12:07 sioux uhci_hcd 0000:00:1d.1: uhci_result_common: failed > with status 440000 > Aug 22 06:12:07 sioux usb-storage: Status code -84; transferred 0/4096 At exactly the same time, the transfer failed. > Aug 22 06:12:07 sioux usb-storage: -- unknown error > Aug 22 06:12:07 sioux usb-storage: Bulk data transfer result 0x4 > Aug 22 06:12:07 sioux usb-storage: -- transport indicates error, resetting > Aug 22 06:12:07 sioux hub 3-0:1.0: logical disconnect on port 1 > Aug 22 06:12:07 sioux usb-storage: usb_reset_device returns -19 > Aug 22 06:12:07 sioux usb-storage: usb_stor_Bulk_reset called > Aug 22 06:12:07 sioux usb-storage: usb_stor_control_msg: rq=ff rqtype=21 > value=0000 index=00 len=0 > Aug 22 06:12:07 sioux usb-storage: Soft reset failed: -19 > Aug 22 06:12:07 sioux usb-storage: scsi cmd done, result=0x70000 > Aug 22 06:12:07 sioux usb-storage: *** thread sleeping. > Aug 22 06:12:07 sioux hub 3-0:1.0: state 7 ports 2 chg 0002 evt 0000 > Aug 22 06:12:07 sioux hub 3-0:1.0: port 1, status 0100, change 0000, 12 Mb/s > Aug 22 06:12:07 sioux usb 3-1: USB disconnect, address 2 And according to the host controller, the device is no longer connected. This could have something to do with the electronic switch that internally attaches the device to either the EHCI or the UHCI controller; problems in that switch might manifest like this. I have no idea what the reason for this might be, or how to fix it. Maybe someone else on the mailing list has a suggestion. One possible way to work around it, if you have an extra PCI slot, would be to buy an add-on PCI USB card. They are pretty inexpensive, and a separate card wouldn't be subject to whatever problem affects the motherboard. Alan Stern ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
