Bananapi BPI-R3 periodic disconnect all clients

Please note this bug: https://github.com/openwrt/mt76/issues/729

Thank you frank, Iā€™ve also read your note in another topic. In such case, it proves that my case isnā€™t temperate related, if the output from sensors command is higher than the actual reading. I got 50c average through 48hrs of logging record, only a spike up to 82c on 2.4Ghz for less than a minute, way far from the threshold.

Try to sort your top/htop on memory usage. I donā€™t think this is sorted by mem usage.

EDIT: Also VSZ is virtual memory, it doesnā€™t say much. We need to look into RSS memory.

Hope this one is helpful. I updated to latest snapshot, try to see if the memory usage would still reach high percentage after few days. Screenshot_2023-03-08_233407-01 Here is the screenshot, hope it helps.

wellā€¦ nowā€¦ itā€™s not 98% memory usage anymoreā€¦ Itā€™s using 200Mb.

Anyway, use the same htop command and the same ordering by RES column, whenever it reaches that high memory consumption again.

That being said, if 1% memory is used by dnsmaq process, that would be 20 Mb + .8% + .6% + 2x .2% + 10x .1 = 1% = ~ 65 Mb. Letā€™s round up to 80 Mb. Adding the rest of process shouldnā€™t really add up to 200Mbm, but more like 80Mb. Iā€™m I right? Where is letā€™s say the remaining ~120MB being allocated towards?

I could be correctā€¦ just thinking out loud. Anyway, keep us posted when itā€™s 99% memory again!

That was after upgraded to latest snapshot & rebooted, the previous firmware was also using around 200MiB after fresh reboot, but 97% after 4 days of running. I will monitor the mem usage and give update.

Disconnection just happened again after running for about 12hrs from fresh reboot.

Complete log since the ERROR:

Thu Mar  9 12:37:44 2023 kern.warn kernel: [53627.423716] ------------[ cut here ]------------
Thu Mar  9 12:37:44 2023 kern.info kernel: [53627.428339] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 6 timed out
Thu Mar  9 12:37:44 2023 kern.warn kernel: [53627.435303] WARNING: CPU: 1 PID: 0 at dev_watchdog+0x330/0x33c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.441127] 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 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
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.512141] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.98 #0
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.518129] Hardware name: Bananapi BPI-R3 (DT)
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.522641] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.529581] pc : dev_watchdog+0x330/0x33c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.533576] lr : dev_watchdog+0x330/0x33c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.537569] sp : ffffffc00800bdb0
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.540867] x29: ffffffc00800bdb0 x28: 0000000000000140 x27: 00000000ffffffff
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.547984] x26: 0000000000000000 x25: 0000000000000001 x24: ffffff8000e394c0
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.555098] x23: 0000000000000000 x22: 0000000000000001 x21: ffffffc008ad6000
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.562213] x20: ffffff8000e39000 x19: 0000000000000006 x18: ffffffc008aea2e0
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.569328] x17: ffffffc0770dc000 x16: ffffffc00800c000 x15: 00000000000005c7
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.576444] x14: 00000000000001ed x13: ffffffc00800bad8 x12: ffffffc008b422e0
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.583560] x11: 712074696d736e61 x10: ffffffc008b422e0 x9 : 0000000000000000
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.590676] x8 : ffffffc008aea290 x7 : ffffffc008aea2e0 x6 : 0000000000000001
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.597791] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.604905] x2 : 0000000000000040 x1 : 0000000000000004 x0 : 000000000000003f
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.612021] Call trace:
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.614453]  dev_watchdog+0x330/0x33c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.618100]  call_timer_fn.constprop.0+0x20/0x80
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.622701]  __run_timers.part.0+0x208/0x284
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.626954]  run_timer_softirq+0x38/0x70
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.630859]  _stext+0x10c/0x28c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.633986]  __irq_exit_rcu+0xdc/0xfc
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.637635]  irq_exit+0xc/0x1c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.640676]  handle_domain_irq+0x60/0x8c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.644585]  gic_handle_irq+0x50/0x120
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.648320]  call_on_irq_stack+0x28/0x44
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.652227]  do_interrupt_handler+0x4c/0x54
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.656393]  el1_interrupt+0x2c/0x4c
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.659956]  el1h_64_irq_handler+0x14/0x20
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.664037]  el1h_64_irq+0x74/0x78
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.667422]  arch_cpu_idle+0x14/0x20
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.670983]  do_idle+0xc0/0x150
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.674113]  cpu_startup_entry+0x20/0x60
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.678019]  secondary_start_kernel+0x130/0x140
Thu Mar  9 12:37:44 2023 kern.debug kernel: [53627.682532]  __secondary_switched+0x50/0x54
Thu Mar  9 12:37:44 2023 kern.warn kernel: [53627.686701] ---[ end trace 23a15a9fb18fbfa4 ]---
Thu Mar  9 12:37:44 2023 kern.err kernel: [53627.691307] mtk_soc_eth 15100000.ethernet eth0: transmit timed out
Thu Mar  9 12:37:44 2023 kern.info kernel: [53627.830536] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Thu Mar  9 12:37:44 2023 kern.err kernel: [53628.373625] mtk_soc_eth 15100000.ethernet: warm reset failed
Thu Mar  9 12:37:44 2023 kern.info kernel: [53628.392404] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Thu Mar  9 12:37:44 2023 kern.info kernel: [53628.400792] mtk_soc_eth 15100000.ethernet eth1: configuring for inband/2500base-x link mode
Thu Mar  9 12:37:44 2023 kern.info kernel: [53628.400805] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Thu Mar  9 12:38:14 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 08:c7:29:b4:34:26
Thu Mar  9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: disassociated
Thu Mar  9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: authenticated
Thu Mar  9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 IEEE 802.11: associated (aid 1)
Thu Mar  9 12:38:14 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 08:c7:29:b4:34:26 auth_alg=open
Thu Mar  9 12:38:14 2023 daemon.info hostapd: phy1-ap0: STA 08:c7:29:b4:34:26 WPA: pairwise key handshake completed (RSN)
Thu Mar  9 12:38:14 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 08:c7:29:b4:34:26
Thu Mar  9 12:38:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.248 08:c7:29:b4:34:26
Thu Mar  9 12:38:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.248 08:c7:29:b4:34:26 Mitchs-iPhone
Thu Mar  9 12:39:06 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:06 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar  9 12:39:25 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:25 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:32 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:32 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:57 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:39:57 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:11 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:11 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar  9 12:40:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:15 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:19 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:19 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:27 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:27 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:44 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:44 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:56 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:56 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar  9 12:40:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:40:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:00 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:00 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:04 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:04 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:13 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:29 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:29 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:41 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:41 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar  9 12:41:43 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:43 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:45 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:45 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:49 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:41:58 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:42:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:42:14 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:44:35 2023 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 04:68:65:8b:ee:f8
Thu Mar  9 12:44:35 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: disassociated
Thu Mar  9 12:44:37 2023 daemon.info hostapd: phy1-ap0: STA 04:68:65:8b:ee:f8 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Mar  9 12:47:18 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:47:18 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC
Thu Mar  9 12:47:20 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:47:20 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:47:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:47:23 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 12:51:37 2023 daemon.info hostapd: phy1-ap0: STA 48:87:59:12:c3:a3 IEEE 802.11: authenticated
Thu Mar  9 12:51:37 2023 daemon.info hostapd: phy1-ap0: STA 48:87:59:12:c3:a3 IEEE 802.11: associated (aid 2)
Thu Mar  9 12:51:37 2023 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 48:87:59:12:c3:a3 auth_alg=open
Thu Mar  9 12:51:37 2023 daemon.info hostapd: phy1-ap0: STA 48:87:59:12:c3:a3 WPA: pairwise key handshake completed (RSN)
Thu Mar  9 12:51:37 2023 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.148 48:87:59:12:c3:a3
Thu Mar  9 12:51:40 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.148 48:87:59:12:c3:a3 2201116SG
Wed Mar  8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: No sensors found!
Wed Mar  8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Make sure you loaded all the kernel drivers you need.
Wed Mar  8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Try sensors-detect to find out which these are.
Wed Mar  8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: No sensors found!
Wed Mar  8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Make sure you loaded all the kernel drivers you need.
Wed Mar  8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S95done: Try sensors-detect to find out which these are.
Wed Mar  8 23:27:11 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Wed Mar  8 23:27:11 2023 daemon.info samba4-server: io_uring module found, enabling VFS io_uring. (also needs Kernel 5.4+ Support)
Wed Mar  8 23:27:11 2023 daemon.notice procd: /etc/rc.d/S99transmission: Transmission not enabled. Please enable in /etc/config/transmission
Wed Mar  8 23:27:11 2023 daemon.info transmission: Transmission not enabled. Please enable in /etc/config/transmission
Wed Mar  8 23:27:11 2023 daemon.info procd: - init complete -
Wed Mar  8 23:27:13 2023 daemon.notice netifd: wan (2613): udhcpc: broadcasting select for 192.168.1.2, server 192.168.1.1
Wed Mar  8 23:27:13 2023 daemon.notice netifd: wan (2613): udhcpc: lease of 192.168.1.2 obtained from 192.168.1.1, lease time 86400
Wed Mar  8 23:27:13 2023 daemon.notice netifd: Interface 'wan' is now up
Wed Mar  8 23:27:13 2023 user.notice firewall: Reloading firewall due to ifup of wan (br-wan)
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: started, version 2.89 cachesize 1000
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.0.100 -- 192.168.0.249, lease time 1h
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using nameserver 192.168.1.1#53
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: using only locally-known addresses for lan
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 10 names
Wed Mar  8 23:27:14 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534).
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Successfully dropped root privileges.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: avahi-daemon 0.8 starting up.
Thu Mar  9 13:00:10 2023 daemon.warn avahi-daemon[3566]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: No service file found in /etc/avahi/services.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-wan.IPv6 with address fe80::6826:f2ff:fe1a:acc9.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-wan.IPv6 for mDNS.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-wan.IPv4 with address 192.168.1.2.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-wan.IPv4 for mDNS.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-lan.IPv6 with address fdc1:bfda:51a1::1.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-lan.IPv6 for mDNS.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface br-lan.IPv4 with address 192.168.0.1.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface br-lan.IPv4 for mDNS.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::6826:f2ff:fe1a:acc8.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface eth0.IPv6 for mDNS.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface lo.IPv6 for mDNS.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: New relevant interface lo.IPv4 for mDNS.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Network interface enumeration completed.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for fe80::6826:f2ff:fe1a:acc9 on br-wan.*.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for 192.168.1.2 on br-wan.IPv4.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for fdc1:bfda:51a1::1 on br-lan.*.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for 192.168.0.1 on br-lan.IPv4.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for fe80::6826:f2ff:fe1a:acc8 on eth0.*.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for ::1 on lo.*.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering new address record for 127.0.0.1 on lo.IPv4.
Thu Mar  9 13:00:10 2023 daemon.info avahi-daemon[3566]: Registering HINFO record with values 'AARCH64'/'LINUX'.
Thu Mar  9 13:00:11 2023 daemon.info avahi-daemon[3566]: Server startup complete. Host name is OpenWrt-Bananapi-BPI-R3.local. Local service cookie is 1296436648.
Thu Mar  9 13:00:16 2023 daemon.err nmbd[3166]: [2023/03/09 13:00:16.715866,  0] ../../source3/nmbd/nmbd.c:901(main)
Thu Mar  9 13:00:16 2023 daemon.err nmbd[3166]:   nmbd version 4.17.2 started.
Thu Mar  9 13:00:16 2023 daemon.err nmbd[3166]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Thu Mar  9 13:00:17 2023 daemon.err smbd[3165]: [2023/03/09 13:00:17.023557,  0] ../../source3/smbd/server.c:1741(main)
Thu Mar  9 13:00:17 2023 daemon.err smbd[3165]:   smbd version 4.17.2 started.
Thu Mar  9 13:00:17 2023 daemon.err smbd[3165]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Thu Mar  9 13:00:39 2023 daemon.err nmbd[3166]: [2023/03/09 13:00:39.751780,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Thu Mar  9 13:00:39 2023 daemon.err nmbd[3166]:   *****
Thu Mar  9 13:00:39 2023 daemon.err nmbd[3166]:
Thu Mar  9 13:00:39 2023 daemon.err nmbd[3166]:   Samba name server OPENWRT-BANANAPI-BPI-R3 is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.1
Thu Mar  9 13:00:39 2023 daemon.err nmbd[3166]:
Thu Mar  9 13:00:39 2023 daemon.err nmbd[3166]:   *****
Thu Mar  9 13:00:40 2023 daemon.info dnsmasq[1]: exiting on receipt of SIGTERM
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: started, version 2.89 cachesize 1000
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: DNS service limited to local subnets
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-cryptohash no-DNSSEC no-ID loop-detect inotify dumpfile
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: UBus support enabled: connected to system bus
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq-dhcp[1]: DHCP, IP range 192.168.0.100 -- 192.168.0.249, lease time 1h
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for zororomemorial.co.zw
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using only locally-known addresses for secure.v.co.zw
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using 249965 more local addresses
Thu Mar  9 13:00:49 2023 daemon.info dnsmasq[1]: using 369 more nameservers
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using nameserver 192.168.1.1#53
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for test
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for onion
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for localhost
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for local
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for invalid
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for bind
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for zororomemorial.co.zw
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using only locally-known addresses for secure.v.co.zw
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using 249965 more local addresses
Thu Mar  9 13:00:50 2023 daemon.info dnsmasq[1]: using 369 more nameservers
Thu Mar  9 13:00:51 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Thu Mar  9 13:00:51 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 10 names
Thu Mar  9 13:00:51 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Thu Mar  9 13:00:52 2023 user.info adblock-4.1.5[1947]: blocklist with overall 249967 blocked domains loaded successfully (Bananapi BPI-R3, OpenWrt SNAPSHOT r22248-bf055fcdca)
Thu Mar  9 13:01:07 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.203 44:8a:5b:42:23:67
Thu Mar  9 13:01:07 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.203 44:8a:5b:42:23:67 MSI-GP60-LAN
Thu Mar  9 13:01:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.0.200 18:c0:4d:40:a2:79
Thu Mar  9 13:01:46 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.0.200 18:c0:4d:40:a2:79 James-PC

Here you have a crash in ethernet driver not wifi. Can you do anything on the system after this? If yes is wired network accessable? I guess system or at least network is completely broken.

Can you report issue to openwrt with this trace?

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.

Screenshot_2023-03-09_124905-01

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

1 Like

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.

Screenshot_2023-03-12_222524-01

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.

Screenshot_2023-03-14_171326-01

1 Like

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.