QMI modems with MM-master branch error
Dan Williams
dcbw at redhat.com
Fri May 5 16:17:18 UTC 2017
On Fri, 2017-05-05 at 14:08 +0000, Penalva, Salvador wrote:
> I thought that too,
>
> but this modem still worked with the commit before the last changes
> I mentioned in the email before. Why is the connection attempt
> cancelled then an in the second retry working again?
The issue from the original logs has been fixed as mentioned by
Aleksander.
In your latest logs, the modem really is indicating that it has lost
registration during the connection attempt:
ModemManager[918]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (searching -> idle)
ModemManager[918]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (idle -> registering)
ModemManager[918]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
ModemManager[918]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (searching -> registered)
ModemManager[918]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
ModemManager[918]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (home -> idle)
"idle" is not a registered state, and the modem is reporting that it
has disconnected from the netowrk.
To debug further, would you be able to back up to commit
8c04cc036782dab0e80c1f2314baa3376eecad02 and grab debug logs of the
full connect sequence so we can see what's going on when the first
connect is successful?
Thanks!
Dan
> Thanks,
>
> Salvador
>
> -----Original Message-----
> From: Aleksander Morgado [mailto:aleksander at aleksander.es]
> Sent: viernes, 05 de mayo de 2017 14:52
> To: Penalva, Salvador
> Cc: ModemManager (development); Ben Chan
> Subject: Re: QMI modems with MM-master branch error
>
> On Fri, May 5, 2017 at 1:36 PM, Penalva, Salvador <Salvador.Penalva at d
> igi.com> wrote:
> > ModemManager[918]: <info> Modem
> > /org/freedesktop/ModemManager1/Modem/0: state changed (searching
> > ->
> > registered)
> > ModemManager[918]: <info> Simple connect state (6/8): Bearer
> > ModemManager[918]: <info> Simple connect state (7/8): Connect
> > ModemManager[918]: <info> Modem
> > /org/freedesktop/ModemManager1/Modem/0: state changed (registered
> > ->
> > connecting)
> > ModemManager[918]: [/dev/cdc-wdm0] Allocating new client ID...
> > ModemManager[918]: [/dev/cdc-wdm0] Registered 'wds' (version 1.36)
> > client with ID '11'
> > ModemManager[918]: <info> Modem
> > /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state
> > changed (home -> idle)
> > ModemManager[918]: <info> Modem
> > /org/freedesktop/ModemManager1/Modem/0: state changed (connecting
> > ->
> > disconnecting)
> > ModemManager[918]: <warn> Error disconnecting bearer
> > '/org/freedesktop/ModemManager1/Bearer/0': 'Couldn't disconnect QMI
> > bearer: this bearer is not connected'. Will assume disconnected
> > anyway.
> > error: couldn't connect the modem:
> > 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Cancelled:
> > Connection setup operation has been cancelled'
> > ModemManager[918]: <info> Modem
> > /org/freedesktop/ModemManager1/Modem/0: state changed
> > (disconnecting
> > -> enabled)
>
> This issue seems unrelated to the original bug; it looks like the
> modem registration is going away (home->idle) just in the middle of a
> connection attempt, so the connection attempt is cancelled.
>
>
> --
> Aleksander
> https://aleksander.es
> _______________________________________________
> ModemManager-devel mailing list
> ModemManager-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
More information about the ModemManager-devel
mailing list