Re: HS USB errors on OMAP3530

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 7, 2008 at 3:38 PM, David Brownell <david-b@xxxxxxxxxxx> wrote:
> 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
>

Dave,

I did use a Total Phase Beagle 480USB protocol analyzer when this
issue first manifested, but there is nothing that jumped out at me as
a possible error or glitch. It just looks like the transactions just
stopped mid-way without any rhyme or reason.

I've noticed this issue with a couple of HS flash drives, as well as,
a FS CD-ROM drive.

Would the "let SET_ADDRESS settle" change only affect the initial
detection? My initial insertion of device works great, the errors I
showed are after I do a read of a large amount of data from the Flash
drive and essentially wedge something in the USB stream.

Regards
~ Ashwin
--
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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux