From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============7681269258808527588==" MIME-Version: 1.0 From: Jonas Bonn Subject: Re: Unsalble cellular connection Date: Mon, 19 Aug 2019 07:38:29 +0200 Message-ID: In-Reply-To: List-Id: To: ofono@ofono.org --===============7681269258808527588== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi JH, On 19/08/2019 03:51, JH wrote: > Hi Michael, > = > On 8/18/19, Michael Nazzareno Trimarchi = 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=3D05c6, idProduct=3D90b2, bcdDevice=3D 0.00 >> Aug 17 11:32:45 solar kernel: usb 1-1: New USB device strings: Mfr=3D1, >> Product=3D2, SerialNumber=3D3 >> 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. 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=3D05c6, idProduct=3D90b2, bcdDevice=3D 0.00 Aug 17 08:51:50 solar kernel: usb 1-1: New USB device strings: Mfr=3D3, = Product=3D2, SerialNumber=3D4 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=3D05c6, idProduct=3D90b2, bcdDevice=3D 0.00 Aug 17 11:32:45 solar kernel: usb 1-1: New USB device strings: Mfr=3D1, = Product=3D2, SerialNumber=3D3 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 >=20 --===============7681269258808527588==--