XT12 router mode frequent reboot by unknown reason

[Subaru]

Hello seniors,


I am facing XT12 router mode frequent reboot by unknown reason, I cannot avoid issue via downgrade or upgrade FW version (will reboot via manully after every downgrade or upgrade), and ASUS CS always reply me: 1. The SW engineer has not find any reason in logs, 2. HW tester cannot reproduce, but replaced 2 adaters to me.
about number 2 respone, when I recevied RMA back items, I am soon start test, but happen same issue immdiately, and ASUS was rejected my request for change new XT12.

Below is my network chart and devices,
Modem (bridge mode) <---Cat.6 cable---> XT12 (Router, PPPoE, WPA2/3 mixed) <---5GHz-2 (WPA3)---> XT12 node (WPA2/3 mixed)
Only 1 PC working on 2.5Gbps with Cat.6 cable connect to router.
WiFi clients details: 2 cleaners are connect router and node respectively by 2.4GHz WiFi. 1 Nintendo switch, 1 Chromecast 4K and 6 mobiles are roaming between router and node via 5GHz-1 WiFi.

Below steps are my test operations, based on first 388 and newest FW.
1. The 2 adaters switch. → Router crash.
2. Based step.1, I switch XT12 mode (Router to node, node to router). → Router crash.
So, maybe HW or FW issue right? even whitch reason, if reasons are front prompt, it should reproduce easy on ASUS repair station, but result is nagative.
I am sure my house power supply is normal working, if power supply abnormal, my desktop, node and modem should impact.
BTW, I had found WiFi 5GHz-1 driver version is not static in one version via Merlin FW, is it normal?

Below is short history and download after problem happened, I upload log files in attachment.

Jan 11 15:16:04 kernel: No wdev corresponding to bssidx: 0x5 found! Ignoring event.
Jan 11 15:16:04 ahs: ===Terminate ahs daemon===
Jan 11 15:16:05 kernel: netlink: 12 bytes leftover after parsing attributes in process `ip'.
Jan 11 15:16:07 kernel: port_generic_stop 572 skip turnning off power on eth1 here
Jan 11 15:16:07 kernel: port_generic_stop 572 skip turnning off power on eth2 here
Jan 11 15:16:07 kernel: port_generic_stop 572 skip turnning off power on eth3 here
Jan 11 15:16:07 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Jan 11 15:16:07 kernel: In wl_dfs_cac_notify_status chanspec 0x1909 DFS state 0
Jan 11 15:16:07 kernel: In wl_dfs_cac_notify_status chanspec 0xee32 DFS state 0
Jan 11 15:16:07 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Jan 11 15:16:07 kernel: In wl_dfs_cac_notify_status chanspec 0xef72 DFS state 0
Jan 11 15:16:08 get_ext_phy_id: 2/1/0/0
Jan 11 15:16:08 kernel: enet_ioctl_compat_ethctl:L1773 No PHY type PHY_TYPE_UNKNOWN at address 30 has been found.
Jan 11 15:16:08 kernel: enet_ioctl_compat_ethctl:L1773 No PHY type PHY_TYPE_UNKNOWN at address 30 has been found.
May 5 13:05:14 kernel: klogd started: BusyBox v1.24.1 (2022-12-15 08:43:59 CST)
May 5 13:05:14 kernel: Linux version 4.19.183 (gitserv_asus@bpza001bud) (gcc version 9.2.0 (Buildroot 2019.11.1)) #1 SMP PREEMPT Thu Dec 15 08:45:51 CST 2022
May 5 13:05:14 kernel: random: get_random_bytes called from start_kernel+0x9c/0x454 with crng_init=0
May 5 13:05:14 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe console=ttyAMA0,115200 earlycon rootwait mtdparts=brcmnand.0:2097152(loader),264241152@2097152(image),524288@266338304(crashlog) root=/dev/ubiblock0_6 ubi.mtd=image ubi.block=0,6 rootfstype=squashfs cma=0M
May 5 13:05:14 kernel: mtusize 1500
May 5 13:05:14 kernel: CCI hardware cache coherency enabled
May 5 13:05:14 kernel: bootloader version U-Boot 2019.07 (Dec 15 2022 - 10:33:50 +0800), Build: 5.04L.0
May 5 13:05:14 kernel: inMemNvramData.szBoardId XT12_gpy211
May 5 13:05:14 kernel: size of sk_buff 512
May 5 13:05:14 kernel: offset of cb in sk_buff 368
May 5 13:05:14 kernel: PMC driver initcall
May 5 13:05:14 kernel: PMC driver scanning DT

Jan 12 18:37:01 kernel: B8:4D:43:15:58:E1 not mesh client, can't update it's ip
Jan 12 18:37:01 rc_service: amas_lib 2492:notify_rc restart_firewall
Jan 12 18:37:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7769)]do webs_update
Jan 12 18:37:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7787)]retrieve firmware information
Jan 12 18:37:15 WATCHDOG: [FAUPGRADE][auto_firmware_check7790)]user in use
Jan 12 18:37:22 kernel: B8:4D:43:15:58:E1 not mesh client, can't update it's ip
Jan 12 18:37:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7769)]do webs_update
Jan 12 18:37:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7787)]retrieve firmware information
Jan 12 18:37:45 WATCHDOG: [FAUPGRADE][auto_firmware_check7790)]user in use
Jan 12 18:38:33 kernel: B8:4D:43:15:58:E1 not mesh client, can't update it's ip
Jan 12 18:42:20 rc_service: httpds 2422:notify_rc start_sig_check
Jan 12 18:42:23 BWDPI: fun bitmap = 53f
Jan 12 18:43:03 kernel: 04:42:1A:CD:EE:C0 not mesh client, can't delete it
Jan 12 18:43:33 kernel: B8:4D:43:15:58:E1 not mesh client, can't update it's ip
May 5 13:05:17 kernel: klogd started: BusyBox v1.24.1 (2023-01-12 11:08:09 CST)
May 5 13:05:17 kernel: Linux version 4.19.183 (chengche@AA1400153-PLX) (gcc version 9.2.0 (Buildroot 2019.11.1)) #1 SMP PREEMPT Thu Jan 12 11:08:53 CST 2023
May 5 13:05:17 kernel: random: get_random_bytes called from start_kernel+0x9c/0x454 with crng_init=0
May 5 13:05:17 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe console=ttyAMA0,115200 earlycon rootwait mtdparts=brcmnand.0:2097152(loader),264241152@2097152(image),524288@266338304(crashlog) root=/dev/ubiblock0_4 ubi.mtd=image ubi.block=0,4 rootfstype=squashfs cma=0M
May 5 13:05:17 kernel: mtusize 1500
May 5 13:05:17 kernel: CCI hardware cache coherency enabled
May 5 13:05:17 kernel: bootloader version U-Boot 2019.07 (Jan 12 2023 - 13:43:06 +0800), Build: 5.04L.0

 

[Prasanna Ariyanayagam]

I think I am having the same problems. Did you resolve this?

 

[Subaru]

I think I am having the same problems. Did you resolve this?

No, and ASUS cannot fix this issue, I got refund at January