URC mistaken for solicited responce

[matthew stanger]

>
> +CIND shouldn't be any URC

+CIND isn't (polled by mm-broadband-modem.c), but the +CIEV that follows it
is.

Cinterion's ^SIND turn's on the +CIEV URC's. Which means the setting AT cmd
doesn't match the AT URC response. Lovely huh, not sure if that makes a
difference.

On Fri, May 18, 2018 at 2:00 PM, Aleksander Morgado <
aleksander at aleksander.es> wrote:

> > I found this in our logs. As you can see we get a URC right after a
> > solicited request that's polled. This causes a connection reset.
> >
> > 2018-04-25T07:35:19.155738 ModemManager[1797]: <debug> (ttyACM1): -->
> > 'AT^SWWAN?<CR>'
> > 2018-04-25T07:35:20.317705 ModemManager[1797]: <debug> (ttyACM0): <--
> > '<CR><LF>+CIEV: 1,3<CR><LF>'
> > 2018-04-25T07:35:20.398151 ModemManager[1797]: <debug> (ttyACM1): <--
> > '<CR><LF>+CIND: 0,2,1,1,1,0,1,0<CR><LF><CR><LF>OK<CR><LF><CR><LF>+CIEV:
> > 1,3<CR><LF><CR><LF>+CIEV: psinfo,6<CR><LF><CR><LF>+CREG:
> > 5,"1611","0217BCC",2<CR><LF><CR><LF>+CGREG:
> > 5,"1611","0217BCC",2<CR><LF><CR><LF>+CIEV: psinfo,10<CR><LF>'
> > 2018-04-25T07:35:20.413390 ModemManager[1797]: <debug> Modem
> > /org/freedesktop/ModemManager1/Modem/0: access technology changed
> (hsdpa,
> > hsupa -> umts)
> > 2018-04-25T07:35:20.427281 ModemManager[1797]: <debug> Modem
> > /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts
> ->
> > hsdpa, hsupa)
> > 2018-04-25T07:35:20.438959 ModemManager[1797]: <warn>  checking if
> connected
> > failed: Couldn't parse ^SWWAN response: '+CIND: 0,2,1,1,1,0,1,0'
> >
> > I'm looking to push a patch for this but wanted to see if anyone had
> > thoughts on approach before I start?
> >
>
> Hum.... +CIND shouldn't be any URC. Are you sure it's not a previously
> sent AT+CIND? that ended up timing out?
>
> --
> Aleksander
> https://aleksander.es
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20180518/324cc5c2/attachment-0001.html>