We are experiencing a weird behaviour with our RUTX50s on several vessels in the Baltic. We had multiple occasions of the routers locking up in case the LTE connection was weak or broke down (offshore when there was no network). Symptoms:
Devices could not connect through Wifi (the Wifi connection failed to establish during the handshake).
Ethernet connections would also not establish (no DHCP assignment happened; if address assigned manually, a connect via HTTP would fail, a connect through SSH would pass sshd but then get kicked as Busybox would fail to start).
Only a reboot would resolve the situation. However, in case the connection issues to the LTE network persist, the router would lock up again with the symptoms above within minutes.
Because the router can‘t be connected to, we are unfortunately not able to retrieve „live“ logs.
Could you please confirm whether the routers have been kept in a fully protected environment with no possibility of water ingress?
Also, did the described behavior only start appearing recently, or has it been present since the devices were first installed?
How are the routers powered? What power supplies are being used? Please ensure they meet the 18 W requirement.
Furthermore, make sure the devices are running either the latest firmware (7.17) or the current stable release (7.15.4). When possible, please also provide the current internal modem firmware version from one of the affected units.
Please find some additional information below as requested:
Yes, absolutely, no water ingress. The devices are installed in a protected environment in line with their IP class and we have checked that there have been no issues.
Router firmware: RUTX_R_00.07.16.3
Modem firmware: RG501QEUAAR12A11M4G
The appeared for the first time three weeks ago. However, the SIM, network and roaming situation has changed as well (we now use a Norwegian SIM for Norway as opposed to the T-Mobile cards which we used for roaming).
Power is provided by a 12-24V Victron isolating DC-DC converter able to provide 4A. Other devices, neither on the 12V nor the 24V, were experiencing any issues.
In addition, I now have been able to access the router when it was in a “locked” state.
I am pasting a syslog excerpt below. You will see that a kernel warning is showing up repeatedly. Also, RAM usage was at the upper limit. I was however not able to issue a ps or top to see where the RAM consumption emerges from. I can send you more of this by PM.
22164 Thu Aug 14 11:21:36 2025 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,14 --release-client-id wds
22165 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): udhcpc: SIOCGIFINDEX: No such device
22166 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): udhcpc: received SIGTERM
22167 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): udhcpc: unicasting a release of 10.152.5.225 to 10.152.5.226
22168 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): udhcpc: sending release
22169 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): udhcpc: can't bind to interface qmimux0: No such device
22170 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): udhcpc: bindtodevice: No such device
22171 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): udhcpc: entering released state
22172 Thu Aug 14 11:21:36 2025 daemon.notice netifd: mob1s2a1_4 (2341): Command failed: Permission denied
22173 Thu Aug 14 11:21:36 2025 daemon.notice netifd: Interface 'mob1s2a1_4' is now down
22174 Thu Aug 14 11:21:37 2025 user.notice qmux: Stopping network on device: /dev/cdc-wdm0 cid: 15
22175 Thu Aug 14 11:21:37 2025 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,15 --stop-network 0xFFFFFFFF --autoconnect
22176 Thu Aug 14 11:21:37 2025 user.notice qmux: Freeing cid: 15
22177 Thu Aug 14 11:21:37 2025 user.notice netifd: uqmi -s -d /dev/cdc-wdm0 -t 3000 --set-client-id wds,15 --release-client-id wds
22178 Thu Aug 14 11:21:39 2025 user.notice qmux: mob1s2a1 teardown successful
22179 Thu Aug 14 13:21:40 2025 cron.err crond[5444]: time disparity of 120 minutes detected
22180 Thu Aug 14 13:21:47 2025 kern.notice DNS resolution started to fail
22181 Thu Aug 14 13:22:16 2025 kern.err kernel: [150759.589295] rcu: INFO: rcu_sched self-detected stall on CPU
22182 Thu Aug 14 13:22:16 2025 kern.err kernel: [150759.589360] rcu: 0-....: (5999 ticks this GP) idle=173c/1/0x40000002 softirq=3125500/3125506 fqs=2816
22183 Thu Aug 14 13:22:16 2025 kern.err kernel: [150759.594056] rcu: (t=6000 jiffies g=7415761 q=17574 ncpus=4)
22184 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.603170] CPU: 0 PID: 4103 Comm: cat Tainted: G O 6.6.92 #0
22185 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.609069] Hardware name: Generic DT based system
22186 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.616184] PC is at dev_fetch_sw_netstats+0x50/0xf4
22187 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.620958] LR is at dev_fetch_sw_netstats+0x34/0xf4
22188 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.626164] pc : [<c088e74c>] lr : [<c088e730>] psr: 00000013
22189 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.631202] sp : c15fbb50 ip : 00000001 fp : 00000000
22190 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.637622] r10: 00000000 r9 : 00000000 r8 : 00000000
22191 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.642917] r7 : 00000000 r6 : c0e050ac r5 : 00000000 r4 : c725d918
22192 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.648215] r3 : 0000000f r2 : ff7de6a0 r1 : 00000004 r0 : 00000001
22193 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.654555] Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
22194 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.661153] Control: 10c5387d Table: 85a2406a DAC: 00000051
22195 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.668448] dev_fetch_sw_netstats from dev_get_stats+0x3c/0x128
22196 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.674260] dev_get_stats from rtnl_fill_stats+0x30/0x118
22197 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.680422] rtnl_fill_stats from rtnl_fill_ifinfo+0x704/0x12d4
22198 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.685805] rtnl_fill_ifinfo from rtmsg_ifinfo_build_skb+0xb8/0x13c
22199 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.692057] rtmsg_ifinfo_build_skb from unregister_netdevice_many_notify+0x410/0x81c
22200 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.698394] unregister_netdevice_many_notify from unregister_netdevice_queue+0xa0/0x104
22201 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.706208] unregister_netdevice_queue from qmimux_start_xmit+0x4ac/0x4e8 [qmi_wwan]
22202 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.714455] qmimux_start_xmit [qmi_wwan] from del_mux_store+0x58/0xb0 [qmi_wwan]
22203 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.722267] del_mux_store [qmi_wwan] from kernfs_fop_write_iter+0x114/0x1cc
22204 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.729817] kernfs_fop_write_iter from do_iter_readv_writev+0xac/0x100
22205 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.737023] do_iter_readv_writev from do_iter_write+0x78/0x1fc
22206 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.743792] do_iter_write from iter_file_splice_write+0x23c/0x384
22207 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.749781] iter_file_splice_write from direct_splice_actor+0x34/0x48
22208 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.755770] direct_splice_actor from splice_direct_to_actor+0xc4/0x28c
22209 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.762368] splice_direct_to_actor from do_splice_direct+0xa0/0xc8
22210 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.769310] do_splice_direct from do_sendfile+0x2e0/0x470
22211 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.775647] do_sendfile from sys_sendfile64+0xe0/0x100
22212 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.780944] sys_sendfile64 from ret_fast_syscall+0x0/0x54
22213 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.786497] Exception stack(0xc15fbfa8 to 0xc15fbff0)
22214 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.791798] bfa0: 01000000 00000000 00000001 00000003 00000000 01000000
22215 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.797010] bfc0: 01000000 00000000 00000003 000000ef 00000001 00000003 00000001 00000000
22216 Thu Aug 14 13:22:16 2025 kern.warn kernel: [150759.805255] bfe0: 00480f34 bedf1b84 0045a9ec b6f12204
Thank you for the update. In this case, to assist and troubleshoot this matter effectively, we’ll need to continue this process privately, because sensitive/publicly unshareable information, such as the troubleshoot file, public IP addresses, serial numbers, etc., needs to be gathered. You should find a support request form in the inbox of the email address you used for your forum registration. Kindly fill out the form, and please reference Ticket ID: 15100 when submitting it. Once the form is completed, we’ll contact you directly via email to investigate the issue in detail and help work towards a solution.