I would advise having the debug info options activated on the config file before building... Maybe the resulting sysimage is a bit bigger but not that much... and the crashlogs would be so much more helpful 
As it is, the crashlogs don't have useful information to understand what happened... what do you think @db260179 ?
Try another power supply, that can cause grief. If its still crashing then im afraid you have a faulty unit.
Hi, @db260179 you're doing a great job, my router has worked better than ever.
Thank you.
I see that you have released another version with even more improvements but I cannot find the sysupgrade file.
Is the sysupgrade file in your new version?
Hello again @db260179.
Something happened while using your stable version 1.0
Fri Oct 30 22:04:29 2020 kern.info kernel: [178756.287278] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Fri Oct 30 22:04:29 2020 kern.info kernel: [178756.292855] mt76x2e 0000:01:00.0: Build: 1
Fri Oct 30 22:04:29 2020 kern.info kernel: [178756.297108] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Fri Oct 30 22:04:29 2020 kern.info kernel: [178756.325698] mt76x2e 0000:01:00.0: Firmware running!
Fri Oct 30 22:04:29 2020 kern.info kernel: [178756.335884] ieee80211 phy1: Hardware restart was requested
Fri Oct 30 22:04:32 2020 kern.info kernel: [178759.827186] mt76x2e 0000:01:00.0: Firmware Version: 0.0.00
Fri Oct 30 22:04:32 2020 kern.info kernel: [178759.832763] mt76x2e 0000:01:00.0: Build: 1
Fri Oct 30 22:04:32 2020 kern.info kernel: [178759.837002] mt76x2e 0000:01:00.0: Build Time: 201507311614____
Fri Oct 30 22:04:32 2020 kern.info kernel: [178759.865576] mt76x2e 0000:01:00.0: Firmware running!
Fri Oct 30 22:04:32 2020 kern.info kernel: [178759.875742] ieee80211 phy1: Hardware restart was requested
What do you think is the reason for this?
Have added built images to that release and imagebuilder
So it seems others people with mt76 chips have had the same issue
Another possibilty is the power supply is not strong enough and the wifi is just restarting under load.
This issue is quite common amongst 2.4ghz wireless ap, mt7612en is a problematic chip, i only use the 5ghz, suggestions have to use bg mode and not N mode.
Submitted official support. Didnt add the switch adjustments as effects all mt7621 devices and not fully tested.
Be advised, that the new DSA driver in the master branch of openwrt, for the switch doesn't currently have a nice luci gui to configure it, so you have to use the cli to configure the switch for now if using the snapshot release of this device.
Hello to all,
Thank you for your amazing work for this device. I flashed the router yesterday and it was quite straightforward. The only version that booted was this one from @db260179, don't know exactly why. In @db260179 last post it is stated that the new DSA driver does not allow to configure the switch in the gui, so no Vlan's in gui? Is this correct for this last version 1.1 stable? Or is it only valid for the pull request?
Another thing I found is that the 5Ghz band is only operable in channel 36, if I switch it to any other channel it does not work anymore it states Wireless not enable/not started maybe. And also if I set it to auto sometimes after Save&Apply it starts but the channel is always 36 or it does not start at all. Is this normal?
Thank you for your support.
So do be clear, the recent add support of this device to the official openwrt master branch, which is called the snapshot releases. So this snapshot is now using kernel 5.4 and a new switch driver DSA. Unfortunatley this new driver has no gui config from the luci web page as the way it works is no longer compatible with the luci architecture.
My stable release are based on the V19.07.4 branch and use the kernel 4.14 kernel which doesnt have this issue, so there is still a switch config options in luci. My latest v1.1 stable is complete and functional.
Not sure what country you are in, but in the advanced settings of the wireless you need to make sure you set the correct domain. Some countries restrict what 5ghz channels can be used, the driver will use this database to restrict what channels can be used.
Hello @db260179,
Thank you for your explanation. Now everything is understood.
Regarding the 5Ghz band, I did not touch the anything in advanced settings, so I am going to adjust the settings to my country (Portugal) and then try it again.
Thanks for the support and all the work.
Hello @db260179,
I see that there is a new version v1.1.1 stable and that it is recommended to do the upgrade. Justo to be sure and to not break anything, the advised upgrade is from the WebGui with the openwrt-19.07.4-r11208-ce6496d796-ramips-mt7621-xiaomi_mir4ag-squashfs-sysupgrade.bin, right?
Is setting to router to default settings recommended?
Sorry for these questions but been new at this I think is better to ask then to break anything.
Thank you very much for your support.
Best regards.
Hi, so do a backup first in the webui, then do the firmware upgrade keeping the 'keep settings' set when doing the upgrade.
You will still need to reinstall any additional packages that you installed after the firmware install.
This new version is just an image size adjustment correction and the previous version will keep the config as long as you have the 'keep config' option enabled.
Hello,
Thank you very much for your support. Already updated like decribed and running fine.
Thanks again.
@db260179 Hi David,
Thanks, I've applied your firmware with "Forced upgrade" to 4A Gigabit Edition with Winbond based SPI.
Will report back any findings.
The device is running as WDS (Client) bridging to another identical device that is running @araujorm firmware.
@db260179 Thanks for your work on firmware for this device. I've had the following issue running your v1.1.1-stable release:
Tue Nov 10 08:46:19 2020 kern.warn kernel: [38608.860589] ------------[ cut here ]------------
Tue Nov 10 08:46:19 2020 kern.warn kernel: [38608.865221] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:320 0x803306b8
Tue Nov 10 08:46:19 2020 kern.info kernel: [38608.872266] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out
Tue Nov 10 08:46:19 2020 kern.warn kernel: [38608.879199] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack_netlink nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport
Tue Nov 10 08:46:19 2020 kern.warn kernel: [38608.950012] ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 leds_gpio gpio_button_hotplug
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38608.972553] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.201 #0
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38608.978619] Stack : 00000000 00000200 80630000 80063860 00000000 00000000 00000000 00000000
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38608.986954] 00000000 00000000 00000000 00000000 00000000 00000001 87c0dd70 1cc28229
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38608.995291] 87c0de08 00000000 00000000 00000000 00000038 80420278 312e3420 30322e34
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.003628] 36767069 44000000 00000010 64656c20 00000000 00000000 00000001 8048722c
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.011964] 00000009 00000140 ffffffff 00000200 00000000 802636ac 00000008 80630008
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.020299] ...
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.022735] Call Trace:
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.022750] [<80063860>] 0x80063860
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.028659] [<80420278>] 0x80420278
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.032136] [<802636ac>] 0x802636ac
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.035608] [<8000b8ec>] 0x8000b8ec
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.039077] [<8000b8f4>] 0x8000b8f4
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.042550] [<8040a398>] 0x8040a398
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.046019] [<80063a0c>] 0x80063a0c
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.049489] [<803306b8>] 0x803306b8
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.052961] [<80029208>] 0x80029208
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.056432] [<803306b8>] 0x803306b8
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.059943] [<803305cc>] 0x803305cc
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.063424] [<80029240>] 0x80029240
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.066896] [<802dbea8>] 0x802dbea8
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.070370] [<803305cc>] 0x803305cc
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.073849] [<803306b8>] 0x803306b8
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.077320] [<8003d7a4>] 0x8003d7a4
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.080795] [<803305cc>] 0x803305cc
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.084266] [<8007831c>] 0x8007831c
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.087737] [<80078848>] 0x80078848
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.091210] [<80073634>] 0x80073634
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.094682] [<8006a4d0>] 0x8006a4d0
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.098153] [<804253e0>] 0x804253e0
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.101633] [<8002cf8c>] 0x8002cf8c
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.105105] [<80217fd0>] 0x80217fd0
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.108576] [<80006b08>] 0x80006b08
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.112045]
Tue Nov 10 08:46:20 2020 kern.warn kernel: [38609.113669] ---[ end trace 04f246e759c1a1f4 ]---
Tue Nov 10 08:46:20 2020 kern.err kernel: [38609.118285] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Tue Nov 10 08:46:20 2020 kern.info kernel: [38609.124478] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000065
Tue Nov 10 08:46:20 2020 kern.info kernel: [38609.130476] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=06db0000, max=0, ctx=1645, dtx=1645, fdx=1644, next=1645
Tue Nov 10 08:46:20 2020 kern.info kernel: [38609.141344] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=06150000, max=0, calc=3202, drx=3203
Tue Nov 10 08:46:20 2020 kern.info kernel: [38609.154236] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Tue Nov 10 08:46:20 2020 kern.info kernel: [38609.167052] mtk_soc_eth 1e100000.ethernet: PPE started
Tue Nov 10 08:46:20 2020 kern.info kernel: [38609.172809] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down
Tue Nov 10 08:46:21 2020 kern.info kernel: [38610.801878] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up
Tue Nov 10 12:52:37 2020 kern.info kernel: [53385.965955] mtk_soc_eth 1e100000.ethernet eth0: port 2 link up
Tue Nov 10 14:20:01 2020 daemon.notice wpa_supplicant[1819]: wlan1: CTRL-EVENT-BEACON-LOSS
Tue Nov 10 14:20:02 2020 daemon.notice wpa_supplicant[1819]: wlan1: CTRL-EVENT-BEACON-LOSS
Tue Nov 10 16:10:20 2020 kern.err kernel: [65248.991224] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Tue Nov 10 16:10:20 2020 kern.info kernel: [65248.997418] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000065
Tue Nov 10 16:10:20 2020 kern.info kernel: [65249.003453] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07210000, max=0, ctx=3172, dtx=3172, fdx=3171, next=3172
Tue Nov 10 16:10:20 2020 kern.info kernel: [65249.014335] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=07190000, max=0, calc=776, drx=777
Tue Nov 10 16:10:20 2020 kern.info kernel: [65249.026983] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Tue Nov 10 16:10:20 2020 kern.info kernel: [65249.039892] mtk_soc_eth 1e100000.ethernet: PPE started
Tue Nov 10 16:10:20 2020 kern.info kernel: [65249.045849] mtk_soc_eth 1e100000.ethernet eth0: port 2 link down
Tue Nov 10 16:10:20 2020 kern.info kernel: [65249.051927] mtk_soc_eth 1e100000.ethernet eth0: port 3 link down
Tue Nov 10 16:10:22 2020 kern.info kernel: [65250.708752] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up
Tue Nov 10 16:10:24 2020 kern.info kernel: [65252.196153] mtk_soc_eth 1e100000.ethernet eth0: port 2 link up
Tue Nov 10 17:55:50 2020 kern.err kernel: [71578.792847] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Tue Nov 10 17:55:50 2020 kern.info kernel: [71578.799026] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000065
Tue Nov 10 17:55:50 2020 kern.info kernel: [71578.805049] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=07160000, max=0, ctx=1867, dtx=1867, fdx=1866, next=1867
Tue Nov 10 17:55:50 2020 kern.info kernel: [71578.815910] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=06040000, max=0, calc=1058, drx=1059
Tue Nov 10 17:55:50 2020 kern.info kernel: [71578.828662] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Tue Nov 10 17:55:50 2020 kern.info kernel: [71578.841555] mtk_soc_eth 1e100000.ethernet: PPE started
Tue Nov 10 17:55:50 2020 kern.info kernel: [71578.847276] mtk_soc_eth 1e100000.ethernet eth0: port 2 link down
Tue Nov 10 17:55:54 2020 kern.info kernel: [71581.981770] mtk_soc_eth 1e100000.ethernet eth0: port 2 link up
Tue Nov 10 19:17:50 2020 kern.err kernel: [76498.640905] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Tue Nov 10 19:17:50 2020 kern.info kernel: [76498.647089] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000065
Tue Nov 10 19:17:50 2020 kern.info kernel: [76498.653120] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=05800000, max=0, ctx=422, dtx=422, fdx=421, next=422
Tue Nov 10 19:17:50 2020 kern.info kernel: [76498.663634] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=05850000, max=0, calc=3061, drx=3062
Tue Nov 10 19:17:50 2020 kern.info kernel: [76498.676536] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Tue Nov 10 19:17:50 2020 kern.info kernel: [76498.689524] mtk_soc_eth 1e100000.ethernet: PPE started
Tue Nov 10 19:17:50 2020 kern.info kernel: [76498.695312] mtk_soc_eth 1e100000.ethernet eth0: port 2 link down
Tue Nov 10 19:17:54 2020 kern.info kernel: [76501.849873] mtk_soc_eth 1e100000.ethernet eth0: port 2 link up
Tue Nov 10 22:33:50 2020 daemon.notice wpa_supplicant[1819]: wlan1: WPA: Group rekeying completed with <redacted> [GTK=CCMP]
It seems you are already using the reverted commit mentioned by @araujorm here:
I am also seeing this same issue running @araujorm release https://github.com/araujorm/openwrt/releases/tag/v19.07.4-xiaomi-miwifi-3gv2-mt76updated-2020-10-24 on another identical device:
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.313587] ------------[ cut here ]------------
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.318340] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x1ac/0x324
Wed Nov 11 07:30:17 2020 kern.info kernel: [291403.326684] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.333711] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT wireguard slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 nfsv3 nfs ip6_udp_tunnel udp_tunnel tun lockd sunrpc grace dns_resolver dm_mirror dm_region_hash dm_log
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.404418] dm_crypt dm_mod dax leds_gpio gpio_button_hotplug
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.410338] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.14.195 #0
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.416486] Stack : 00000000 87de3040 805b0000 800728cc 805d0000 805760b8 00000000 00000000
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.424911] 80541600 87c0ddc4 87c3499c 805b0987 8053c3f0 00000001 87c0dd68 1cc28223
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.433335] 00000000 00000000 80710000 00005cb0 00000000 0000012d 00000008 00000000
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.441755] 00000000 805b0000 000642e2 70617773 00000000 805d0000 00000000 8056fee0
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.450176] 803816d0 00000140 00000002 87de3040 00000008 802a8808 00000008 80710008
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.458599] ...
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.461126] Call Trace:
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.463673] [<8000c7b0>] show_stack+0x58/0x100
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.468192] [<8047ab34>] dump_stack+0xa4/0xe0
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.472623] [<8002f608>] __warn+0xe0/0x138
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.476792] [<8002f690>] warn_slowpath_fmt+0x30/0x3c
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.481841] [<803816d0>] dev_watchdog+0x1ac/0x324
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.486638] [<80089618>] call_timer_fn.isra.25+0x24/0x84
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.492019] [<800898d4>] run_timer_softirq+0x1bc/0x248
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.497237] [<80498ad8>] __do_softirq+0x128/0x2ec
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.502017] [<80033fb4>] irq_exit+0xac/0xc8
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.506291] [<8025b480>] plat_irq_dispatch+0xfc/0x138
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.511409] [<80007588>] except_vec_vi_end+0xb8/0xc4
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.516444] [<80008f50>] r4k_wait_irqoff+0x1c/0x24
Wed Nov 11 07:30:17 2020 kern.warn kernel: [291403.521369] ---[ end trace 902155b884447e73 ]---
Wed Nov 11 07:30:17 2020 kern.err kernel: [291403.526075] mtk_soc_eth 1e100000.ethernet eth0: transmit timed out
Wed Nov 11 07:30:17 2020 kern.info kernel: [291403.532325] mtk_soc_eth 1e100000.ethernet eth0: dma_cfg:80000065
Wed Nov 11 07:30:17 2020 kern.info kernel: [291403.538419] mtk_soc_eth 1e100000.ethernet eth0: tx_ring=0, base=06ad0000, max=0, ctx=2306, dtx=2306, fdx=2305, next=2306
Wed Nov 11 07:30:17 2020 kern.info kernel: [291403.549344] mtk_soc_eth 1e100000.ethernet eth0: rx_ring=0, base=06260000, max=0, calc=2145, drx=2146
Wed Nov 11 07:30:17 2020 kern.info kernel: [291403.563805] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Wed Nov 11 07:30:17 2020 kern.info kernel: [291403.576400] mtk_soc_eth 1e100000.ethernet: PPE started
Thanks for the feedback.
Does the router freeze completly or carry on working?
v1.1.1 doesnt have my recent patches for up and down issues.
This transmit timeout appears to be related to the hardware version of the mt7530 switch, some have bugs that cause this.
It carries on working which is the same behaviour as previous firmwares.
I've noticed that after longer run times (usually 7 days+) with some of the @araujorm's builds I tend to see some random periods of complete packet loss over the WiFi bridge which is then stable again after reboot. I've been running various builds across the devices so difficult to pinpoint the cause of that.
I will try to do some more structured throughput testing, say 5 mins after boot, and then retest after this issue has occurred (also currently in the middle of sorting out a couple of tweaks to log usage rrd and vnstat to NFS share for better visibility of what's going on when these issues happen).
Do you have any reference links noted about this please?
Someone was saying that there could be an under volt issue causing crashing issues?
One thing you can try, is get a 12v 3A psu with the same plug, poor psu can cause all kinds of issues.
What is connected to this router? 1gb devices or 100mb? - as a recent patch i've done disables the EEE mode, this can cause up/down interface issues.
Timeout issue is an historical issue for the mt7530 switch, the reset function i've added will just let the switch to continue without a hard lock.
Tested the OEM supplied PSU and was reading ~11.6 Volts.
I've replaced with 5A supply I had laying about (although doubt it's really rated this high anyway).
The new PSU is reading ~12.5 Volts so will see if this makes a difference before making any further changes...
Previously just a 1Gbit uplink to an unmanaged 1Gbit switch.
Have also moved direct 1GBit link to PC direct to switch too (but this issue was present prior to using second port). The WAN port is unused.