5GHZ settings
And I have used this before:`Wireless Ethernet Dispatch
WED enables hardware acceleration for WiFi 5GHz traffic. This feature is not yet exposed in LuCI, to enable use the command line. More information is found here.
SSH: nano /etc/modules.conf
Append: options mt7915e wed_enable=Y
Save and Reboot
To check that the kernel module has this applied the following command will return Y (yes): cat /sys/module/mt7915e/parameters/wed_enable `
Could you see the Negotiated rate?
I will send you the details when I’m home. I created the additional SSIDs/Virtual AccessPoints over the Luci wireless interface.
I’m using 4.5.7 from the google drive link
It’s not true. Per exemple my Huawei P30 Pro is wifi 5 and supports 160mhz
Wi-Fi 5, also known as 802.11ac, does indeed support 160 MHz channel bandwidths. This capability was introduced as an optional feature in the standard.
But not all devices are able to use it. So generally speaking it does support 160 MHz but… not really 
Highly depends on the device.
https://www.intel.com/content/www/us/en/support/articles/000005725/wireless/legacy-intel-wireless-products.html
I found a link from intel. WIFI5 wave2 have 160Mhz, but the device is much less.
In general the OpenWrt snapshots have been much more stable than any version of GL.iNet’s firmware for this device. And I think the reason for that is because GL.iNet’s firmware is based on 23.05.0-rc1 with some fixes and cherry picked changes applied on top, as I shown here.
If the GL.iNet devs were to rebase their firmware on a newer OpenWrt snapshot version (maybe from the main branch instead of the 23.05 branch) then I think that’d resolve most of the stability issues, since there wouldn’t be any missing commits anymore. It’s just important that they use a pure OpenWrt snapshot with only their UI and packages applied on top. No additional WiFi patches etc.
The 2.4GHz radio still doesn’t perform as well as it should in the OpenWrt snapshots, but that’s a driver issue and I’m going to dig into that myself when I’ve got some free time.
Use a DFS channel like 120 and it’ll work as long as you’ve got devices that support 160MHz.
What I thinking about beta tester forum - create hidden chapter topics and special group user can share information for test. Because most people want to try in public tester and could be make brick Routers, complaints, and much more questions…
If not, then delete my post here. 
when do you have a solution?
Heres my initial review of the 4.5.7 (drive close source firmware) on my MT6000.
Devices:
Realme 6 w/o 160Mhz support
Laptop with AX210 160Mhz support
Wireless config:
5Ghz: 160Mhz enabled (120 channel)
2.4ghz: auto network and bandwidth
SSID seperated
Upgraded without keeping settings
Phone: 2.4ghz now works fine! I hope this time it will actually last. No problem with 5Ghz also. From 5mbps only (2.4ghz) to full PHY speed of my phone.
Laptop: There was actually no problem with my laptop with AX210 wireless card on older firmware revisions even in 2.4ghz. No apparent / obvious issues right now. Full PHY speed on both bands.
Im not also experiencing any extra ssids being broadcasted or what. I also haven’t checked LUCI and will stick with default country code and transmission power for now.
Absurdly regretting having invested a high amount of money in a kit, which I still received the wrong plug adapter for, requested an exchange and they still informed me that the correct model for my country was exactly the one they sent… yes, the company knows better than the local customer!
We still have completely unstable equipment, which ends up giving us no confidence in its use. 2.4ghz network with absurd latency, leaving IOT devices with terrible performance. 5ghz wifi with constant drops… and now, a sequence of crashes What is the manufacturer’s official rating? We are at almost 900 posts and I notice little interaction from the company.
Best regards,
Oops#1 Part1
<6>[14962.089024] mt7530-mdio mdio-bus:1f lan3: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[14962.096972] br-lan: port 2(lan3) entered blocking state
<6>[14962.102198] br-lan: port 2(lan3) entered forwarding state
<6>[17747.980640] mt7530-mdio mdio-bus:1f lan3: Link is Down
<6>[17747.985952] br-lan: port 2(lan3) entered disabled state
<6>[17802.662966] mt7530-mdio mdio-bus:1f lan3: Link is Up - 1Gbps/Full - flow control off
<6>[17802.670746] br-lan: port 2(lan3) entered blocking state
<6>[17802.675962] br-lan: port 2(lan3) entered forwarding state
<6>[18425.804012] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18425.811950] br-lan: port 3(lan4) entered blocking state
<6>[18425.817172] br-lan: port 3(lan4) entered forwarding state
<6>[18520.188694] br-lan: port 1(lan2) entered disabled state
<6>[18520.194089] mt7530-mdio mdio-bus:1f lan2: Link is Down
<6>[18520.309889] mt7530-mdio mdio-bus:1f lan4: Link is Down
<6>[18520.315205] br-lan: port 3(lan4) entered disabled state
<6>[18521.851767] mt7530-mdio mdio-bus:1f lan2: Link is Up - 10Mbps/Full - flow control rx/tx
<6>[18521.859799] br-lan: port 1(lan2) entered blocking state
<6>[18521.865013] br-lan: port 1(lan2) entered forwarding state
<6>[18521.961071] mt7530-mdio mdio-bus:1f lan4: Link is Up - 10Mbps/Full - flow control rx/tx
<6>[18521.969104] br-lan: port 3(lan4) entered blocking state
<6>[18521.974327] br-lan: port 3(lan4) entered forwarding state
<6>[18533.219878] mt7530-mdio mdio-bus:1f lan2: Link is Down
<6>[18533.225080] br-lan: port 1(lan2) entered disabled state
<6>[18533.306154] mt7530-mdio mdio-bus:1f lan4: Link is Down
<6>[18533.311367] br-lan: port 3(lan4) entered disabled state
<6>[18535.665168] mt7530-mdio mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18535.673120] br-lan: port 1(lan2) entered blocking state
<6>[18535.678344] br-lan: port 1(lan2) entered forwarding state
<6>[18535.830272] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18535.838226] br-lan: port 3(lan4) entered blocking state
<6>[18535.843438] br-lan: port 3(lan4) entered forwarding state
<6>[18559.567470] mt7530-mdio mdio-bus:1f lan2: Link is Down
<6>[18559.572679] br-lan: port 1(lan2) entered disabled state
<6>[18560.134263] mt7530-mdio mdio-bus:1f lan4: Link is Down
<6>[18560.139498] br-lan: port 3(lan4) entered disabled state
<6>[18561.807899] mt7530-mdio mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18561.815838] br-lan: port 1(lan2) entered blocking state
<6>[18561.821059] br-lan: port 1(lan2) entered forwarding state
<6>[18562.461030] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18562.469006] br-lan: port 3(lan4) entered blocking state
<6>[18562.474234] br-lan: port 3(lan4) entered forwarding state
<1>[70544.153335] Unable to handle kernel write to read-only memory at virtual address 0000000000000000
<1>[70544.162207] Mem abort info:
<1>[70544.164985] ESR = 0x0000000096000045
<1>[70544.168724] EC = 0x25: DABT (current EL), IL = 32 bits
<1>[70544.174017] SET = 0, FnV = 0
<1>[70544.177061] EA = 0, S1PTW = 0
<1>[70544.180185] FSC = 0x05: level 1 translation fault
<1>[70544.185043] Data abort info:
<1>[70544.187911] ISV = 0, ISS = 0x00000045
<1>[70544.191728] CM = 0, WnR = 1
<1>[70544.194680] user pgtable: 4k pages, 39-bit VAs, pgdp=000000004b24f000
<1>[70544.201103] [0000000000000000] pgd=080000004c247003, p4d=080000004c247003, pud=080000004c247003, pmd=0000000000000000
<0>[70544.211694] Internal error: Oops: 0000000096000045 [#1] SMP
<7>[70544.217247] Modules linked in: pppoe ppp_async option wireguard usb_wwan rndis_host qmi_wwan pppox ppp_generic nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet mt7915e mt76_connac_lib mt76 mac80211 libchacha20poly1305 ipt_REJECT huawei_cdc_ncm chacha_neon cfg80211 cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_recent xt_quota xt_pkttype xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_helper xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_cgroup xt_addrtype xt_TCPMSS xt_REDIRECT xt_MASQUERADE xt_LOG xt_CT usbserial usbnet slhc poly1305_neon 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_compat nft_chain_nat nf_tables nf_reject_ipv4 nf_log_syslog nf_flow_table nf_conntrack_netlink nf_conncount mdio_netlink libcurve25519_generic libcrc32c libchacha iptable_nat iptable_mangle
<7>[70544.217388] iptable_filter ipheth ip_tables crc_ccitt compat cls_flower cdc_wdm cdc_acm br_netfilter arptable_filter arpt_mangle arp_tables act_vlan crypto_safexcel fuse cls_bpf act_bpf 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 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 ip_set_hash_ipmark ip_set_hash_ipmac ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_NPT ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb ip6_udp_tunnel udp_tunnel tun ntfs nls_utf8 nls_iso8859_1 nls_cp437 sha1_generic seqiv md5 des_generic libdes authencesn authenc mtdoops uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd
<7>[70544.304712] xhci_hcd uhci_hcd ohci_platform ohci_hcd fsl_mph_dr_of ehci_platform ehci_fsl kmwan ehci_hcd gpio_button_hotplug gl_sdk4_tertf gl_sdk4_black_white_list vfat fat exfat usbcore usb_common mii gl_sdk4_hw_info
<7>[70544.410996] CPU: 0 PID: 388 Comm: napi/mtk_eth-6 Not tainted 5.15.139 #0
<7>[70544.417677] Hardware name: GL.iNet GL-MT6000 (DT)
<7>[70544.422362] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
<7>[70544.429302] pc : mt76_tx+0xbc/0x3c0 [mt76]
<7>[70544.433393] lr : mt7915_eeprom_get_power_delta+0x1928/0x2580 [mt7915e]
<7>[70544.439905] sp : ffffffc009a132b0
<7>[70544.443202] x29: ffffffc009a132b0 x28: ffffff8005dc4f28 x27: ffffff80057c0d90
<7>[70544.450318] x26: ffffffc009a13470 x25: ffffff800a729958 x24: ffffff8009154aa8
<7>[70544.457434] x23: ffffff8005dc4f28 x22: ffffffc000fe1fa8 x21: ffffff8005dc4f00
<7>[70544.464548] x20: ffffff80057c2020 x19: ffffff8009154cc8 x18: 0000000000000070
<7>[70544.471664] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000080
<7>[70544.478779] x14: 0000000000000001 x13: 00000003aaaa0000 x12: 0000000000000000
<7>[70544.485894] x11: 0000000000000023 x10: 0000000000000000 x9 : ffffffc009a13800
<7>[70544.493010] x8 : 00000000a7c48394 x7 : ffffff80077b4104 x6 : 00000000f0000010
<7>[70544.500125] x5 : ffffff8005032020 x4 : 0000000000000000 x3 : 0000000000000001
<7>[70544.507241] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff8009154e00
<7>[70544.514357] Call trace:
<7>[70544.516789] mt76_tx+0xbc/0x3c0 [mt76]
<7>[70544.520525] mt7915_eeprom_get_power_delta+0x1928/0x2580 [mt7915e]
<7>[70544.526688] __ieee80211_schedule_txq+0xe60/0x1b30 [mac80211]
<7>[70544.532442] __ieee80211_xmit_fast+0x7b4/0x950 [mac80211]
<7>[70544.537837] __ieee80211_subif_start_xmit+0x1e8/0x354 [mac80211]
<7>[70544.543839] ieee80211_subif_start_xmit+0x3c/0x3bc [mac80211]
<7>[70544.549580] ieee80211_subif_start_xmit_8023+0x318/0x430 [mac80211]
<7>[70544.555841] dev_hard_start_xmit+0xe4/0x180
<7>[70544.560012] __dev_queue_xmit+0x968/0xc30
<7>[70544.564006] dev_queue_xmit+0x10/0x20
<7>[70544.567652] br_dev_queue_push_xmit+0x9c/0x1b4
<7>[70544.572083] br_forward_finish+0x98/0xb0
<7>[70544.575990] __br_forward+0x138/0x1a0
<7>[70544.579637] br_forward+0x124/0x150
<7>[70544.583111] br_dev_xmit+0x208/0x3ec
<7>[70544.586672] dev_hard_start_xmit+0xe4/0x180
<7>[70544.590838] __dev_queue_xmit+0x968/0xc30
<7>[70544.594831] dev_queue_xmit+0x10/0x20
<7>[70544.598478] ip_finish_output2+0x204/0x4b0
<7>[70544.602560] __ip_finish_output+0x9c/0x190
<7>[70544.606640] ip_finish_output+0x30/0xd0
<7>[70544.610461] ip_output+0x98/0x120
<7>[70544.613760] ip_forward_finish+0x84/0xc0
<7>[70544.617667] ip_forward+0x458/0x510
<7>[70544.621140] ip_rcv_finish+0x8c/0xb0
<7>[70544.624699] ip_rcv+0x98/0xcc
<7>[70544.627652] __netif_receive_skb_one_core+0x44/0x50
<7>[70544.632513] __netif_receive_skb+0x14/0x60
<7>[70544.636592] process_backlog+0xac/0x1e0
<7>[70544.640412] __napi_poll+0x54/0x1b0
<7>[70544.643885] net_rx_action+0x2a0/0x320
<7>[70544.647618] _stext+0x10c/0x28c
<7>[70544.650746] do_softirq+0x8c/0xa0
<7>[70544.654049] __local_bh_enable_ip+0xa0/0xa4
<7>[70544.658216] napi_threaded_poll+0x120/0x1a0
<7>[70544.662382] kthread+0x11c/0x130
<7>[70544.665599] ret_from_fork+0x10/0x20
<0>[70544.669161] Code: f90002a0 52800002 f90006a1 f900a275 (f9000035)
<4>[70544.675234] ---[ end trace 700fb61e6e89cfa1 ]---
Panic#2 Part1
<6>[17747.985952] br-lan: port 2(lan3) entered disabled state
<6>[17802.662966] mt7530-mdio mdio-bus:1f lan3: Link is Up - 1Gbps/Full - flow control off
<6>[17802.670746] br-lan: port 2(lan3) entered blocking state
<6>[17802.675962] br-lan: port 2(lan3) entered forwarding state
<6>[18425.804012] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18425.811950] br-lan: port 3(lan4) entered blocking state
<6>[18425.817172] br-lan: port 3(lan4) entered forwarding state
<6>[18520.188694] br-lan: port 1(lan2) entered disabled state
<6>[18520.194089] mt7530-mdio mdio-bus:1f lan2: Link is Down
<6>[18520.309889] mt7530-mdio mdio-bus:1f lan4: Link is Down
<6>[18520.315205] br-lan: port 3(lan4) entered disabled state
<6>[18521.851767] mt7530-mdio mdio-bus:1f lan2: Link is Up - 10Mbps/Full - flow control rx/tx
<6>[18521.859799] br-lan: port 1(lan2) entered blocking state
<6>[18521.865013] br-lan: port 1(lan2) entered forwarding state
<6>[18521.961071] mt7530-mdio mdio-bus:1f lan4: Link is Up - 10Mbps/Full - flow control rx/tx
<6>[18521.969104] br-lan: port 3(lan4) entered blocking state
<6>[18521.974327] br-lan: port 3(lan4) entered forwarding state
<6>[18533.219878] mt7530-mdio mdio-bus:1f lan2: Link is Down
<6>[18533.225080] br-lan: port 1(lan2) entered disabled state
<6>[18533.306154] mt7530-mdio mdio-bus:1f lan4: Link is Down
<6>[18533.311367] br-lan: port 3(lan4) entered disabled state
<6>[18535.665168] mt7530-mdio mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18535.673120] br-lan: port 1(lan2) entered blocking state
<6>[18535.678344] br-lan: port 1(lan2) entered forwarding state
<6>[18535.830272] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18535.838226] br-lan: port 3(lan4) entered blocking state
<6>[18535.843438] br-lan: port 3(lan4) entered forwarding state
<6>[18559.567470] mt7530-mdio mdio-bus:1f lan2: Link is Down
<6>[18559.572679] br-lan: port 1(lan2) entered disabled state
<6>[18560.134263] mt7530-mdio mdio-bus:1f lan4: Link is Down
<6>[18560.139498] br-lan: port 3(lan4) entered disabled state
<6>[18561.807899] mt7530-mdio mdio-bus:1f lan2: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18561.815838] br-lan: port 1(lan2) entered blocking state
<6>[18561.821059] br-lan: port 1(lan2) entered forwarding state
<6>[18562.461030] mt7530-mdio mdio-bus:1f lan4: Link is Up - 1Gbps/Full - flow control rx/tx
<6>[18562.469006] br-lan: port 3(lan4) entered blocking state
<6>[18562.474234] br-lan: port 3(lan4) entered forwarding state
<1>[70544.153335] Unable to handle kernel write to read-only memory at virtual address 0000000000000000
<1>[70544.162207] Mem abort info:
<1>[70544.164985] ESR = 0x0000000096000045
<1>[70544.168724] EC = 0x25: DABT (current EL), IL = 32 bits
<1>[70544.174017] SET = 0, FnV = 0
<1>[70544.177061] EA = 0, S1PTW = 0
<1>[70544.180185] FSC = 0x05: level 1 translation fault
<1>[70544.185043] Data abort info:
<1>[70544.187911] ISV = 0, ISS = 0x00000045
<1>[70544.191728] CM = 0, WnR = 1
<1>[70544.194680] user pgtable: 4k pages, 39-bit VAs, pgdp=000000004b24f000
<1>[70544.201103] [0000000000000000] pgd=080000004c247003, p4d=080000004c247003, pud=080000004c247003, pmd=0000000000000000
<0>[70544.211694] Internal error: Oops: 0000000096000045 [#1] SMP
<7>[70544.217247] Modules linked in: pppoe ppp_async option wireguard usb_wwan rndis_host qmi_wwan pppox ppp_generic nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet mt7915e mt76_connac_lib mt76 mac80211 libchacha20poly1305 ipt_REJECT huawei_cdc_ncm chacha_neon cfg80211 cdc_ncm cdc_ether xt_time xt_tcpudp xt_state xt_recent xt_quota xt_pkttype xt_owner xt_nat xt_multiport xt_mark xt_mac xt_limit xt_helper xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_cgroup xt_addrtype xt_TCPMSS xt_REDIRECT xt_MASQUERADE xt_LOG xt_CT usbserial usbnet slhc poly1305_neon 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_compat nft_chain_nat nf_tables nf_reject_ipv4 nf_log_syslog nf_flow_table nf_conntrack_netlink nf_conncount mdio_netlink libcurve25519_generic libcrc32c libchacha iptable_nat iptable_mangle
<7>[70544.217388] iptable_filter ipheth ip_tables crc_ccitt compat cls_flower cdc_wdm cdc_acm br_netfilter arptable_filter arpt_mangle arp_tables act_vlan crypto_safexcel fuse cls_bpf act_bpf 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 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 ip_set_hash_ipmark ip_set_hash_ipmac ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_NPT ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb ip6_udp_tunnel udp_tunnel tun ntfs nls_utf8 nls_iso8859_1 nls_cp437 sha1_generic seqiv md5 des_generic libdes authencesn authenc mtdoops uas usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_mtk_hcd
<7>[70544.304712] xhci_hcd uhci_hcd ohci_platform ohci_hcd fsl_mph_dr_of ehci_platform ehci_fsl kmwan ehci_hcd gpio_button_hotplug gl_sdk4_tertf gl_sdk4_black_white_list vfat fat exfat usbcore usb_common mii gl_sdk4_hw_info
<7>[70544.410996] CPU: 0 PID: 388 Comm: napi/mtk_eth-6 Not tainted 5.15.139 #0
<7>[70544.417677] Hardware name: GL.iNet GL-MT6000 (DT)
<7>[70544.422362] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
<7>[70544.429302] pc : mt76_tx+0xbc/0x3c0 [mt76]
<7>[70544.433393] lr : mt7915_eeprom_get_power_delta+0x1928/0x2580 [mt7915e]
<7>[70544.439905] sp : ffffffc009a132b0
<7>[70544.443202] x29: ffffffc009a132b0 x28: ffffff8005dc4f28 x27: ffffff80057c0d90
<7>[70544.450318] x26: ffffffc009a13470 x25: ffffff800a729958 x24: ffffff8009154aa8
<7>[70544.457434] x23: ffffff8005dc4f28 x22: ffffffc000fe1fa8 x21: ffffff8005dc4f00
<7>[70544.464548] x20: ffffff80057c2020 x19: ffffff8009154cc8 x18: 0000000000000070
<7>[70544.471664] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000080
<7>[70544.478779] x14: 0000000000000001 x13: 00000003aaaa0000 x12: 0000000000000000
<7>[70544.485894] x11: 0000000000000023 x10: 0000000000000000 x9 : ffffffc009a13800
<7>[70544.493010] x8 : 00000000a7c48394 x7 : ffffff80077b4104 x6 : 00000000f0000010
<7>[70544.500125] x5 : ffffff8005032020 x4 : 0000000000000000 x3 : 0000000000000001
<7>[70544.507241] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffffff8009154e00
<7>[70544.514357] Call trace:
<7>[70544.516789] mt76_tx+0xbc/0x3c0 [mt76]
<7>[70544.520525] mt7915_eeprom_get_power_delta+0x1928/0x2580 [mt7915e]
<7>[70544.526688] __ieee80211_schedule_txq+0xe60/0x1b30 [mac80211]
<7>[70544.532442] __ieee80211_xmit_fast+0x7b4/0x950 [mac80211]
<7>[70544.537837] __ieee80211_subif_start_xmit+0x1e8/0x354 [mac80211]
<7>[70544.543839] ieee80211_subif_start_xmit+0x3c/0x3bc [mac80211]
<7>[70544.549580] ieee80211_subif_start_xmit_8023+0x318/0x430 [mac80211]
<7>[70544.555841] dev_hard_start_xmit+0xe4/0x180
<7>[70544.560012] __dev_queue_xmit+0x968/0xc30
<7>[70544.564006] dev_queue_xmit+0x10/0x20
<7>[70544.567652] br_dev_queue_push_xmit+0x9c/0x1b4
<7>[70544.572083] br_forward_finish+0x98/0xb0
<7>[70544.575990] __br_forward+0x138/0x1a0
<7>[70544.579637] br_forward+0x124/0x150
<7>[70544.583111] br_dev_xmit+0x208/0x3ec
<7>[70544.586672] dev_hard_start_xmit+0xe4/0x180
<7>[70544.590838] __dev_queue_xmit+0x968/0xc30
<7>[70544.594831] dev_queue_xmit+0x10/0x20
<7>[70544.598478] ip_finish_output2+0x204/0x4b0
<7>[70544.602560] __ip_finish_output+0x9c/0x190
<7>[70544.606640] ip_finish_output+0x30/0xd0
<7>[70544.610461] ip_output+0x98/0x120
<7>[70544.613760] ip_forward_finish+0x84/0xc0
<7>[70544.617667] ip_forward+0x458/0x510
<7>[70544.621140] ip_rcv_finish+0x8c/0xb0
<7>[70544.624699] ip_rcv+0x98/0xcc
<7>[70544.627652] __netif_receive_skb_one_core+0x44/0x50
<7>[70544.632513] __netif_receive_skb+0x14/0x60
<7>[70544.636592] process_backlog+0xac/0x1e0
<7>[70544.640412] __napi_poll+0x54/0x1b0
<7>[70544.643885] net_rx_action+0x2a0/0x320
<7>[70544.647618] _stext+0x10c/0x28c
<7>[70544.650746] do_softirq+0x8c/0xa0
<7>[70544.654049] __local_bh_enable_ip+0xa0/0xa4
<7>[70544.658216] napi_threaded_poll+0x120/0x1a0
<7>[70544.662382] kthread+0x11c/0x130
<7>[70544.665599] ret_from_fork+0x10/0x20
<0>[70544.669161] Code: f90002a0 52800002 f90006a1 f900a275 (f9000035)
<4>[70544.675234] ---[ end trace 700fb61e6e89cfa1 ]---
<0>[70544.685456] Kernel panic - not syncing: Oops: Fatal exception in interrupt
<2>[70544.692310] SMP: stopping secondary CPUs
<0>[70544.696216] Kernel Offset: disabled
<0>[70544.699687] CPU features: 0x0,00000000,20000802
<0>[70544.704201] Memory Limit: none
What firmware version are you using? It’ll help the devs, since it’s not obvious from the crash log.
You could try using GL.iNet’s snapshot firmware, but as noted in the posts above, it does have issues of its own.
I’m using the latest “stable” version 4.5.6 I’ve already tried the 4.5.7 snapshot and this one is even worse! I believe there has been enough time for the company to issue an opinion on so many problems we are facing!
I have about 3 devices with GLiNet, this is the first time that the MT6000 is having so much issues and can’t be resolve even after almost 1 months of time that people reporting here and there including myself, and all are actually having different kind of slowness on different channel even with the same firmware.
Perhaps the dev team can quick resolve (although Chinese New Year is coming next week), but I hope all the things can be settle down in Q1 2024, else more people buying this router will trigger refund or return, increase the burden of your sales and support pipeline as well.
Cheers and Happy Chinese New Year in advance. @alex_zheng
When trying firmware 4.5.7 did you perform a complete reset? Since it’s a downgrade to a much older version of OpenWrt you shouldn’t keep any settings.
Originally I was going to suggest using OpenWrt snapshots instead, since I’ve been using them for over a month and everythings stable and working. But the 2.4GHz radio still doesn’t perform as well as it should, so that could be a problem for IoT devices.
firmware version: 4.5.6
When the 2.4GHz channel was set to 1, the client device, which was showing significant latency, was able to communicate with the client device in a stable and reliable communication. Of course, I have confirmed with an analyzer that this is not due to the environment.
The mt76 main branch of Openwrt has fixed the connection problem with apple devices at 5GHz 160Mhz bandwidth.
Sorry to bother you. Could you please show me a pic the adapter of your area ? We can arrange one for you.
From your log It seems like a ethernet crash. Is the first time you met this issue?
Yes, It has been a long time. We are working on it for a long time but the issue is a bit more difficult. We need more time on it.
@Jounouchi Thanks very much and wish you a good day. We are turning to close source wifi version these days. we will have a inner version next week, to a better experience for you guys. We will do some test first. So maybe the firmware will release to you in the late Feb （because Chinese new year）.
We have confidence to solve the problem. And thanks for your understanding.
“I notice little interaction from the company”
Not true, the company gl-inet is very engaged on this forum, more than any other pro-consumer router company that I know.
They regularly answer questions here.
They also provide regular bug fixes and snapshot code releases announced here.
Some may critique their code release methodology but I appreciate the ability to chat on a forum directly with gl-inet employees.
I own more than 10 gl-inet devices myself, including the 3 x Flint1 and 2 x Flint2, several Beryl and a Spitz 5G.
The way I see it, these are devices for enthusiasts like myself and not the off the shelf “Best Buy” type routers.
Therefore we have to be okay with some messing around.
Maybe I’m misinformed but reading this thread everyday my take is that the WiFi issues on the Flint2 may end up being fixed in software, or they may end up being a bad hardware decision, hopefully it’s software.
Thanks