Crash of FW update service

Hi,

We are facing this problem during FOTA upgrade process, after calling, le_fwupdate_Install() was not responding for some time, then system went crashing.

92816 2023/10/07 16:04:30.349000 906.9342 156 ATB4 SYS SYSL 0 log info verbose 1 <30>Oct 7 08:03:10 CoredumpHandler: Moving coredump from /var/volatile/core_tmp/core.1696665786.mm_mw_swu_ota_mgr.1766.gz to /var/volatile/core/core.1696665786.mm_mw_swu_ota_mgr.1766.gz
92817 2023/10/07 16:04:30.349000 906.9348 157 ATB4 SYS SYSL 0 log info verbose 1 <30>Oct 7 08:03:10 CoredumpHandler: Moving coredump from /var/volatile/core_tmp/context.1696665786.mm_mw_swu_ota_mgr.1766.txt to /var/volatile/core/context.1696665786.mm_mw_swu_ota_mgr.1766.txt
92818 2023/10/07 16:04:30.349000 906.9354 158 ATB4 SYS SYSL 0 log info verbose 1 <30>Oct 7 08:03:10 CoredumpHandler: Crash in "mm_mw_swu_ota_mgr", thread="mm_mw_swu_ota_m", pid=1766, crashID=03a4000001a40050, based on signal=5, PC=0x4a30, caller=0x4a10
92819 2023/10/07 16:04:30.349000 906.9448 159 ATB4 SYS SYSL 0 log info verbose 1 <14>Oct 7 08:03:10 Legato: INFO | supervisor[1115]/supervisor T=main | proc.c proc_SigChildHandler() 2092 | Process 'mm_mw_swu_ota_mgr' (PID: 1766) has exited due to signal 5 (Trace/breakpoint trap).
92820 2023/10/07 16:04:30.349000 907.0534 160 ATB4 SYS SYSL 0 log info verbose 1 <12>Oct 7 08:03:10 Legato: -WRN- | supervisor[1115]/supervisor T=main | app.c app_SigChildHandler() 3950 | Process 'mm_mw_swu_ota_mgr' in app 'mm_mw_swu_ota_mgr' faulted: Ignored.
92821 2023/10/07 16:04:30.349000 907.0871 161 ATB4 SYS SYSL 0 log info verbose 1 <12>Oct 7 08:03:10 Legato: -WRN- | _appStopClient[2128]/framework T=main | LE_FILENAME CreateSocket() 550 | Socket opened as standard i/o file descriptor 2!
92822 2023/10/07 16:04:30.349000 907.0964 162 ATB4 SYS SYSL 0 log info verbose 1 <14>Oct 7 08:03:10 Legato: INFO | supervisor[1115]/supervisor T=main | app.c app_StopComplete() 4621 | app 'mm_mw_swu_ota_mgr' has stopped.

mm_mw_swu_ota_mgr is the application that takes care of the upgrade process.

  1. Could you help us to understand why the system will crash under the mechanim of Legato supervisor.
  2. How can we prevent this from happening again?

Your prompt response is highly appreciated.

BR,
Louis

Are you using FOTA by your own server or AVMS?

Hi,

Using our own server, but the issue happened after the firmware downloaded and validation phase has passed succesfully.

BR,
Louis

If you redo fwupdate command, will it work?

Which firmware are you upgrading from and to?

Hi,

The system has already crashed, there is nothing we can do about it, board had become unresponsive and had to be flashed by wire to recover.

BR,
Louis

Which firmware are you upgrading from and to?

Hi,

Are you referring to Legato version? If so, we have been using legato-18.08.0, it is still the same version, no change there. Apart from that, we are upgrading the modem and applications.

BR,
Louis

I am referring to the module FW.
For example, if your original FW is R10, and then you upgrade to FW R16.
I would suggest you do testing on official FW first instead your custom FW to isolate factors

Hi,

On the module FW perspective, the baseline version is the same before/after the upgrade. Additionally, the issue is not 100% systematic, it happened just a few time.

The purpose is to come up with a solution to avoid this, and to achieve that, we need to figure out why le_fwupdate_Install() not responding, and how does that turn into a system crash?

Could you please advice?

Thanks a lot!

BR,
Louis

I assume you are using WP76.

if you are using legato-18.08, first of all, this is not legato version of any official release.
Next, this legato version is around the corresponding FW between R10 and R12.
It is already very old FW.
I would suggest you retry on some newer FW like R16 or R17.