AnyDATA ADU-500A USB-modem and a lot of "ubsa_cfg_request" errors

[Alexey Markov-2]

Hello!

First of all, excuse my English.

Well, i have an AnyDATA ADU-500A Rev.A USB-modem, and i'm going to use
it for my handmade "VIA EPIA-based mobile router". I have installed
latest 8.0-RC2 and configured ppp, and now everything works just fine,
except that I got a lot of such messages on console when I run ppp:

ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED (ignored)

I really want to work it out, and I have some spare time for experiments,
but haven't any experience of debuging kernel drivers. Can anybody give me
a clue to solve this little problem?

--
WBR, Alexey Markov.

_______________________________________________
freebsd-usb@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscribe@..."

[Hans Petter Selasky]

On Thursday 05 November 2009 09:01:05 Alexey Markov wrote:

> Hello!
>
> First of all, excuse my English.
>
> Well, i have an AnyDATA ADU-500A Rev.A USB-modem, and i'm going to use
> it for my handmade "VIA EPIA-based mobile router". I have installed
> latest 8.0-RC2 and configured ppp, and now everything works just fine,
> except that I got a lot of such messages on console when I run ppp:
>
> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED
> (ignored)
>
> I really want to work it out, and I have some spare time for experiments,
> but haven't any experience of debuging kernel drivers. Can anybody give me
> a clue to solve this little problem?

Did you look in the source code:

/sys/dev/usb/serial/ubsa.c

--HPS
_______________________________________________
freebsd-usb@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscribe@..."

[Alexey Markov-2]

Hello, Hans!
On November, 05 2009 at 15:59 you wrote to freebsd-usb@...:

 ??>> except that I got a lot of such messages on console when I run ppp:
 ??>>
 ??>> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED
 ??>>
 ??>> I really want to work it out, and I have some spare time for
 ??>> experiments, but haven't any experience of debuging kernel drivers.
 ??>> Can anybody give me a clue to solve this little problem?

 HPS> Did you look in the source code:
 HPS> /sys/dev/usb/serial/ubsa.c

Yes, of course! Line #317 belongs to ubsa_cfg_request(), which just calls
another function, ucom_cfg_do_request(), with some parameters. But this
function is called several times in the code, so I've changed code of
ubsa_cfg_request() function to see, which config requests are failed:

DPRINTFN(0, "device request failed, err=%s, index=%d, value=%d "...

I have got a lot of messages like this one:

ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED,
index=10, value=1 (ignored)

where index/value pairs sequence is:

10/1, 11/1, 12/0, 0/24, 3/0, 2/3, 1/0, 16/384, 0/2, 3/0 and so forth.

It seems, that driver tried to set some config parameters like DTR, RTS,
BAUDRATE etc, and failed. But after all, modem is working (maybe, with
non-optimal settings or default settings).

So, I need an advice: what can I do to find the cause of failed config
requests?

--
WBR, Alexey Markov.
_______________________________________________
freebsd-usb@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscribe@..."

[Hans Petter Selasky]

On Friday 06 November 2009 08:31:05 Alexey Markov wrote:

> Hello, Hans!
> On November, 05 2009 at 15:59 you wrote to freebsd-usb@...:
>
>  ??>> except that I got a lot of such messages on console when I run ppp:
>  ??>>
>  ??>> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED
>  ??>>
>  ??>> I really want to work it out, and I have some spare time for
>  ??>> experiments, but haven't any experience of debuging kernel drivers.
>  ??>> Can anybody give me a clue to solve this little problem?
>
>  HPS> Did you look in the source code:
>  HPS> /sys/dev/usb/serial/ubsa.c
>
> Yes, of course! Line #317 belongs to ubsa_cfg_request(), which just calls
> another function, ucom_cfg_do_request(), with some parameters. But this
> function is called several times in the code, so I've changed code of
> ubsa_cfg_request() function to see, which config requests are failed:
>
> DPRINTFN(0, "device request failed, err=%s, index=%d, value=%d "...
>
> I have got a lot of messages like this one:
>
> ubsa_cfg_request:371: device request failed, err=USB_ERROR_STALLED,
> index=10, value=1 (ignored)
>
> where index/value pairs sequence is:
>
> 10/1, 11/1, 12/0, 0/24, 3/0, 2/3, 1/0, 16/384, 0/2, 3/0 and so forth.
>
> It seems, that driver tried to set some config parameters like DTR, RTS,
> BAUDRATE etc, and failed. But after all, modem is working (maybe, with
> non-optimal settings or default settings).
>
> So, I need an advice: what can I do to find the cause of failed config
> requests?

Hi,

Maybe you device belongs in the ugensa.c driver and not ubsa.c if it does not
support all those DTR/RTS ... settings? Do you have a datasheet for the modem
in question?

--HPS
_______________________________________________
freebsd-usb@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscribe@..."

[Alexey Markov-2]

Hello, Hans!
On November, 06 2009 at 11:29 you wrote to Alexey Markov:

 HPS> Maybe you device belongs in the ugensa.c driver and not ubsa.c

No, AnyDATA ADU-500A definitely belongs to the ubsa driver, it even
stated in the man page of ubsa. Just in case i had tried the ugensa
driver, but it doesn't work at all.

 HPS> if it does not support all those DTR/RTS ... settings?

I think, it may be connected with this PR: usb/134950

 HPS>  Do you have a datasheet for the modem in question?

Alas! There is no any datasheets neither in Google nor on manufacturer
site. :-(

--
WBR, Alexey Markov.
_______________________________________________
freebsd-usb@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscribe@..."