Re: --firmware-list crashes modemmanager?
Hey, > > > Surprising; I'm kind of sure there is a crash when running > > --firmware-list command. I'm using Sierra EM7430 in MBIM mode. qmicli > > output is below. What is your configuration? > > > I'm using a Sierra EM7565 in QMI mode on OpenWrt. There's only one > image installed. The qmicli output matches the mmcli output: > > root@wrt1900ac-1:~# qmicli -p -d /dev/cdc-wdm0 --dms-list-stored-images > [/dev/cdc-wdm0] Device list of stored images retrieved: > > [0] Type:'modem' > Maximum: '4' > > [modem0] > Unique ID: '?_?' > Build ID: '01.09.04.00_?' > Storage index: '1' > Failure count: '0' > > [1] Type:'pri' > Maximum: '50' > > >> [CURRENT] << > [pri0] > Unique ID: '002.019_000' > Build ID: '01.09.04.00_GENERIC' > > > > I guess the MBIM vs QMI difference is the important point here. I > didn't know ModemManager supported firmware management in MBIM mode? Or > maybe it doesn't, but bugs out for some reason? > MM doesn't current support firmware image management in MBIM mode (although it could for QMI-capable MBIM modems...). This totally looks like MM may be crashing due to some unexpected error somewhere. Amol, could you build with debug symbols and run under gdb to see if we can catch a proper trace when MM crashes? -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: --firmware-list crashes modemmanager?
Amol Lad writes: > Surprising; I'm kind of sure there is a crash when running > --firmware-list command. I'm using Sierra EM7430 in MBIM mode. qmicli > output is below. What is your configuration? I'm using a Sierra EM7565 in QMI mode on OpenWrt. There's only one image installed. The qmicli output matches the mmcli output: root@wrt1900ac-1:~# qmicli -p -d /dev/cdc-wdm0 --dms-list-stored-images [/dev/cdc-wdm0] Device list of stored images retrieved: [0] Type:'modem' Maximum: '4' [modem0] Unique ID: '?_?' Build ID: '01.09.04.00_?' Storage index: '1' Failure count: '0' [1] Type:'pri' Maximum: '50' >> [CURRENT] << [pri0] Unique ID: '002.019_000' Build ID: '01.09.04.00_GENERIC' I guess the MBIM vs QMI difference is the important point here. I didn't know ModemManager supported firmware management in MBIM mode? Or maybe it doesn't, but bugs out for some reason? I'm using an EM7455 in MBIM mode in my laptop (Debian on x86_64), and mmcli fails to list any images there - without crashing: bjorn@miraculix:~$ mmcli -m 2 --firmware-list error: couldn't list firmware images: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Unsupported: Cannot list firmware: operation not supported' This is with a current master branch snapshot, so I guess there are some fixes since the 1.12 release used in OpenWrt. Or maybe the problem related to handling dbus call errors in OpenWrt? Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
RE: --firmware-list crashes modemmanager?
Surprising; I'm kind of sure there is a crash when running --firmware-list command. I'm using Sierra EM7430 in MBIM mode. qmicli output is below. What is your configuration? root@OpenWrt:/# qmicli -d /dev/cdc-wdm0 -p --dms-list-stored-images [/dev/cdc-wdm0] Device list of stored images retrieved: [0] Type:'modem' Maximum: '4' [modem0] Unique ID: '?_?' Build ID: '02.30.03.00_?' Storage index: '1' Failure count: '0' >>>>>>>>>> [CURRENT] <<<<<<<<<< [modem1] Unique ID: '?_?' Build ID: '02.20.03.01_?' Storage index: '2' Failure count: '0' [modem2] Unique ID: '?_?' Build ID: '02.20.03.00_?' Storage index: '3' Failure count: '0' [modem3] Unique ID: '?_?' Build ID: '02.24.05.06_?' Storage index: '4' Failure count: '0' [1] Type:'pri' Maximum: '50' [pri0] Unique ID: '001.026_001' Build ID: '02.30.03.00_DOCOMO' >>>>>>>>>> [CURRENT] <<<<<<<<<< [pri1] Unique ID: '002.046_001' Build ID: '02.30.03.00_GENERIC' [pri2] Unique ID: '001.023_001' Build ID: '02.30.03.00_KDDI' [pri3] Unique ID: '001.024_000' Build ID: '02.30.03.00_Softbank' [pri4] Unique ID: '002.044_000' Build ID: '02.30.03.00_TELSTRA' The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).-Original Message- From: Bjørn Mork Sent: Friday, 15 November 2019 8:21 PM To: Amol Lad Cc: Aleksander Morgado ; modemmanager-devel@lists.freedesktop.org Subject: Re: --firmware-list crashes modemmanager? Amol Lad writes: > root@OpenWrt:/# mmcli -m 0 --firmware-list > error: couldn't list firmware images: > 'GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient > disconnected from message bus without replying' Odd. Works for me: root@wrt1900ac-1:/# mmcli -m 0 --firmware-list Firmware | list: 01.09.04.00_GENERIC_002.019_000 | current: yes | gobi pri unique id: 002.019_000 | gobi modem unique id: ?_? Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: --firmware-list crashes modemmanager?
Amol Lad writes: > root@OpenWrt:/# mmcli -m 0 --firmware-list > error: couldn't list firmware images: > 'GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient > disconnected from message bus without replying' Odd. Works for me: root@wrt1900ac-1:/# mmcli -m 0 --firmware-list Firmware | list: 01.09.04.00_GENERIC_002.019_000 | current: yes | gobi pri unique id: 002.019_000 | gobi modem unique id: ?_? Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
--firmware-list crashes modemmanager?
Hi Aleksander, It seems "mmcli -m 0 -firmware-list" is crashing modemmanager. There is no debug output also in -debug mode. Please see last two commands in bottom of this email. I'm running MM 1.12.0 (in openwrt) root@OpenWrt:/# mmcli -m 0 General |dbus path: /org/freedesktop/ModemManager1/Modem/0 |device id: 1f75cd7f52f1f8d71fed0aeb735b4c9c28e3b338 Hardware | manufacturer: Sierra Wireless, Incorporated |model: Sierra Wireless EM7430 Qualcomm(r) Snapdragon(tm) X7 LTE-A |firmware revision: SWI9X30C_02.30.03.00 | carrier config: default | h/w revision: EM7430 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 359075062306476 System | device: /sys/devices/platform/soc/soc:internal-regs/f10f8000.usb3/usb5/5-1 | drivers: qcserial, cdc_mbim | plugin: Sierra | primary port: cdc-wdm0 |ports: ttyUSB0 (qcdm), ttyUSB1 (gps), ttyUSB2 (at), | cdc-wdm0 (mbim), wwan0 (net) Numbers | own: 9108813566 Status | unlock retries: sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 0% (recent) Modes|supported: allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 3g, 4g; preferred: 3g | allowed: 3g, 4g; preferred: 4g | current: allowed: 4g; preferred: none Bands|supported: utran-1, utran-6, utran-5, utran-8, utran-9, eutran-1, | eutran-3, eutran-5, eutran-7, eutran-8, eutran-18, eutran-19, | eutran-21, eutran-28, eutran-38, eutran-39, eutran-40, eutran-41, | utran-19 | current: eutran-1, eutran-3, eutran-5, eutran-7, eutran-8, | eutran-18, eutran-19, eutran-21, eutran-28, eutran-38, eutran-39, | eutran-40, eutran-41 IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 359075062306476 |enabled locks: fixed-dialing | operator id: 40445 |operator name: airtel | registration: home 3GPP EPS | ue mode of operation: csps-2 SIM |dbus path: /org/freedesktop/ModemManager1/SIM/0 Bearer |dbus path: /org/freedesktop/ModemManager1/Bearer/0 root@OpenWrt:/# mmcli -m 0 --firmware-list error: couldn't list firmware images: 'GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying' root@OpenWrt:/# mmcli -m 0 error: couldn't find modem at '/org/freedesktop/ModemManager1/Modem/0' The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it). ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
