Hi,
Posted this on the mangOH forums, but also posting here as we haven’t received a reply and this issue is turning into a massive show stopper for us. If anyone can help us understand this problem that would be extremely helpful.
We’re seeing an issue on our mangOH Red units that shutdown for unexplained reasons. Here is a crash log we were able to extract.
Nov 5 17:31:31 swi-mdm9x28 user.warn kernel: [ 61.011285] irq 50, desc: cefdb000, depth: 0, count: 0, unhandled: 0
Nov 5 17:31:31 swi-mdm9x28 user.warn kernel: [ 61.011308] ->handle_irq(): c025ac68, msm_gpio_irq_handler+0x0/0x150
Nov 5 17:31:31 swi-mdm9x28 user.warn kernel: [ 61.011338] ->irq_data.chip(): c0ed8e68, gic_chip+0x0/0x74
Nov 5 17:31:31 swi-mdm9x28 user.warn kernel: [ 61.011361] ->action(): (null)
Nov 5 17:31:31 swi-mdm9x28 user.warn kernel: [ 61.011372] IRQ_NOPROBE set
Nov 5 17:31:31 swi-mdm9x28 user.warn kernel: [ 61.011383] IRQ_NOREQUEST set
Nov 5 17:31:31 swi-mdm9x28 user.warn kernel: [ 61.011394] IRQ_NOTHREAD set
Nov 5 17:31:32 swi-mdm9x28 user.info kernel: [ 62.443635] gpio_check_and_wake: wake-n_gpio26 STATE=WAKEUP
Nov 5 17:31:32 swi-mdm9x28 user.info kernel: [ 62.465129] gpio_check_and_wake: wake-n_gpio26 STATE=SLEEP
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: qmi_at_unsol_ind_cb: ind id:33
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: Received AT command forward request from modem
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: fwdcmd.opcode=1
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: fwdcmd.name=$QCPWRDN
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: fwdcmd.ntokens=0
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: ctrCond signalling complete.
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: Recieved ctrCond: p: 0, S:0, nr: 1
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: QCPWRDN has been detected
Nov 5 17:31:33 swi-mdm9x28 user.warn kernel: [ 63.685455] PSM: Modem oprt mode - 3
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: sending QMI_AT_FWD_RESP_AT_CMD_RESP_V01 message
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: qmi_client_send_raw_msg_sync returned: 0
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: New request processing complete.
Nov 5 17:31:33 swi-mdm9x28 user.info swiapp: Waiting for ctrCond
Nov 5 17:31:33 swi-mdm9x28 daemon.info init: starting pid 1755, tty '': '/etc/init.d/rcK'
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.872044] gpio_check_and_wake: wake-n_gpio26 STATE=WAKEUP
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.879719] swimcu_device_init: start 0x7ff
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.883297] swimcu_device_init: mcufw ver=2.009 target=1 opt=0xF
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.887979] swimcu_device_init: success
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.895223] swimcu_set_fault_mask: 0x100, cnt 1
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.895241] swimcu reset_recovery: complete
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.895250] swimcu_set_reset_source: 0x40
Nov 5 17:31:33 swi-mdm9x28 user.info kernel: [ 63.895271] gpio_check_and_wake: wake-n_gpio26 STATE=SLEEP
Does anyone know what QCPWRDN means, and why it would cause a random shutdown?
cm info details:
root@swi-mdm9x28:~# cm info
Device: WP7603-1
IMEI: 351711090107910
IMEISV: 4
FSN: WD752585161410
Firmware Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
Bootloader Version: SWI9X07Y_02.16.02.00 000000 jenkins 2018/04/19 19:59:02
MCU Version: 002.009
PRI Part Number (PN): 9907595
PRI Revision: 001.004
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.032_000
SKU: 1103727
Last Reset Cause: Power Down
Resets Count: Expected: 248 Unexpected: 2
Legato version
root@swi-mdm9x28:~# legato version
18.06.1_302932300e810a4fb0cba7b4960af4fd