On Thursday 07 August 2008, Ashwin Bihari wrote: > sd 0:0:0:0: [sda] Attached SCSI removable disk > usb 1-2: reset high speed USB device using ehci-omap and address 2 > usb 1-2: device descriptor read/64, error -110 > usb 1-2: device descriptor read/64, error -110 > usb 1-2: reset high speed USB device using ehci-omap and address 2 > usb 1-2: device descriptor read/64, error -110 > usb 1-2: device descriptor read/64, error -110 > usb 1-2: reset high speed USB device using ehci-omap and address 2 > usb 1-2: device not accepting address 2, error -110 > usb 1-2: reset high speed USB device using ehci-omap and address 2 > usb 1-2: device not accepting address 2, error -110 > usb 1-2: USB disconnect, address 2 > sd 0:0:0:0: Device offlined - not ready after error recovery > Result: hostbyte=0x01 driverbyte=0x00 > end_request: I/O error, dev sda, sector 775288 > end_request: I/O error, dev sda, sector 775288 > ... I wouldn't assume this is specifically an OMAP issue -- though it might be in this case. If you could throw a USB sniffer at the problem and report what that shows, it may be enlightening... Folk have been reporting these symptoms for some time, but nobody can quite track it down. I think one person who was able to observe the problem (I've never seen it) reported that switching disk, USB cable, *OR* PC host made the problem go away ... but MS-Windows didn't see it on the same hardware. As I recall, one person had some recent success shrinking the "let SET_ADDRESS settle" mdelay in drivers/usb/hub.c (near line 2535). Strictly speaking, that shouldn't be needed. - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
