I am not familiar with this device or its source, but the negative numbers correspond to errors EPROTO and ENODEV, the 34:08:03 seems to be off-by-one from the BSSID you connect to... It would be helpful to know the kernel version, and model/versions of the hardware and firmware-- likely you can get the info by grepping dmesg/kmsg for qmi and mwifi. lspci and lsusb -vt might also be useful info. Seems like the modem is a subsystem of the 1-1:1.0 device that is though. I have a qmi modem and it changes bConfigurationValue parameter which causes it to reset and present different interfaces (qmi vs mbim if i recall correctly), perhaps something is making that change... ModemManager? Have a look in /sys/kernel/modules/ there should be some sort of *qmi*/parameters/ where you can maybe change the debug flag (alternatively you could modinfo qmi_wwan, assuming that is the right module, and rmmod it, and modprobe the_qmi-module the_debug_parameter=0xfffffff) Sorry this is sort of a generic response, and I know not the most useful, but others would likely benefit from additional info too, and time allowing I'll poke around in the code to try and come up with some ideas On Fri, Jan 24, 2020 at 5:10 PM JH <jupiter.hce@xxxxxxxxx> wrote: > > Hi, > > I have been running mwifiex_sdio for a uBlox 4G LTE SARA-R4 and Lily > WiFi module, it seems that WiFi connection is stable, but the LTE > connection is often connected and disconnected. > > Looking into the kernel messages, there were many messages to > disconnect and connect it again every half of an hour. The device did > not set IPv6 which is understandably that IPv6: ADDRCONF(NETDEV_UP) > link is not ready, but why it often doing mwifiex_sdio mmc0:0001:1: > info: successfully disconnected from 34:08:03 and what that means? > > root@solar:/var/backups# [ 2045.955013] mwifiex_sdio mmc0:0001:1: > CMD_RESP: cmd 0x23f error, result=0x2 > > root@solar:/var/backups# [ 2250.000008] mwifiex_sdio mmc0:0001:1: > info: successfully disconnected from 34:08:03 > [ 2250.081497] IPv6: ADDRCONF(NETDEV_UP): mlan0: link is not ready > [ 2250.206977] IPv6: ADDRCONF(NETDEV_UP): wwan0: link is not ready > [ 2251.417295] mwifiex_sdio mmc0:0001:1: info: trying to associate to > 'JupiterIoT' bssid 34:08:04:12:b1:a2 > [ 2251.521866] mwifiex_sdio mmc0:0001:1: info: associated to bssid > 34:08:04:12:b1:a2 successfully > [ 2251.666834] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready > [ 2251.743352] mwifiex_sdio mmc0:0001:1: CMD_RESP: cmd 0x23f error, result=0x2 > > > Also, the 4G LTE SARA-R4 uses USB interface and protocol, but it seems > to me that mwifiex_sdio managers both LTE and WiFi connections, right? > > I am currently debugging the LTE connection stability issues, it > ofoten connected to LTE, then in half hours or hours randomly, lose > the LTE connection. I try to narrow down the cause, whether the USB > interface or from mwifiex_sdio caused LTE connection stability. When > the LTE lost connection there were following errors which I am not > clear if related to the mwifiex_sdio or not. Appreciate your advise > and comments to diagnostic the issue and to fix the LTE connection > problems. > > 1019.130834] option 1-1:1.0: device disconnected > [ 1019.142012] qmi_wwan 1-1:1.3: nonzero urb status received: -71 > [ 1019.147909] qmi_wwan 1-1:1.3: wdm_int_callback - 0 bytes > [ 1019.153254] qmi_wwan 1-1:1.3: wdm_int_callback - usb_submit_urb > failed with result -19 > [ 1019.228197] option1 ttyUSB1: GSM modem (1-port) converter now > disconnected from ttyUSB1 > > Thank you. > > Kind regards, > > - jh
