CBA850 frequently reboots

[willow]

I have a CBA850 with LP6 modem and I'm using a Visible SIM. I have updated the router firmware to 7.0.50 and the modem firmware for Verizon to 02.30.01.01_VERIZON,002.052_000. For the most part, it works, but frequently, it will reboot and I can't figure out why. The log only shows events starting with the current reboot. I do have a fairly weak signal:

Signal Strength 82
RSSI -84 dBm
SINR 9.2 dB
RSRP -112 dB
RSRQ -10 dB'

Could that be the cause? If not, does anyone have any suggestions for determining the problem?

Many thanks!

[JimHelms]

Signals are not the best but I have seen worse.

What reboots, the modem or the router?

Do you have the Default Connection State as Always On?

I have seen instances where the modem would no idle and the software would reboot the modem to reactivate the connection.

[willow]

Thanks for the reply!

It's the router that's rebooting... it drops its connection to the web UI, signal strength lights turn off, main light turns amber, etc. I was actively using/testing the internet connection, so I'd assume that that the modem would not have had a chance to go idle.

I figured out how to enable USB logging, but it didn't reveal anything (that I could see), Here's a sample:

3646 user.info WAN:9aa0bec9.AutoAPNFront: Connected
3646 user.info WAN:9aa0bec9.CPPM: Connecting device
3646 user.info cp_stack_mgr: INFO simctrl.c(2394) modem1: simctrl_data_open()
3646 user.info cp_stack_mgr: INFO simctrl.c(1939) modem1: simctrl_handle_open() attempting connect of active sim
3646 user.info cp_stack_mgr: INFO simctrl_ifc_shim.c( 322) modem1: simctrl_shim_protocol_info_ifc_get_info()
3646 user.info cp_stack_mgr: INFO cp_stack_manager.c( 862) modem1: cp_stack_manager_get_signal_strength() - not configured yet
3646 user.info cp_stack_mgr: INFO cp_stack_manager.c( 827) modem1: cp_stack_manager_update_diagnostics() - not yet configured
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1535) modem1: lte_sierra_data_open_process() step:150, instance: 0
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1535) modem1: lte_sierra_data_open_process() step:151, instance: 0
3646 user.info cp_stack_mgr: INFO gsm.c(1330) modem1: modem_gsm_is_APN_configuration_needed() - APN configuration NOT needed
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1535) modem1: lte_sierra_data_open_process() step:158, instance: 0
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1535) modem1: lte_sierra_data_open_process() step:159, instance: 0
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1814) modem1: lte_sierra_data_open_process() ----- exiting with step=160, resl=1
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1413) modem1: lte_sierra_attach_process() step: 286, status: 0, instance: 0
3646 user.info WAN:9aa0bec9: Connect Event: processing - state: connecting
3646 user.info cp_stack_mgr: WARN wan_manager_linux.c(2147):wan_manager_parse_cb() adding APN1 -> vzwims, IPV4V6
3646 user.info cp_stack_mgr: WARN wan_manager_linux.c(2147):wan_manager_parse_cb() adding APN2 -> vzwadmin, IPV4V6
3646 user.info cp_stack_mgr: WARN wan_manager_linux.c(2147):wan_manager_parse_cb() adding APN3 -> VSBLINTERNET, IPV4V6
3646 user.info cp_stack_mgr: WARN wan_manager_linux.c(2147):wan_manager_parse_cb() adding APN4 -> vzwapp, IPV4V6
3646 user.info cp_stack_mgr: WARN wan_manager_linux.c(2147):wan_manager_parse_cb() adding APN5 -> vzw800, IPV4V6
3646 user.info cp_stack_mgr: WARN wan_manager_linux.c(2147):wan_manager_parse_cb() adding APN6 -> VSBLINTERNET, IPV4V6
3646 user.info WAN:9aa0bec9.CPPM: state=connecting result=processing
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1413) modem1: lte_sierra_attach_process() step: 287, status: 0, instance: 0
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1441) modem1: lte_sierra_attach_process() ok: 1, power: 1
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1413) modem1: lte_sierra_attach_process() step: 291, status: 0, instance: 0
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1535) modem1: lte_sierra_data_open_process() step:160, instance: 0
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1535) modem1: lte_sierra_data_open_process() step:161, instance: 0
3646 user.info cp_stack_mgr: INFO lte_sierra.c(1814) modem1: lte_sierra_data_open_process() ----- exiting with step=162, resl=1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:41, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:42, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:43, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:44, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2807) modem1: modem_common_qmi_data_open_process() ----- exiting with step:45, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:45, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:46, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:47, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:48, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:49, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:50, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2807) modem1: modem_common_qmi_data_open_process() ----- exiting with step:51, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:51, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:52, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2171) modem1: modem_common_qmi_data_open_process() step:53, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(2807) modem1: modem_common_qmi_data_open_process() ----- exiting with step:54, instance: 0, status: 0, resl: 1
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(1341) modem1: modem_common_qmi_data_register_process() step:74, status:0
3646 user.info cp_stack_mgr: INFO modem_common_qmi.c(1341) modem1: modem_common_qmi_data_register_process() step:81, status:0
3647 user.info cp_stack_mgr: INFO modem_common_qmi.c(1341) modem1: modem_common_qmi_data_register_process() step:82, status:0
3647 user.info cp_stack_mgr: INFO modem_common_qmi.c(1726) modem1: modem_common_qmi_data_register_process() - READY: reg:1 and (cs:2 or ps:1) - MCC:311, MNC:480
3647 user.info cp_stack_mgr: INFO cp_stack_manager.c( 862) modem1: cp_stack_manager_get_signal_strength() - not configured yet
3647 user.info cp_stack_mgr: INFO cp_stack_manager.c( 827) modem1: cp_stack_manager_update_diagnostics() - not yet configured
3648 user.info cp_stack_mgr: INFO modem_common_qmi.c(1341) modem1: modem_common_qmi_data_register_process() step:81, status:0
3648 user.info cp_stack_mgr: INFO modem_common_qmi.c(1341) modem1: modem_common_qmi_data_register_process() step:82, status:0
3648 user.info cp_stack_mgr: INFO modem_common_qmi.c(1726) modem1: modem_common_qmi_data_register_process() - READY: reg:1 and (cs:2 or ps:1) - MCC:311, MNC:480
3648 user.info cp_stack_mgr: INFO cp_stack_manager.c( 862) modem1: cp_stack_manager_get_signal_strength() - not configured yet
3648 user.info cp_stack_mgr: INFO cp_stack_manager.c( 827) modem1: cp_stack_manager_update_diagnostics() - not yet configured
3606 syslog.info syslogd started: BusyBox v1.24.1
3606 kern.notice kernel: klogd started: BusyBox v1.24.1 (2019-03-25 16:18:22 UTC)

[JimHelms]

When you upgraded the router software to 7.0.50, did you check the box to reset the router to default factory settings?

Just to eliminate the software being the issue, I would download a fresh software image and reflash the CBA850 again, and be sure to set the router to factory defaults.

What power adapter are you using?

[willow]

I've reset to factory settings and re-flashed the firmware a couple of times already. The power supply is something I had not considered (its a cheap 12v 2A - Model LX-1202). A bad one would perfectly explain what I've been experiencing! I've got another one. I'll try it out for a couple of days and see what happens. Many thanks! Merry Christmas!

[JimHelms]

A faulty power supply as well as one with the improper 2.5mm (as opposed to 2.1mm) barrel tip connector can and will cause issues.