Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Unsalble cellular connection (Michael Nazzareno Trimarchi)
2. Re: Unsalble cellular connection (Jonas Bonn)
3. Re: Unsalble cellular connection (Jonas Bonn)
4. Re: Unsalble cellular connection (Jonas Bonn)
----------------------------------------------------------------------
Message: 1
Date: Mon, 19 Aug 2019 09:36:35 +0200
From: Michael Nazzareno Trimarchi <[email protected]>
To: Jonas Bonn <[email protected]>
Cc: JH <[email protected]>, connman <[email protected]>,
Giacinto Cifelli <[email protected]>, Daniel Wagner <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: Unsalble cellular connection
Message-ID:
<CAOf5uw=6hQkfhAt=OWH+mim30NyOHU6Z8GVMJ6yKCEf=1nf...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi
On Mon, Aug 19, 2019 at 7:38 AM Jonas Bonn <[email protected]> wrote:
>
> Hi JH,
>
> On 19/08/2019 03:51, JH wrote:
> > Hi Michael,
> >
> > On 8/18/19, Michael Nazzareno Trimarchi <[email protected]>
> > wrote:
> >> Aug 17 11:32:44 solar kernel: usb 1-1: new high-speed USB device
> >> number 5 using ci_hdrc
> >> Aug 17 11:32:45 solar kernel: usb 1-1: New USB device found,
> >> idVendor=05c6, idProduct=90b2, bcdDevice= 0.00
> >> Aug 17 11:32:45 solar kernel: usb 1-1: New USB device strings: Mfr=1,
> >> Product=2, SerialNumber=3
> >> Aug 17 11:32:45 solar kernel: usb 1-1: Product: QHSUSB__BULK
> >> Aug 17 11:32:45 solar kernel: usb 1-1: Manufacturer: Qualcomm CDMA
> >> Technologies MSM
> >> Aug 17 11:32:45 solar kernel: usb 1-1: SerialNumber: 5ff10299
> >>
> >> Here seems that reboot in bootloader mode. I have couple of disconnect
> >> and reconnect and I don't know if connman
> >> send some power on/off at command and make this strange behavior. The
> >> fact that start in bootloader mode can be a power
> >> issue? can you try to connect using a powered HUB?
> >
> > I did a couple of restarting ofonod and connmand during the debug, one
> > or two times power recycling manually, not clear if it was me to cause
> > those reboot or not.
> >
> > Like Daniel said, it was unlikely that connman would run reboot, it
> > might just record some messages from kernel.
>
> Neither connman nor ofono are currently capable of rebooting the modem.
>
> >
> > Just talked to the hardware engineer, he said who is very concerning
> > we are using kernel 5.1.0, he said we should use kernel 4.9.123, could
> > the kernel 5.1.0 cause that issue? Jonas what is your comments?
>
> I find the advice rather concerning! Hope you're not getting investment
> advice from this guy, too...
>
> The kernel log has this:
>
> Aug 17 08:51:46 solar kernel: usb 1-1: USB disconnect, device number 3
> Aug 17 08:51:46 solar kernel: option1 ttyUSB0: GSM modem (1-port)
> converter now disconnected from ttyUSB0
> Aug 17 08:51:46 solar kernel: option 1-1:1.0: device disconnected
> Aug 17 08:51:46 solar kernel: option1 ttyUSB1: GSM modem (1-port)
> converter now disconnected from ttyUSB1
> Aug 17 08:51:46 solar kernel: option 1-1:1.2: device disconnected
> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: nonzero urb status
> received: -71
>
> That's a USB communication failure!
>
> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback - 0 bytes
> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback -
> usb_submit_urb failed with result -19
> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3 wwan0: unregister
> 'qmi_wwan' usb-ci_hdrc.1-1, WWAN/QMI device
>
> Below, the device (modem) is reenumerated, which would indicate to me
> that it has restarted. I don't think the kernel automatically sends a
> reset to a device on comm failures...??? This explains the
> communication failure, at least.
Can be chattering and rush current? Even are you sure that you don't have
some reset our of the ofono service that send an at command that
restart the modem?
Michael
>
> Aug 17 08:51:49 solar kernel: usb 1-1: new high-speed USB device number
> 4 using ci_hdrc
> Aug 17 08:51:50 solar kernel: usb 1-1: New USB device found,
> idVendor=05c6, idProduct=90b2, bcdDevice= 0.00
> Aug 17 08:51:50 solar kernel: usb 1-1: New USB device strings: Mfr=3,
> Product=2, SerialNumber=4
> Aug 17 08:51:50 solar kernel: usb 1-1: Product: Qualcomm CDMA
> Technologies MSM
> Aug 17 08:51:50 solar kernel: usb 1-1: Manufacturer: Qualcomm, Incorporated
> Aug 17 08:51:50 solar kernel: usb 1-1: SerialNumber: 5ff10299
> Aug 17 08:51:50 solar kernel: option 1-1:1.0: GSM modem (1-port)
> converter detected
> Aug 17 08:51:50 solar kernel: usb 1-1: GSM modem (1-port) converter now
> attached to ttyUSB0
> Aug 17 08:51:50 solar kernel: option 1-1:1.2: GSM modem (1-port)
> converter detected
> Aug 17 08:51:50 solar kernel: usb 1-1: GSM modem (1-port) converter now
> attached to ttyUSB1
> Aug 17 08:51:50 solar kernel: qmi_wwan 1-1:1.3: cdc-wdm0: USB WDM device
> Aug 17 08:51:50 solar kernel: qmi_wwan 1-1:1.3 wwan0: register
> 'qmi_wwan' at usb-ci_hdrc.1-1, WWAN/QMI device, f6:0d:90:fa:af:24
>
> ofono should _definitely_ show this device reenumeration in its logs.
> Why is that not there???
>
> -----------------------
>
> Subsequently, the kernel log shows:
>
> Aug 17 11:32:43 solar kernel: usb 1-1: USB disconnect, device number 4
> Aug 17 11:32:43 solar kernel: option1 ttyUSB0: GSM modem (1-port)
> converter now disconnected from ttyUSB0
> Aug 17 11:32:43 solar kernel: option 1-1:1.0: device disconnected
> Aug 17 11:32:43 solar kernel: option1 ttyUSB1: GSM modem (1-port)
> converter now disconnected from ttyUSB1
> Aug 17 11:32:43 solar kernel: option 1-1:1.2: device disconnected
> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3: nonzero urb status
> received: -71
>
> Again, comm error.
>
> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback - 0 bytes
> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback -
> usb_submit_urb failed with result -19
> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3 wwan0: unregister
> 'qmi_wwan' usb-ci_hdrc.1-1, WWAN/QMI device
>
> Modem has rebooted and is reenumerated below.
>
> Aug 17 11:32:44 solar kernel: usb 1-1: new high-speed USB device number
> 5 using ci_hdrc
> Aug 17 11:32:45 solar kernel: usb 1-1: New USB device found,
> idVendor=05c6, idProduct=90b2, bcdDevice= 0.00
> Aug 17 11:32:45 solar kernel: usb 1-1: New USB device strings: Mfr=1,
> Product=2, SerialNumber=3
> Aug 17 11:32:45 solar kernel: usb 1-1: Product: QHSUSB__BULK
> Aug 17 11:32:45 solar kernel: usb 1-1: Manufacturer: Qualcomm CDMA
> Technologies MSM
> Aug 17 11:32:45 solar kernel: usb 1-1: SerialNumber: 5ff10299
> Aug 17 11:32:45 solar kernel: option 1-1:1.0: GSM modem (1-port)
> converter detected
> Aug 17 11:32:45 solar kernel: usb 1-1: GSM modem (1-port) converter now
> attached to ttyUSB0
>
> Here, however, the modem isn't booting up into normal operational state,
> but rather into some other configuration that, presumably, is intended
> for doing device firmware updates...
>
> So you have a couple of things to figure out:
> i) Why is the modem restarting (crashing) spontaneously?
> ii) What are the conditions for entering the bootloader/firmware update
> state? How are you managing to meet these conditions?
> iii) Why is ofono not showing the device reenumeration... it should,
> and it should show the modem being taken down and brought back up again.
> (I suspect it's just a matter of your logs being out of sync... it's
> probably there if you look, again).
>
> >
> > Let me further clarify it, the issue did not occur very often, it
> > occurred randomly between hours to many days, that is a big worry, LTE
> > should be 100% stable.
>
> The issue doesn't seem to have anything to do with the radio link. The
> LTE is probably stable; the issue lies elsewhere.
>
> /Jonas
>
> >
> > Thank you.
> >
> > Kind regards,
> >
> > - jh
> >
--
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO - Founder Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
| [`as] http://www.amarulasolutions.com |
------------------------------
Message: 2
Date: Mon, 19 Aug 2019 09:50:58 +0200
From: Jonas Bonn <[email protected]>
To: Michael Nazzareno Trimarchi <[email protected]>
Cc: JH <[email protected]>, connman <[email protected]>,
Giacinto Cifelli <[email protected]>, Daniel Wagner <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: Unsalble cellular connection
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 19/08/2019 09:36, Michael Nazzareno Trimarchi wrote:
> Hi
>
> On Mon, Aug 19, 2019 at 7:38 AM Jonas Bonn <[email protected]> wrote:
>> The kernel log has this:
>>
>> Aug 17 08:51:46 solar kernel: usb 1-1: USB disconnect, device number 3
>> Aug 17 08:51:46 solar kernel: option1 ttyUSB0: GSM modem (1-port)
>> converter now disconnected from ttyUSB0
>> Aug 17 08:51:46 solar kernel: option 1-1:1.0: device disconnected
>> Aug 17 08:51:46 solar kernel: option1 ttyUSB1: GSM modem (1-port)
>> converter now disconnected from ttyUSB1
>> Aug 17 08:51:46 solar kernel: option 1-1:1.2: device disconnected
>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: nonzero urb status
>> received: -71
>>
>> That's a USB communication failure!
>>
>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback - 0 bytes
>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback -
>> usb_submit_urb failed with result -19
>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3 wwan0: unregister
>> 'qmi_wwan' usb-ci_hdrc.1-1, WWAN/QMI device
>>
>> Below, the device (modem) is reenumerated, which would indicate to me
>> that it has restarted. I don't think the kernel automatically sends a
>> reset to a device on comm failures...??? This explains the
>> communication failure, at least.
>
> Can be chattering and rush current? Even are you sure that you don't have
> some reset our of the ofono service that send an at command that
> restart the modem?
Just to try to prevent us from going down the wrong rabbit hole here:
i) The modem is a QMI device so there are no AT commands being sent
ii) The ofono log should show any such command if it were being
transmitted (unfortunately, JH hasn't been able to produce a proper log
around this event, yet)
iii) I'm pretty certain that the QMI (gobi) driver in ofono doesn't
support any 'reset' command
My inclination would be to look elsewhere.
i) figure out what reset signalling the modem does and put a scope on it.
ii) try to eliminate ofono and connman from the picture entirely by
running the modem manually... what's the utility called, qmictl? comes
with libqmi, in any case. Presumably, if it's a hardware issue, the
problem will show itself under these circumstances, as well.
/Jonas
>
> Michael
>
>>
>> Aug 17 08:51:49 solar kernel: usb 1-1: new high-speed USB device number
>> 4 using ci_hdrc
>> Aug 17 08:51:50 solar kernel: usb 1-1: New USB device found,
>> idVendor=05c6, idProduct=90b2, bcdDevice= 0.00
>> Aug 17 08:51:50 solar kernel: usb 1-1: New USB device strings: Mfr=3,
>> Product=2, SerialNumber=4
>> Aug 17 08:51:50 solar kernel: usb 1-1: Product: Qualcomm CDMA
>> Technologies MSM
>> Aug 17 08:51:50 solar kernel: usb 1-1: Manufacturer: Qualcomm, Incorporated
>> Aug 17 08:51:50 solar kernel: usb 1-1: SerialNumber: 5ff10299
>> Aug 17 08:51:50 solar kernel: option 1-1:1.0: GSM modem (1-port)
>> converter detected
>> Aug 17 08:51:50 solar kernel: usb 1-1: GSM modem (1-port) converter now
>> attached to ttyUSB0
>> Aug 17 08:51:50 solar kernel: option 1-1:1.2: GSM modem (1-port)
>> converter detected
>> Aug 17 08:51:50 solar kernel: usb 1-1: GSM modem (1-port) converter now
>> attached to ttyUSB1
>> Aug 17 08:51:50 solar kernel: qmi_wwan 1-1:1.3: cdc-wdm0: USB WDM device
>> Aug 17 08:51:50 solar kernel: qmi_wwan 1-1:1.3 wwan0: register
>> 'qmi_wwan' at usb-ci_hdrc.1-1, WWAN/QMI device, f6:0d:90:fa:af:24
>>
>> ofono should _definitely_ show this device reenumeration in its logs.
>> Why is that not there???
>>
>> -----------------------
>>
>> Subsequently, the kernel log shows:
>>
>> Aug 17 11:32:43 solar kernel: usb 1-1: USB disconnect, device number 4
>> Aug 17 11:32:43 solar kernel: option1 ttyUSB0: GSM modem (1-port)
>> converter now disconnected from ttyUSB0
>> Aug 17 11:32:43 solar kernel: option 1-1:1.0: device disconnected
>> Aug 17 11:32:43 solar kernel: option1 ttyUSB1: GSM modem (1-port)
>> converter now disconnected from ttyUSB1
>> Aug 17 11:32:43 solar kernel: option 1-1:1.2: device disconnected
>> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3: nonzero urb status
>> received: -71
>>
>> Again, comm error.
>>
>> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback - 0 bytes
>> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback -
>> usb_submit_urb failed with result -19
>> Aug 17 11:32:44 solar kernel: qmi_wwan 1-1:1.3 wwan0: unregister
>> 'qmi_wwan' usb-ci_hdrc.1-1, WWAN/QMI device
>>
>> Modem has rebooted and is reenumerated below.
>>
>> Aug 17 11:32:44 solar kernel: usb 1-1: new high-speed USB device number
>> 5 using ci_hdrc
>> Aug 17 11:32:45 solar kernel: usb 1-1: New USB device found,
>> idVendor=05c6, idProduct=90b2, bcdDevice= 0.00
>> Aug 17 11:32:45 solar kernel: usb 1-1: New USB device strings: Mfr=1,
>> Product=2, SerialNumber=3
>> Aug 17 11:32:45 solar kernel: usb 1-1: Product: QHSUSB__BULK
>> Aug 17 11:32:45 solar kernel: usb 1-1: Manufacturer: Qualcomm CDMA
>> Technologies MSM
>> Aug 17 11:32:45 solar kernel: usb 1-1: SerialNumber: 5ff10299
>> Aug 17 11:32:45 solar kernel: option 1-1:1.0: GSM modem (1-port)
>> converter detected
>> Aug 17 11:32:45 solar kernel: usb 1-1: GSM modem (1-port) converter now
>> attached to ttyUSB0
>>
>> Here, however, the modem isn't booting up into normal operational state,
>> but rather into some other configuration that, presumably, is intended
>> for doing device firmware updates...
>>
>> So you have a couple of things to figure out:
>> i) Why is the modem restarting (crashing) spontaneously?
>> ii) What are the conditions for entering the bootloader/firmware update
>> state? How are you managing to meet these conditions?
>> iii) Why is ofono not showing the device reenumeration... it should,
>> and it should show the modem being taken down and brought back up again.
>> (I suspect it's just a matter of your logs being out of sync... it's
>> probably there if you look, again).
>>
>>>
>>> Let me further clarify it, the issue did not occur very often, it
>>> occurred randomly between hours to many days, that is a big worry, LTE
>>> should be 100% stable.
>>
>> The issue doesn't seem to have anything to do with the radio link. The
>> LTE is probably stable; the issue lies elsewhere.
>>
>> /Jonas
>>
>>>
>>> Thank you.
>>>
>>> Kind regards,
>>>
>>> - jh
>>>
>
>
>
------------------------------
Message: 3
Date: Mon, 19 Aug 2019 09:56:14 +0200
From: Jonas Bonn <[email protected]>
To: Michael Nazzareno Trimarchi <[email protected]>
Cc: JH <[email protected]>, connman <[email protected]>,
Giacinto Cifelli <[email protected]>, Daniel Wagner <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: Unsalble cellular connection
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
On 19/08/2019 09:50, Jonas Bonn wrote:
>
>
> On 19/08/2019 09:36, Michael Nazzareno Trimarchi wrote:
>> Hi
>>
>> On Mon, Aug 19, 2019 at 7:38 AM Jonas Bonn <[email protected]> wrote:
>>> The kernel log has this:
>>>
>>> Aug 17 08:51:46 solar kernel: usb 1-1: USB disconnect, device number 3
>>> Aug 17 08:51:46 solar kernel: option1 ttyUSB0: GSM modem (1-port)
>>> converter now disconnected from ttyUSB0
>>> Aug 17 08:51:46 solar kernel: option 1-1:1.0: device disconnected
>>> Aug 17 08:51:46 solar kernel: option1 ttyUSB1: GSM modem (1-port)
>>> converter now disconnected from ttyUSB1
>>> Aug 17 08:51:46 solar kernel: option 1-1:1.2: device disconnected
>>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: nonzero urb status
>>> received: -71
>>>
>>> That's a USB communication failure!
>>>
>>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback - 0
>>> bytes
>>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3: wdm_int_callback -
>>> usb_submit_urb failed with result -19
>>> Aug 17 08:51:46 solar kernel: qmi_wwan 1-1:1.3 wwan0: unregister
>>> 'qmi_wwan' usb-ci_hdrc.1-1, WWAN/QMI device
>>>
>>> Below, the device (modem) is reenumerated, which would indicate to me
>>> that it has restarted.? I don't think the kernel automatically sends a
>>> reset to a device on comm failures...???? This explains the
>>> communication failure, at least.
>>
>> Can be chattering and rush current? Even are you sure that you don't have
>> some reset our of the ofono service that send an at command that
>> restart the modem?
>
> Just to try to prevent us from going down the wrong rabbit hole here:
> i)? The modem is a QMI device so there are no AT commands being sent
> ii)? The ofono log should show any such command if it were being
> transmitted (unfortunately, JH hasn't been able to produce a proper log
> around this event, yet)
> iii)? I'm pretty certain that the QMI (gobi) driver in ofono doesn't
> support any 'reset' command
>
> My inclination would be to look elsewhere.
>
> i)? figure out what reset signalling the modem does and put a scope on it.
> ii)? try to eliminate ofono and connman from the picture entirely by
> running the modem manually... what's the utility called, qmictl?? comes
> with libqmi, in any case.? Presumably, if it's a hardware issue, the
> problem will show itself under these circumstances, as well.
>
Is the problem reproducible with the EVK? If not, you've pretty much
eliminated software as the cause of the issue... it's the same device,
but with an independent power supply.
/Jonas
------------------------------
Message: 4
Date: Mon, 19 Aug 2019 10:17:33 +0200
From: Jonas Bonn <[email protected]>
To: Michael Nazzareno Trimarchi <[email protected]>, JH
<[email protected]>
Cc: "[email protected]" <[email protected]>, connman
<[email protected]>
Subject: Re: Unsalble cellular connection
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Michael,
Re-adding JH and mailing lists to conversation...
On 19/08/2019 10:00, Michael Nazzareno Trimarchi wrote:
> Hi
>
> On Mon, Aug 19, 2019 at 9:51 AM Jonas Bonn <[email protected]> wrote:
>>
>>
>>
>> On 19/08/2019 09:36, Michael Nazzareno Trimarchi wrote:
>>> Can be chattering and rush current? Even are you sure that you don't have
>>> some reset our of the ofono service that send an at command that
>>> restart the modem?
>>
>> Just to try to prevent us from going down the wrong rabbit hole here:
>> i) The modem is a QMI device so there are no AT commands being sent
>
> Ok, so the uart used as ttyUSB0 and ttyUSB1 they don't support any AT command?
> Is qmi part only the network interface?
ttyUSB0 and ttyUSB1 _do_ support AT commands, but are complementary to
the QMI interface which is a complete communication channel to the modem
in itself. The network interface is _only_ for the QMI channel: the
network packets are carried on a dedicated endpoint of the USB interface
supporting QMI.
I think the question of QMI vs AT is moot here. Internally the modem
does pretty much the same thing; it's just the interface that looks a
bit different.
In JH's case, only the 'qmimisc' device and the 'network' interface are
in play via ofono. These are separate endpoints on a single USB
interface, all managed by the qmi-wwan driver in the kernel.
/Jonas
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 46, Issue 19
***************************************
