-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 30 apr 2008, om 11:17 heeft Felipe Balbi het volgende geschreven:
On Wed, 30 Apr 2008 11:09:37 +0200, Koen Kooi <k.kooi@xxxxxxxxxxxxxxxxxx
>
wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 30 apr 2008, om 10:42 heeft Syed Mohammed, Khasim het volgende
geschreven:
Hi all,
We have USB ECHI port 1 integrated with SMSC PHY (USB 3326) on
Beagle Board. I have connected a high speed Mass Storage (USB
harddisk) to the port, the enumeration happens fine and I am also
able to do a data transfer, but after some time, it fails with below
message:
ehci-omap ehci-omap.0: port 1 reset error -110
hub 2-0:1.0: hub_port_status failed (err = -32)
# ehci-omap ehci-omap.0: port 1 reset error -110
hub 2-0:1.0: hub_port_status failed (err = -32)
I'm having similar issues with usbon the beagleboard:
usb 1-1: USB disconnect, address 2
usb 1-1.3: USB disconnect, address 7
eth0: unregister 'asix' usb-ehci-omap.0-1.3, ASIX AX8817x USB 2.0
Ethernet
usb 1-1: clear tt 4 (9082) error -19
usb 1-1: clear tt 4 (9082) error -19
I tried various combinations of the usb-ethernet adaptor with and
without hub and found:
* no hub, low cpu load + slow transfer (e.g. download over adsl):
transferring a few MiBs is OK
* hub, low cpu load + slow transfer: transferring ~ 1MiB is OK
* big cpu load (e.g. using scp): 128KiB max
I didn't dare to try a USB disk yet :)
false overcurrent indication maybe ?
try modprobe ehci_hcd ignore_oc=1
I've uploaded a kernel with your timeout patch and a modular ehci_hcd
(so you need to unpack modules.tgz into your rootfs) to here:
http://amethyst.openembedded.net/~koen/beagleboard/usbtest/
I'm currently 700 km from my beagleboard, so testing is appreciated :)
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFIGEfvMkyGM64RGpERAk/cAJ0T3DKFfouuyQUiTrZj33POfqTBKQCdGu0m
uvY9AAnoacU189vQK2gZZd8=
=ow2T
-----END PGP SIGNATURE-----
--
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
