Yes, whenever that I lost connection (Ethernet) to DHCP server (BPI-R3), my PC would pop up a warning, thats the time I noticed. I barely pay attention on Wifi on my phone, as it is connected to a dump AP (Redmi AX6000) but not BPI-R3.
I can’t do anything after lost connection, can’t do ssh, ping to server (192.168.0.1), only thing I can do is to power circle the BPI-R3 for a reboot.
May I ask where can I report the issue?
Already updated the issue report on the topic I created in Openwrt forum.
Meanwhile, I will go back to the commit where it was running straight for a month without disconnection as @dangowrt instructed, see if the disconnection & high memory usage issues still persist.
It is a lengthy process for rebuild, test commits, I will report back whenever there is a valuable update & findings…
So system is completely stalled and defined as this…not wifi related (mt76 repo)
Can you provide a link? It should be here: https://github.com/openwrt/openwrt/issues
oh, i posted it as a forum topic here.
Will report on OpenWrt git as well, thank you for point this out. The link is here. https://github.com/openwrt/openwrt/issues/12143
I would put the trace (lines “cut here” till “end of trace”) directly in the report,so not everyone needs to download logfile. This avoids bug posted again with same error because message was not found by search
yea, no problem and thanks for the suggestion, will update the report.
I think I may found some clue (see below), but still need longer time for conclusion.
I re-flashed to latest commit (on that day) r22253-89390a9e50
Discard all existing settings during firmware update, and reconfig only whats neccessary (Wifi, firewall, samba4 share, adblock) I used to keep settings for each firmware upgrade due to laziness to reconfigure all over again.
After 2 days 11 hours, no issue and everything is stable, even the high memory usage is gone, stable 200+MB consumption. It looks like some leftover from add-on package which (I didn’t aware of) caused issue.
Will keep this updated after more testing time.
UPDATE (fresh configuration after upgrade by not saving existing settings):
Running smooth and no more disconnection for up to 4 days already.
Previous high memory usage (up to 97% or 1.8GB used) is also gone, now stable consume about 200MB.
After 5 days of smooth running without said issues, I think I should mark this topic as SOLVED.
[SOLUTION:] Re-flashed the firmware, discarded all existing settings.
Well… 5 days is not long enough IMO. Keep an eye on this for at least a month or so.
Thanks, the said issue would occur about 2 days after a fresh boot before.
Now its straight for 13 days without disconnection or kernel crash, still check and counting the uptime.
Well, what a coincidence. Just when you commented and I thought 13 days of smooth operation would prove the issue has gone, it occurred again just 20min ago.
Same like before, lost all DHCP clients. cannot Ping, SSH to server.
Thu Mar 23 22:30:51 2023 kern.warn kernel: [1164017.939720] ------------[ cut here ]------------
Thu Mar 23 22:30:51 2023 kern.info kernel: [1164017.944517] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 3 timed out
Thu Mar 23 22:30:51 2023 kern.warn kernel: [1164017.951656] WARNING: CPU: 2 PID: 0 at dev_watchdog+0x330/0x33c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164017.957655] Modules linked in: iptable_mangle iptable_filter ipt_REJECT ipt_ECN ip_tables xt_time xt_tcpudp xt_tcpmss xt_statistic xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_ecn xt_dscp xt_comment xt_TCPMSS xt_LOG xt_HL xt_DSCP xt_CLASSIFY x_tables sch_cake sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred act_gact ifb pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt76_connac_lib mt76 mac80211 cfg80211 slhc sfp nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 mdio_i2c libcrc32c crc_ccitt compat crypto_safexcel pwm_fan
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164017.957807] hwmon i2c_gpio i2c_algo_bit nvme nvme_core autofs4 sha1_generic seqiv md5 des_generic libdes authencesn authenc leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd xhci_hcd gpio_button_hotplug usbcore usb_common
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.064271] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.15.98 #0
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.070433] Hardware name: Bananapi BPI-R3 (DT)
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.075118] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.082232] pc : dev_watchdog+0x330/0x33c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.086403] lr : dev_watchdog+0x330/0x33c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.090570] sp : ffffffc008c0bdb0
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.094042] x29: ffffffc008c0bdb0 x28: 0000000000000140 x27: 00000000ffffffff
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.101332] x26: 0000000000000000 x25: 0000000000000002 x24: ffffff80009224c0
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.108620] x23: 0000000000000000 x22: 0000000000000001 x21: ffffffc008ad6000
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.115909] x20: ffffff8000922000 x19: 0000000000000003 x18: ffffffc008aea2e0
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.123198] x17: ffffffc0770ed000 x16: ffffffc008c0c000 x15: 0000000000000798
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.130487] x14: 0000000000000288 x13: ffffffc008c0bad8 x12: ffffffc008b422e0
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.137776] x11: 712074696d736e61 x10: ffffffc008b422e0 x9 : 0000000000000000
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.145065] x8 : ffffffc008aea290 x7 : ffffffc008aea2e0 x6 : 0000000000000001
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.152353] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.159642] x2 : 0000000000000040 x1 : 0000000000000004 x0 : 000000000000003f
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.166931] Call trace:
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.169536] dev_watchdog+0x330/0x33c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.173358] call_timer_fn.constprop.0+0x20/0x80
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.178133] __run_timers.part.0+0x208/0x284
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.182560] run_timer_softirq+0x38/0x70
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.186639] _stext+0x10c/0x28c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.189940] __irq_exit_rcu+0xdc/0xfc
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.193762] irq_exit+0xc/0x1c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.196976] handle_domain_irq+0x60/0x8c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.201059] gic_handle_irq+0x50/0x120
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.204969] call_on_irq_stack+0x28/0x44
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.209050] do_interrupt_handler+0x4c/0x54
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.213389] el1_interrupt+0x2c/0x4c
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.217124] el1h_64_irq_handler+0x14/0x20
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.221378] el1h_64_irq+0x74/0x78
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.224937] arch_cpu_idle+0x14/0x20
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.228672] do_idle+0xc0/0x150
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.231976] cpu_startup_entry+0x20/0x60
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.236056] secondary_start_kernel+0x130/0x140
Thu Mar 23 22:30:51 2023 kern.debug kernel: [1164018.240743] __secondary_switched+0x50/0x54
Thu Mar 23 22:30:51 2023 kern.warn kernel: [1164018.245084] ---[ end trace de2befc368436867 ]---
Thu Mar 23 22:30:51 2023 kern.err kernel: [1164018.249870] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Thu Mar 23 22:30:51 2023 kern.info kernel: [1164018.388360] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Thu Mar 23 22:30:52 2023 kern.err kernel: [1164018.919988] mtk_soc_eth 15100000.ethernet: warm reset failed
Thu Mar 23 22:30:52 2023 kern.info kernel: [1164018.938997] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Thu Mar 23 22:30:52 2023 kern.info kernel: [1164018.947550] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/2500base-x link mode
Thu Mar 23 22:30:52 2023 kern.info kernel: [1164018.947561] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Thu Mar 23 22:30:57 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 9c:e3:3f:66:4b:0a
Thu Mar 23 22:30:57 2023 daemon.info hostapd: phy1-ap0: STA 9c:e3:3f:66:4b:0a IEEE 802.11: disassociated
Thu Mar 23 22:30:58 2023 daemon.info hostapd: phy1-ap0: STA 9c:e3:3f:66:4b:0a IEEE 802.11: authenticated
Thu Mar 23 22:30:58 2023 daemon.info hostapd: phy1-ap0: STA 9c:e3:3f:66:4b:0a IEEE 802.11: associated (aid 1)
Thu Mar 23 22:30:58 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 9c:e3:3f:66:4b:0a auth_alg=open
Thu Mar 23 22:30:58 2023 daemon.info hostapd: phy1-ap0: STA 9c:e3:3f:66:4b:0a WPA: pairwise key handshake completed (RSN)
Thu Mar 23 22:30:58 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 9c:e3:3f:66:4b:0a
Thu Mar 23 22:30:59 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.211 9c:e3:3f:66:4b:0a
Thu Mar 23 22:30:59 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.211 9c:e3:3f:66:4b:0a jemima
Thu Mar 23 22:31:12 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar 23 22:31:12 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar 23 22:31:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.118 04:68:65:8b:ee:f8 James-iPhone
Thu Mar 23 22:31:17 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:17 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.118 04:68:65:8b:ee:f8 James-iPhone
Thu Mar 23 22:31:19 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:19 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.118 04:68:65:8b:ee:f8 James-iPhone
Thu Mar 23 22:31:21 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:21 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.248 08:c7:29:b4:34:26 Mitchs-iPhone
Thu Mar 23 22:31:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.248 08:c7:29:b4:34:26 Mitchs-iPhone
Thu Mar 23 22:31:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 04:68:65:8b:ee:f8
Thu Mar 23 22:31:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:24 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 04:68:65:8b:ee:f8
Thu Mar 23 22:31:24 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:25 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:25 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.248 08:c7:29:b4:34:26 Mitchs-iPhone
Thu Mar 23 22:31:27 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 04:68:65:8b:ee:f8
Thu Mar 23 22:31:27 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:29 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 08:c7:29:b4:34:26
Thu Mar 23 22:31:29 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:31 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 08:c7:29:b4:34:26
Thu Mar 23 22:31:31 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:31 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 04:68:65:8b:ee:f8
Thu Mar 23 22:31:31 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:33 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 08:c7:29:b4:34:26
Thu Mar 23 22:31:33 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:38 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 08:c7:29:b4:34:26
Thu Mar 23 22:31:38 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:39 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 04:68:65:8b:ee:f8
Thu Mar 23 22:31:39 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:39 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 9c:e3:3f:66:4b:0a
Thu Mar 23 22:31:39 2023 daemon.info hostapd: phy1-ap0: STA 9c:e3:3f:66:4b:0a IEEE 802.11: disassociated
Thu Mar 23 22:31:41 2023 daemon.info hostapd: phy1-ap0: STA 9c:e3:3f:66:4b:0a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Mar 23 22:31:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.118 04:68:65:8b:ee:f8 James-iPhone
Thu Mar 23 22:31:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 08:c7:29:b4:34:26
Thu Mar 23 22:31:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:48 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.118 04:68:65:8b:ee:f8
Thu Mar 23 22:31:48 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.118 04:68:65:8b:ee:f8 James-iPhone
Thu Mar 23 22:31:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.248 08:c7:29:b4:34:26 Mitchs-iPhone
Thu Mar 23 22:31:51 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar 23 22:31:51 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.248 08:c7:29:b4:34:26 Mitchs-iPhone
Thu Mar 23 22:31:52 2023 kern.warn kernel: [1164079.100621] page_pool_release_retry() stalled pool shutdown 28 inflight 60 sec
I used a USB to Serial adapter to access Openwrt after lost all clients, did ‘/etc/init.d/network restart’ but not help bring back the connection. REBOOT is the only solution.
The latest commit (or commit after Feb, 2023) really has some issues.
Flashed to latest commit OpenWrt SNAPSHOT r22387-47de2c6862, running for 2 days then lost connection again. This time, the Ping, ssh, and even Luci is still accessible, the clients retained their assigned IP but just lost upstream connection (Internet).
Tue Mar 28 08:48:10 2023 kern.warn kernel: [258902.740244] ------------[ cut here ]------------
Tue Mar 28 08:48:10 2023 kern.info kernel: [258902.744949] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 3 timed out
Tue Mar 28 08:48:10 2023 kern.warn kernel: [258902.752008] WARNING: CPU: 0 PID: 0 at dev_watchdog+0x330/0x33c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.757915] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mt7915e mt76_connac_lib mt76 mac80211 cfg80211 slhc sfp nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 mdio_i2c libcrc32c crc_ccitt compat crypto_safexcel fuse pwm_fan hwmon i2c_gpio i2c_algo_bit nvme nvme_core autofs4 sha1_generic seqiv md5 des_generic libdes authencesn authenc leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd xhci_hcd gpio_button_hotplug usbcore usb_common
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.829449] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.102 #0
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.835610] Hardware name: Bananapi BPI-R3 (DT)
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.840208] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.847236] pc : dev_watchdog+0x330/0x33c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.851316] lr : dev_watchdog+0x330/0x33c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.855395] sp : ffffffc008003db0
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.858780] x29: ffffffc008003db0 x28: 0000000000000140 x27: 00000000ffffffff
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.865983] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff80009214c0
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.873184] x23: 0000000000000000 x22: 0000000000000001 x21: ffffffc008ad6000
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.880386] x20: ffffff8000921000 x19: 0000000000000003 x18: ffffffc008aea2e0
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.887588] x17: ffffffc0770cb000 x16: ffffffc008004000 x15: 0000000000000681
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.894789] x14: 000000000000022b x13: ffffffc008003ad8 x12: ffffffc008b422e0
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.901991] x11: 712074696d736e61 x10: ffffffc008b422e0 x9 : 0000000000000000
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.909193] x8 : ffffffc008aea290 x7 : ffffffc008aea2e0 x6 : 0000000000000001
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.916394] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.923594] x2 : ffffff807fb89080 x1 : ffffffc0770cb000 x0 : 000000000000003f
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.930798] Call trace:
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.933316] dev_watchdog+0x330/0x33c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.937048] call_timer_fn.constprop.0+0x20/0x80
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.941736] __run_timers.part.0+0x208/0x284
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.946075] run_timer_softirq+0x38/0x70
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.950068] _stext+0x10c/0x28c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.953280] __irq_exit_rcu+0xdc/0xfc
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.957015] irq_exit+0xc/0x1c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.960142] handle_domain_irq+0x60/0x8c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.964137] gic_handle_irq+0x50/0x120
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.967958] call_on_irq_stack+0x28/0x44
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.971952] do_interrupt_handler+0x4c/0x54
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.976204] el1_interrupt+0x2c/0x4c
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.979853] el1h_64_irq_handler+0x14/0x20
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.984019] el1h_64_irq+0x74/0x78
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.987491] arch_cpu_idle+0x14/0x20
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.991138] do_idle+0xc0/0x150
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.994355] cpu_startup_entry+0x20/0x60
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258902.998347] rest_init+0xc4/0xd0
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258903.001648] arch_call_rest_init+0xc/0x14
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258903.005729] start_kernel+0x5b4/0x5d4
Tue Mar 28 08:48:10 2023 kern.debug kernel: [258903.009461] __primary_switched+0xa0/0xa8
Tue Mar 28 08:48:10 2023 kern.warn kernel: [258903.013542] ---[ end trace 333227c911159d38 ]---
Tue Mar 28 08:48:10 2023 kern.err kernel: [258903.018249] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Tue Mar 28 08:48:10 2023 kern.info kernel: [258903.157617] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Tue Mar 28 08:48:11 2023 kern.err kernel: [258903.690323] mtk_soc_eth 15100000.ethernet: warm reset failedHello, forum! I’m having the same problem as jtxnn678 and a very similar system log from luci as the one from the last message. I have 23.05.3 release installed, two wi-fi networks (AX and 2.4N) and a 400 Mbit/s connection from ISP via cat5e. I have also installed adblock and have set up a bunch of filters. Otherwise the system is pretty much stock System was forking fine for about a month, but after some time I now have basically two types of issues happening randomly: either both wifi networks are UP, but clients have no internet, or there’s no wifi at all. I have only wirelessly connected devices, haven’t yet tried to connect the router with a cable or serial and dump logs when wifi shuts off. What might be causing such problems? I wanted to make a clean install discarding previous configs, but decided to search for an answer here first.
It seems like the adblock with a lot of filters enabled was the reason why I was getting this type of behavior. I’ve disabled and uninstalled adblock completely, made iptables -F and rebooted my router. After that i haven’t faced any problems with my wifi for a day, before that my R3 was sort of “crashing” every 2 to 3 hours with a reboot needed for it to work normally again.
Right now i’ve made a clean install of 23.05.3 and have also changed PWM fan settings on my official BPi heatsink to always work on 100% power (before that it wasn’t working at all). Haven’t had any problems since
Well, after reinstallation everything was working fine for some time, but 10 minutes ago the same problem happened again. There was no load on my network whatsoever, all connected devices were idling (not downloading or uploading anything), and suddenly internet connection was lost everywhere. All the clients stayed connected to the BPI-R3 hotspot, but none of them had internet. I checked RAM usage - it was roughly 160-170 Mb (same as always). Tried pinging 8.8.8.8 from LuCI - 5 sent 0 received. After the reboot everything is working fine again
Here is a cut from system long (was taken under LuCI):
Fri Jun 14 23:15:59 2024 kern.warn kernel: [433649.660692] ------------[ cut here ]------------
Fri Jun 14 23:15:59 2024 kern.info kernel: [433649.665396] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 3 timed out
Fri Jun 14 23:15:59 2024 kern.warn kernel: [433649.672456] WARNING: CPU: 2 PID: 0 at 0xffffffc0086c46d4
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.677838] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack_netlink nf_conntrack mt7915e mt76_connac_lib mt76 mac80211 iptable_mangle iptable_filter ipt_REJECT ipt_ECN ip_tables cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_ecn xt_dscp xt_comment xt_TCPMSS xt_LOG xt_HL xt_DSCP xt_CLASSIFY x_tables slhc sfp sch_cake nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 mdio_i2c libcrc32c compat crypto_safexcel sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred act_gact pwm_fan i2c_gpio
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.677985] i2c_algo_bit ifb sha1_generic seqiv md5 des_generic libdes authencesn authenc leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd xhci_hcd gpio_button_hotplug usbcore usb_common aquantia crc_ccitt
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.783315] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.15.150 #0
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.789475] Hardware name: Bananapi BPI-R3 (DT)
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.794074] pstate: 40400005 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.801101] pc : 0xffffffc0086c46d4
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.804659] lr : 0xffffffc0086c46d4
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.808218] sp : ffffffc008b6bdb0
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.811602] x29: ffffffc008b6bdb0 x28: 0000000000000140 x27: 00000000ffffffff
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.818804] x26: 0000000000000000 x25: 0000000000000002 x24: ffffff8000c804c0
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.826006] x23: 0000000000000000 x22: 0000000000000001 x21: ffffffc008a36000
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.833208] x20: ffffff8000c80000 x19: 0000000000000003 x18: ffffffc008a4a2a8
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.840410] x17: ffffffc07718c000 x16: ffffffc008b68000 x15: 00000000000003e7
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.847611] x14: 000000000000014d x13: ffffffc008b6bae8 x12: ffffffc008aa22a8
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.854813] x11: 712074696d736e61 x10: ffffffc008aa22a8 x9 : 0000000000000000
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.862015] x8 : ffffffc008a4a258 x7 : ffffffc008a4a2a8 x6 : 0000000000000001
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.869216] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.876418] x2 : ffffff807fbaa090 x1 : ffffffc07718c000 x0 : 000000000000003f
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.883620] Call trace:
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.886138] 0xffffffc0086c46d4
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.889350] 0xffffffc0080a5c50
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.892562] 0xffffffc0080a64c8
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.895773] 0xffffffc0080a6e18
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.898984] 0xffffffc0080102bc
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.902195] 0xffffffc00803b280
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.905406] 0xffffffc00803b3a0
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.908617] 0xffffffc008089564
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.911829] 0xffffffc0080100e0
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.915041] 0xffffffc00801584c
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.918253] 0xffffffc00801614c
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.921464] 0xffffffc008834770
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.924675] 0xffffffc008834f24
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.927887] 0xffffffc008011374
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.931098] 0xffffffc008835504
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.934310] 0xffffffc008069390
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.937522] 0xffffffc0080695a0
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.940733] 0xffffffc00801ebe0
Fri Jun 14 23:15:59 2024 kern.debug kernel: [433649.943945] 0xffffffc00883e2cc
Fri Jun 14 23:15:59 2024 kern.warn kernel: [433649.947157] ---[ end trace 7c4a7a868cc49fa6 ]---
It seems like the same error as @jtxnn678 had. @jtxnn678 maybe you have solved this problem in any way? Any advices?
P.S. I have an official heatsink with fan installed, it’s always running on 100%, so i think that this issue is not thermal related
I had disconnection issues both on cable and WiFi, seems solved since I disabled 160Mhz channel width. Not sure it is the same issue but you can make an attempt.
Had you also the transmit timeouts? So maybe frequencies from wifi interfere with ethenet…
I need to check but it seems related with Wifi channels. Using 80Mhz on 5g band and fixed channel seems solving anything.