UPDATE:
After removed the case cover, without modify any configuration it seems running stable and no more for disconnection for 4 days already. Possible over temp throttle issue, still observing for more time… will update again.
1 Like
Do you have made any ventilation holes into the case?
By default case is very closed except the hole for boot-switch and the other right from it. I already mentioned that at least holes for fan are needed,but airflow needs also an entry (if fan used for outgoing flow)
There are two holes (for wall mounting) beneath the case, the case is sitting directly on top of a fan (suction) of laptop cooling pad.
I checked the temp by touching the case from time to time at the beginning of this setup, room temp is AC cooled at 26c-28c, and the case barely feel hot even without AC, just very slightly warm, had it ran for months without problem. (sorry for unable to obtain scientific temp measurement result due to lack of tool)
Although not strongly convinced its caused by the heat issue, but the periodic disconnect issue apparently gone after take off the top cover.
It’s sounds like a hard issue to debug.
Cooling
The wall mounting holes are not enough for cooling. Frank really aimed for home-made holes, manually created. You also might want to add a fan pointing towards the components, rather than trying to blow air from under neat. As Frank stated you might want to integrate an actual custom fan into the casing somehow.
Memory
I found the memory usage very high. Keep in mind the BPI-R3 has “only” 2GB ram. And you were using basically all of it (98%)! Assuming there is no swap partition, your router will crash since it has no additional RAM left anymore!!
What is using so much ram? Could you try to login via SSH maybe, and run commands like top. Shift+ M should order the processes by memory usage, in my case I’m not so sure about that. Since the top version on my OpenWRT seems old, I can’t even use interactive mode…
Anyway… hopefully you are able to pin point the process that is using a lot of memory. I mean look at my old router with only 56MB RAM, and I have more RAM available then you have…
OpenWRT
Last, I want to point out that the snapshot versions aren’t as stable as you might want it to be. It’s not advised to run snapshot OpenWRT version during production.
1 Like
Thank you all for the concern & suggestion.
Cooling
After remove the top cover and ran for straight a week without disconnection issue, I putted back the cover and rebooted, trying to reproduce the disconnection issue see if its really caused by overheat, which I really doubt as if it is caused by the heat with following evidence.
- As the previous disconnection happened about every 2 days periodically, if it is heat or ventilation issue it should reach throttle point quicker than 48 hours.
- With the help of the cooling pad, the case is barely hot, only slightly warm to touch (feels like when we check temp by touch someone’s forehead.)
Still, this is an unconfirmed case. I will try to drill holes on top of the case to adapt an exhaust fan if the disconnection happens again after put back the cover.
Memory Usage
I’ve checked the process list before when the memory usage was high, found no clue. The only suspected process was transmission daemon I enabled for download torrents when my PC is off. After disabled transmission daemon, I didn’t have high memory usage so far. (200MiB+ over 2GiB)
Still observing, will post updates…
Checked the log, and the records are not looking good. Current highest is 78c, will check record again tomorrow see how high will it go after AC auto turned off.
Current settings
- OEM metal case, fully closed.
- Exhaust fan under the case pulling air from two mounting holes. (laptop cooling pad)
- Room AC switched to FAN mode, and with OFF timer set at 2am.
- only 3 client devices connected, no heavy network usage. Probably only 1 iPad is streaming from Netflix, other 2 phone devices are idling.
Sun Mar 5 23:50:37 PST 2023 mt7915_phy1-isa-18000000 Adapter: ISA adapter temp1: +53.0°C (high = +120.0°C, crit = +110.0°C)
mt7915_phy0-isa-18000000 Adapter: ISA adapter temp1: +74.0°C (high = +120.0°C, crit = +110.0°C)
Sun Mar 5 23:52:00 PST 2023 mt7915_phy1-isa-18000000 Adapter: ISA adapter temp1: +53.0°C (high = +120.0°C, crit = +110.0°C)
mt7915_phy0-isa-18000000 Adapter: ISA adapter temp1: +61.0°C (high = +120.0°C, crit = +110.0°C)
Sun Mar 5 23:53:00 PST 2023 mt7915_phy1-isa-18000000 Adapter: ISA adapter temp1: +53.0°C (high = +120.0°C, crit = +110.0°C)
mt7915_phy0-isa-18000000 Adapter: ISA adapter temp1: +78.0°C (high = +120.0°C, crit = +110.0°C)
Checked the log, and the records are not looking good.
Not looking good? Maybe you want to share your logging…?
It could be overheat issues indeed, it could be software issue. We need to deep futher.
Regarding memory usage, 200M is at least better than 2GB. So hopefully there is no additional sudden memory increase anymore… And consider a dedicated machine/SBC for running the torrent daemon.
The logging was a shell script that saves the result from sensors command to a file every 30 seconds, not sure how accurate the sensor report is.
Got 78c without heavy usage or many device connected.
mt7915_phy0-isa-18000000 Adapter: ISA adapter temp1: +78.0°C (high = +120.0°C, crit = +110.0°C)
Haven’t experience periodic disconnection so far, with or without case cover. But the high memory usage has coming back. (1.7GiB cached data?)
Logging from the sensors command averages 50c for 48 hrs, with sudden spike to 82c (highest) for less than a minute.
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.
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-PCHere 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.
May I ask where can I report the issue?