Asus RT-AX3000 reboots every 3 or 4 days with a crashlog

[buildingonsuccess]

I'm not sure if I am in the right place, but am struggling to find an resolution anywhere for my router reboot issue.

Long story short, I've been an ASUS guy forever, and now came the time to get rid of my n66u routers with tomato. I opted for an Asus RT-AX3000. I also have an access point which is the same. Randomly I was getting a reboot and crash.

I've tried stock ASUS firmware, but also Merlin Firmware, stable/release, alpha, beta - still crashes. I've tried different AI Mesh node hardware such as ASUS AC1900. I've replaced the RT-AX3000 hardware with new ones. But still I get a crash.

I have a pretty simple setup (ASUS RT-AX3000 as main router and ASUS RT-AX3000 as mesh node) or (ASUS RT-AX3000 as main router and ASUS AC1900). I never did try using the ASUS AC1900 as a main router as I wanted a little extra horsepower.

Current Firmware is at 386.2_beta1 - I can back it down to a stable release but I already tried that.

Also Wireless setup is simple:
Smart Connect - OFF
5G: Wireless mode Auto, everything else is disabled, Channel Bandwidth set to 80MHz, Enable 160 unchecked Control Channel 44
2.4G: Wireless mode Auto, everything else is disabled, Channel Bandwidth set to 40MHz, Control Channel 10

Help me! ASUS Merlin Gurus! Also can you teach me how to read the crashlog. I mean what's meaningfull in there?

is it this, or is that just chatter.

May  5 01:05:02 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set

Here is just the beginning of my crashlog error entries - attached is the whole log.

May  5 01:05:02 crashlog: LOG
May  5 01:05:02 crashlog: <6>device eth2 entered promiscuous mode
May  5 01:05:02 crashlog: <6>device eth1 entered promiscuous mode
May  5 01:05:02 crashlog: <6>device eth0 entered promiscuous mode
May  5 01:05:02 crashlog: <6>device eth5 entered promiscuous mode
May  5 01:05:02 crashlog: <4>Interface eth1 doesn't exist
May  5 01:05:02 crashlog: <4>could not find igs interface!
May  5 01:05:02 crashlog: <4>IGMP Query send failed
May  5 01:05:02 crashlog: <6>device eth6 entered promiscuous mode
May  5 01:05:02 crashlog: <6>br0: port 6(eth6) entered listening state
May  5 01:05:02 crashlog: <6>br0: port 6(eth6) entered listening state
May  5 01:05:02 crashlog: <6>br0: port 5(eth5) entered listening state
May  5 01:05:02 crashlog: <6>br0: port 5(eth5) entered listening state
May  5 01:05:02 crashlog: <4><=== Deactivate Deep Green Mode
May  5 01:05:02 crashlog: <6>br0: port 4(eth0) entered listening state
May  5 01:05:02 kernel: Linux version 4.1.52 (merlin@ubuntu-dev) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #1 SMP PREEMPT Wed Mar 10 11:50:22 EST 2021
May  5 01:05:02 crashlog: <6>br0: port 4(eth0) entered listening state
May  5 01:05:02 crashlog: <2>eth0 (Int switch port: 0) (Logical Port: 0) (phyId: 8) Link Up at 100 mbps full duplex
May  5 01:05:02 crashlog: <6>br0: port 6(eth6) entered learning state
May  5 01:05:02 crashlog: <6>br0: port 5(eth5) entered learning state
May  5 01:05:02 crashlog: <6>cfg80211: Calling CRDA to update world regulatory domain
May  5 01:05:02 crashlog: <2>eth2 (Int switch port: 2) (Logical Port: 2) (phyId: a) Link Up at 1000 mbps full duplex
May  5 01:05:02 crashlog: <6>br0: port 2(eth2) entered listening state
May  5 01:05:02 crashlog: <6>br0: port 2(eth2) entered listening state
May  5 01:05:02 crashlog: <6>br0: port 1(eth3) entered listening state
May  5 01:05:02 kernel: Kernel command line: isolcpus=2 root=ubi:rootfs_ubifs ubi.mtd=0 rootfstype=ubifs console=ttyAMA0 earlyprintk debug irqaffinity=0 pci=pcie_bus_safe
May  5 01:05:02 crashlog: <6>br0: port 1(eth3) entered listening state
May  5 01:05:02 crashlog: <2>eth3 (Int switch port: 3) (Logical Port: 3) (phyId: b) Link Up at 1000 mbps full duplex
May  5 01:05:02 crashlog: <6>br0: received packet on eth5 with own address as source address
May  5 01:05:02 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
May  5 01:05:02 kernel: Virtual kernel memory layout:
May  5 01:05:02 kernel:     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
May  5 01:05:02 crashlog: <6>br0: port 4(eth0) entered learning state
May  5 01:05:02 kernel:     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
May  5 01:05:02 crashlog: <6>br0: received packet on eth5 with own address as source address
May  5 01:05:02 kernel:     vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
May  5 01:05:02 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
May  5 01:05:02 kernel:     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
May  5 01:05:02 kernel:     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
May  5 01:05:02 crashlog: <6>br0: topology change detected, propagating
May  5 01:05:02 kernel:     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
May  5 01:05:02 crashlog: <6>br0: port 6(eth6) entered forwarding state
May  5 01:05:02 kernel:       .text : 0xc0018000 - 0xc05a2e18   (5676 kB)
May  5 01:05:02 kernel:       .init : 0xc05a3000 - 0xc05d6000   ( 204 kB)
May  5 01:05:02 crashlog: <6>br0: topology change detected, propagating
May  5 01:05:02 kernel:       .data : 0xc05d6000 - 0xc0606960   ( 195 kB)
May  5 01:05:02 crashlog: <6>br0: port 5(eth5) entered forwarding state
May  5 01:05:02 kernel:        .bss : 0xc0606960 - 0xc066cd84   ( 410 kB)
May  5 01:05:02 crashlog: <6>br0: received packet on eth5 with own address as source address
May  5 01:05:02 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
May  5 01:05:02 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
May  5 01:05:02 crashlog: <6>br0: received packet on eth5 with own address as source address
May  5 01:05:02 crashlog: <6>br0: received packet on eth5 with own address as source address
May  5 01:05:02 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver cdc_acm
May  5 01:05:02 crashlog: <6>cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver asix
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver ax88179_178a
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver cdc_ether
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver rndis_host
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver cdc_ncm
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver cdc_wdm
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver qmi_wwan
May  5 01:05:02 crashlog: <6>br0: port 2(eth2) entered learning state
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver cdc_mbim
May  5 01:05:02 crashlog: <6>br0: port 1(eth3) entered learning state
May  5 01:05:02 crashlog: <5>SCSI subsystem initialized
May  5 01:05:02 crashlog: <6>usbcore: registered new interface driver usb-storage

 

[Smokindog]

Did you try a complete factory reset and then re-flash? I know many will say it's redundant but when I run into situations like this I always try

1. Remover all connections from the router
2. Factory reset and wait 5 minutes after reboot
3. Flash target firmware and wait 5 minutes after reboot
4. Factory reset and wait 5 minutes after reboot
5. Reconnect router to network and perform a clean reconfiguration

Between steps make configuration changes only as required to get to the next step.

Everyone has their chicken bones and garlic, this is just my "goto recipe" that has served me well over the years.

 

[Lee MacMillan]

I'm seeing the same thing on my AX86u, also every 3-5 days. Just started a thread on it today after it reset last night after a little more than 5 days since the previous time. If the timing in the log is accurate (mine also shows the May 5 date), then the event only lasts 10-12 seconds which is shorter than a complete reboot. The one time it happened when I was working on the computer, I saw one of the white LEDs change to red for just a few seconds. Don't recall which one it was though. I have not done a factory reset yet. I flashed 386.1_2 over the stock firmware about a week after I got the router (on March 4th). I don't know if this was happening with stock firmware or not but per your post, it is.

 

[buildingonsuccess]

Did you try a complete factory reset and then re-flash? I know many will say it's redundant but when I run into situations like this I always try

1. Remover all connections from the router
2. Factory reset and wait 5 minutes after reboot
3. Flash target firmware and wait 5 minutes after reboot
4. Factory reset and wait 5 minutes after reboot
5. Reconnect router to network and perform a clean reconfiguration

Between steps make configuration changes only as required to get to the next step.

Everyone has their chicken bones and garlic, this is just my "goto recipe" that has served me well over the years.

Does buying new routers count? I actually bought 2 new replacements to rule out any odd hardware failures. Albeit I flashed them with the same Merlin Firmware. Do you think I still need to follow this procedure?

 

[L&LD]

New routers do not negate the need for a full reset to factory defaults.

 

[Lee MacMillan]

I flashed Merlin 386.2, did a factory reset and reconfigured from scratch. I have not had a spontaneous reboot since (over 10 days). It never went more than 5 days before and sometimes rebooted within 24 hours.