Release Asuswrt-Merlin 3006.102.7 is now available

[r3versii]

@RMerlin thanks. Could you check what your settings are on the shield? I'm running on Experience 9.2.4 so that's the latest and greatest. But there's settings for roaming and low powered wifi on the shield, maybe that has to be a specific setting. I also specified in the Shield itself that it has to connect to 5 GHz only, did you enforce it like that too?

 

[RMerlin]

@RMerlin thanks. Could you check what your settings are on the shield? I'm running on Experience 9.2.4 so that's the latest and greatest. But there's settings for roaming and low powered wifi on the shield, maybe that has to be a specific setting. I also specified in the Shield itself that it has to connect to 5 GHz only, did you enforce it like that too?

It's probably on default settings since I usually connect my Shield with an Ethernet cable. I just unplugged it, and connected to the BE92U wifi to test it.

The Shield is definitely on the 5 GHz band since I use different SSIDs per band.

 

[jzchen]

I have a GT-AX6000 and it's not working for me, as my phone only syncs at 144 Mbps and reports Wi-Fi 4/802.11n. It wasn't an issue prior to this firmware update. The router just won't let me enable it, which is annoying.

If it is an AiMesh node then depending on backhaul try AP mode or Repeater mode...

 

[RMerlin]

Roaming and Connect to Low Powered Channels are both disabled here.

 

[RMerlin]

JS error fixed on the Wireless Pro page (bad GPL merge), thank you for reporting it.

EDIT: uploaded a new test build with the fixed page.

 

[r3versii]

It's probably on default settings since I usually connect my Shield with an Ethernet cable. I just unplugged it, and connected to the BE92U wifi to test it.

The Shield is definitely on the 5 GHz band since I use different SSIDs per band.

Well maybe that's part of the issue, I use the same SSID for both (actually all 3) bands

 

[MDM]

> The Shield is definitely on the 5 GHz band since I use different SSIDs per band.

Well maybe that's part of the issue, I use the same SSID for both (actually all 3) bands

Practically always a bad idea, separate ALL SSIDs for peace of mind...

 

[RMerlin]

Well maybe that's part of the issue, I use the same SSID for both (actually all 3) bands

Just to confirm it, try configuring a 5 GHz Guest Network (make sure LAN access is still allowed, if your ShieldTV is accessing a local file server), and connect your Shield to it.

 

[dinko05]

Thanks. As someone with the clock reset issue (my latest one is this one): ```
Mar 14 10:05:42 et12 kernel: In wl_dfs_cac_notify_status chanspec 0xea32 DFS state 0
Aug 23 04:38:58 router kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:0:26364]
Aug 23 04:38:58 router kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
Aug 23 04:38:58 router kernel: Modules linked in: tdts_udbfw(PO) init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000d0c000 - ffffff8000d11000)
Aug 23 04:38:58 router kernel: rcu: 1-...!: (32 ticks this GP) idle=97e/0/0x1 softirq=1960676/1960685 fqs=0
Aug 23 04:38:58 router kernel: tdts_udb(PO) init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001bdd000 - ffffff8001bfd000)
Aug 23 04:38:58 router kernel: rcu: (detected by 0, t=900726557986 jiffies, g=981037, q=775)
Aug 23 04:38:58 router kernel: tdts(PO) init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001e28000 - ffffff8001e78000)
Aug 23 04:38:58 router kernel: Task dump for CPU 1:
Aug 23 04:38:58 router kernel: wireguard init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001bba000 - ffffff8001bd3000)
Aug 23 04:38:58 router kernel: swapper/1 R
Aug 23 04:38:58 router kernel: nf_nat_ftp init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000c03000 - ffffff8000c04000)
Aug 23 04:38:58 router kernel: running task 0 0 1 0x0000000a
Aug 23 04:38:58 router kernel: nf_conntrack_ftp init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000b04000 - ffffff8000b05000)
Aug 23 04:38:58 router kernel: Call trace:
Aug 23 04:38:58 router kernel: xt_length init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff80009ec000 - ffffff80009ed000)
Aug 23 04:38:58 router kernel: __switch_to+0xe8/0x170
Aug 23 04:38:58 router kernel: sr_mod init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000bd1000 - ffffff8000bd4000)
Aug 23 04:38:58 router kernel: 0xffffff800809bef0
Aug 23 04:38:58 router kernel: cdrom init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000b88000 - ffffff8000b8e000)
Aug 23 04:38:58 router kernel: rcu: rcu_sched kthread starved for 900726558066 jiffies! g981037 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=3
Aug 23 04:38:58 router kernel: thfsplus(O) init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000df4000 - ffffff8000e03000)
Aug 23 04:38:58 router kernel: rcu: RCU grace-period kthread stack dump:
Aug 23 04:38:58 router kernel: tntfs(PO) init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001daa000 - ffffff8001dfc000)
Aug 23 04:38:58 router kernel: rcu_sched R running task 0 11 2 0x00000008
Aug 23 04:38:58 router kernel: Call trace:
Aug 23 04:38:58 router kernel: tfat(PO) init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001b66000 - ffffff8001ba1000)
Aug 23 04:38:58 router kernel: __switch_to+0x148/0x170
Aug 23 04:38:58 router kernel: nls_cp437 init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000a35000 - ffffff8000a36000)
Aug 23 04:38:58 router kernel: __schedule+0x214/0x5a0
Aug 23 04:38:58 router kernel: uas init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000a0d000 - ffffff8000a10000)
Aug 23 04:38:58 router kernel: schedule+0x38/0xa0
Aug 23 04:38:58 router kernel: usb_storage init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000cfb000 - ffffff8000d00000)
Aug 23 04:38:58 router kernel: schedule_timeout+0x15c/0x2a0
Aug 23 04:38:58 router kernel: sg init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000adf000 - ffffff8000ae6000)
Aug 23 04:38:58 router kernel: rcu_gp_kthread+0x488/0x900
Aug 23 04:38:58 router kernel: sd_mod init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000997000 - ffffff800099e000)
Aug 23 04:38:58 router kernel: kthread+0x118/0x150
Aug 23 04:38:58 router kernel: scsi_mod init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8000c3c000 - ffffff8000c4f000)
Aug 23 04:38:58 router kernel: ret_from_fork+0x10/0x24
Aug 23 04:38:58 router kernel: ipheth init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001da5000 - ffffff8001da6000)
Aug 23 04:38:58 router kernel: rcu: INFO: rcu_bh detected stalls on CPUs/tasks:
Aug 23 04:38:58 router kernel: qmi_wwan init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d94000 - ffffff8001d96000)
Aug 23 04:38:58 router kernel: rcu: 1-...!: (36499 ticks this GP) idle=97e/0/0x1 softirq=1933001/1960685 fqs=0
Aug 23 04:38:58 router kernel: cdc_wdm init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d8a000 - ffffff8001d8c000)
Aug 23 04:38:58 router kernel: rcu: (detected by 0, t=900726558217 jiffies, g=-831, q=2)
Aug 23 04:38:58 router kernel: cdc_ncm init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d7d000 - ffffff8001d80000)
Aug 23 04:38:58 router kernel: Task dump for CPU 1:
Aug 23 04:38:58 router kernel: swapper/1 R
Aug 23 04:38:58 router kernel: rndis_host
Aug 23 04:38:58 router kernel: running task 0 0 1 0x0000000a
Aug 23 04:38:58 router kernel: init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d75000 - ffffff8001d76000)
Aug 23 04:38:58 router kernel: Call trace:
Aug 23 04:38:58 router kernel: cdc_ether init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d6c000 - ffffff8001d6d000)
Aug 23 04:38:58 router kernel: __switch_to+0xe8/0x170
Aug 23 04:38:58 router kernel: ax88179_178a init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d60000 - ffffff8001d63000)
Aug 23 04:38:58 router kernel: 0xffffff800809bef0
Aug 23 04:38:58 router kernel: asix init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d51000 - ffffff8001d55000)
Aug 23 04:38:58 router kernel: rcu: rcu_bh kthread starved for 900726558279 jiffies! g-831 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=2
Aug 23 04:38:58 router kernel: cdc_acm init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d44000 - ffffff8001d47000)
Aug 23 04:38:58 router kernel: rcu: RCU grace-period kthread stack dump:
Aug 23 04:38:58 router kernel: usbnet init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d35000 - ffffff8001d39000)
Aug 23 04:38:58 router kernel: rcu_bh I 0 12 2 0x00000008
Aug 23 04:38:58 router kernel: mii
Aug 23 04:38:58 router kernel: Call trace:
Aug 23 04:38:58 router kernel: init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d2c000 - ffffff8001d2e000)
Aug 23 04:38:58 router kernel: __switch_to+0xe8/0x170
Aug 23 04:38:58 router kernel: ohci_pci init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d23000 - ffffff8001d24000)
Aug 23 04:38:58 router kernel: __schedule+0x214/0x5a0
Aug 23 04:38:58 router kernel: ohci_platform init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d1a000 - ffffff8001d1b000)
Aug 23 04:38:58 router kernel: schedule+0x38/0xa0
Aug 23 04:38:58 router kernel: ohci_hcd init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d0b000 - ffffff8001d11000)
Aug 23 04:38:58 router kernel: schedule_timeout+0x15c/0x2a0
Aug 23 04:38:58 router kernel: ehci_pci init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001d02000 - ffffff8001d03000)
Aug 23 04:38:58 router kernel: rcu_gp_kthread+0x488/0x900
Aug 23 04:38:58 router kernel: ehci_platform init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001cf9000 - ffffff8001cfa000)
Aug 23 04:38:58 router kernel: kthread+0x118/0x150
Aug 23 04:38:58 router kernel: ehci_hcd init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001ce6000 - ffffff8001cef000)
Aug 23 04:38:58 router kernel: ret_from_fork+0x10/0x24
Aug 23 04:38:58 router crond[4770]: time disparity of 15012122 minutes detected
Aug 23 04:38:58 router kernel: xhci_pci init_addr(0000000000000000 - 0000000000000000), core_addr(ffffff8001cdd000 - ffffff8001cde000)
```
I'll try out this new one now. This last trace was on 102.7_beta2. I just installed your new released beta build and will report back. The 102.7 already had 3 reboots since this morning so let's see .

Thanks for releasing this!!!
Romain