EVDO creating hell lot of problem

GoogleGroups
1

Hello to all,

i'm using a evdo built by ZTE CDMA tech. Whenever i connect my device
after some times it starts throwing the following errors-
usb 1-2: clear tt 1 (9032) error -71
[ 139.999908] usb 1-2: clear tt 1 (9032) error -71
[ 140.050750] option: option_instat_callback: error -32
[ 140.306549] option: option_instat_callback: error -32
[ 140.562500] option: option_instat_callback: error -32
[ 140.690734] option: option_instat_callback: error -32
[ 140.946563] option: option_instat_callback: error -32
[ 141.202514] option: option_instat_callback: error -32
[ 141.458404] option: option_instat_callback: error -32
[ 141.714508] option: option_instat_callback: error -32
[ 141.970550] option: option_instat_callback: error -32
[ 142.226348] option: option_instat_callback: error -32
[ 142.482482] option: option_instat_callback: error -32
[ 142.738494] option: option_instat_callback: error -32
[ 148.882324] option: option_instat_callback: error -32
[ 148.922760] usb 1-2: clear tt 1 (0040) error -71
[ 148.935760] usb 1-2: clear tt 1 (0040) error -71
[ 149.138275] option: option_instat_callback: error -32
[ 149.394409] option: option_instat_callback: error -32
[ 149.650360] option: option_instat_callback: error -32
root@beagleboard:~# [ 149.906280] option: option_instat_callback:
error -32
[ 150.162353] option: option_instat_callback: error -32
[ 150.418365] option: option_instat_callback: error -32
[ 150.674255] option: option_instat_callback: error -32
[ 150.930358] option: option_instat_callback: error -32

and keeps on coming for few minutes then stops with this error
option: option_instat_callback: error -108

But after that device stops responding and only restart remain
solution for this.
After some search on google i found that -32 error corresponds to
EPIPE error. and the module which generates the error is "option" .
Even i got to know that this error can be because of hardware problem.
Improper wire, or device problem can generate this issue. But device
works fine on my PC and i'm using a externally powered usb hub.
Please help how to solve this problem or any workaround such that i
keep on working after ignoring this error.

regards
Abhishek

2

Yesterday i tried to debug this error and i used this commad to get
the following output cat /sys/kernel/usb/usbmon/1u

cfd253c0 435415160 C Ii:1:008:1 -32:128 0
cfd253c0 435420318 S Ii:1:008:1 -115:128 64 <
cfd251c0 435655455 S Bo:1:008:2 -115 1 = 41
cfd251c0 435659545 C Bo:1:008:2 -71 0
[ 443.682464] option: option_instat_callback: error -32
cfd253c0 443863004 C Ii:1:008:1 -32:128 0
cfd253c0 443868192 S Ii:1:008:1 -115:128 64 <
[ 443.938323] option: option_instat_callback: error -32
cfd253c0 444118925 C Ii:1:008:1 -32:128 0
cfd253c0 444124052 S Ii:1:008:1 -115:128 64 <
[ 444.194458] option: option_instat_callback: error -32
cfd253c0 444374998 C Ii:1:008:1 -32:128 0
cfd253c0 444380186 S Ii:1:008:1 -115:128 64 <
[ 444.450408] option: option_instat_callback: error -32
cfd253c0 444630981 C Ii:1:008:1 -32:128 0
cfd253c0 444636139 S Ii:1:008:1 -115:128 64 <
[ 444.706329] option: option_instat_callback: error -32
cfd253c0 444886900 C Ii:1:008:1 -32:128 0
cfd253c0 444892057 S Ii:1:008:1 -115:128 64 <
[ 444.962371] option: option_instat_callback: error -32
cfd253c0 445142943 C Ii:1:008:1 -32:128 0
cfd253c0 445148100 S Ii:1:008:1 -115:128 64 <
here i can see that Callback returns -32 and Submission returns -115
always...
please can anyone help me put with this problem

3

That looks like a known issue in the driver.

http://www.google.co.in/search?aq=f&sourceid=chrome&ie=UTF-8&q=option_instat_callback

How is the modem connected to the board, is it via a hub?

-Deepak

4

I tried to find more solution on this but it seems to me like its a
hardware issue. whenever I dont connect power to my hub and try to power
my hub from beagle USB host only, i start getting this error. and it
does not stop. so it's clear that hardware or power is creating an
issue. BUt sometime when i keep external power for hub then also it
throws this error. I just want some work around which can solve this
problem.

Linux version that i'm using is 2.6.35.7
and beagle version is c3

5

Well for starters, on a C3 board, make sure your usb hub is externally
powered... There is a very limited amount of power on the ehci
port...

Regards,