What's new

Asus CT8 keeps going down, Please Help!

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

johnday29

New Around Here
I spent 12hrs trying to figure out what is going on and seem to fix one thing only to have another problem come up. When I went to bed last night everything was working, this morning there was no internet and the routers GUI was not responsive. I unpowered and rebooted the router and when it came up everything seem to work fine for just a while but then had it all crash again. I did not notice when I woke up and it wasn't working that none of the radios showed up on a wifi scan except 5g 2 and it would not connect. I have updated to the latest firmware but have not done a factory reset, don't want to loose all my settings if I don't have to. When I look at the logs I notice that every time things start going wrong the date on the logs changes from today July 24th to May 5th I am guessing that may be significant possibly. Here is a snippet of my log showing just before, and during. I have included a txt file with a longer version of the log with before, during and after the time change. Can anyone tell me if anything here gives a clue as to what is happening?

Jul 24 09:07:36 kernel: STOPPED EVENT for vap 1 (cc3a4000)
Jul 24 09:07:37 kernel: [UNSPECIFIED] ol_scan_unregister_event_handler: Failed to unregister evhandler=bf61586c arg=ce8124c0
Jul 24 09:07:37 kernel: [UNSPECIFIED] ol_scan_unregister_event_handler: Failed to unregister evhandler=bf61586c arg=ce8124c0
Jul 24 09:07:37 kernel: [UNSPECIFIED] ol_scan_unregister_event_handler: Failed to unregister evhandler=bf615e38 arg=ce8124c0
Jul 24 09:07:37 kernel: send_vdev_delete_cmd_non_tlv for vap 1
Jul 24 09:07:37 kernel: ol_ath_vap_delete: wmi_unified_vdev_delete_send done ID = 1 vap (ca940000) VAP Addr = ae:5e:45:f2:e0:14:
Jul 24 09:07:37 kernel: ieee80211_mbo_vdetach: MBO terminated
Jul 24 09:07:37 kernel: ieee80211_oce_vdetach: OCE terminated
Jul 24 09:07:37 kernel: Suspending Target scn=cb4004c0
Jul 24 09:07:37 kernel: waiting for target paused event from target
Jul 24 09:07:37 kernel: ol_ath_thermal_mitigation_detach: ++
Jul 24 09:07:37 kernel: ol_ath_thermal_mitigation_detach: --
Jul 24 09:07:37 kernel: ol_if_dfs_clist_update: called, cmd=1, nollist= (null), nentries=0
Jul 24 09:07:37 kernel: ce_h2t_tx_ce_cleanup 1039 Fastpath mode ON, Cleaning up HTT Tx CEsmart_log_deinit: Smart logging Disabled
Jul 24 09:07:37 kernel: hif_pci_device_reset: Reset Devicehif_pci_disable_bus: Xhif_disable: Xhif_napi_destroy: NAPI 6 destroyed
Jul 24 09:07:37 kernel: hif_napi_destroy: no NAPI instances. Zapped.ath_sysfs_diag_fini: diag_fsattr
Jul 24 09:07:37 kernel: channel is not 2.4G return faile^M
Jul 24 09:07:37 kernel: ath_lowi_if_netlink_delete Going to decrement current LOWI netlink ref count: 3
Jul 24 09:07:37 kernel: ol_if_dfs_clist_update: called, cmd=1, nollist= (null), nentries=0
Jul 24 09:07:37 kernel: channel is not 2.4G return faile^M
Jul 24 09:07:37 kernel: Green-AP : Detached
Jul 24 09:07:37 kernel: ol_ath_detach: remove global_ic[2]..gloabl_ic ptr:bf699c70
Jul 24 09:07:37 kernel: ol_ath_detach: Peer Count 531
Jul 24 09:07:37 kernel: ath_lowi_if_netlink_delete Going to decrement current LOWI netlink ref count: 2
Jul 24 09:07:37 kernel: ol_if_dfs_clist_update: called, cmd=1, nollist= (null), nentries=0
Jul 24 09:07:37 kernel: channel is not 2.4G return faile^M
Jul 24 09:07:37 kernel: Green-AP : Detached
Jul 24 09:07:37 kernel: ol_ath_detach: remove global_ic[1]..gloabl_ic ptr:bf699c70
Jul 24 09:07:37 kernel: ol_ath_detach: Peer Count 531
Jul 24 09:07:37 kernel: ath_lowi_if_netlink_delete Going to decrement current LOWI netlink ref count: 1
Jul 24 09:07:37 kernel: ol_if_dfs_clist_update: called, cmd=1, nollist= (null), nentries=0
Jul 24 09:07:37 kernel: Green-AP : Detached
Jul 24 09:07:37 kernel: ol_ath_detach: remove global_ic[0]..gloabl_ic ptr:bf699c70
Jul 24 09:07:37 kernel: ol_ath_detach: Peer Count 531
Jul 24 09:07:41 kernel: _nvram_free: 1(init) nvram_idx(1 / 2)
May 5 00:05:30 kernel: klogd started: BusyBox v1.25.1 (2022-02-16 10:00:42 CST)
May 5 00:05:30 INIT: firmware version: 3.0.0.4_386_46122-g69c792f
May 5 00:05:30 kernel: Linux version 3.14.77 (Gabriel@localdomain) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #1 SMP PREEMPT Wed Feb 16 10:03:22 CST 2022
May 5 00:05:30 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64512
May 5 00:05:30 kernel: Kernel command line: root_rfs=0x00225d80 flash_type=nand ubi.mtd=UBI_DEV clk_ignore_unused
May 5 00:05:30 kernel: Memory: 251132K/260096K available (4298K kernel code, 200K rwdata, 1200K rodata, 176K init, 537K bss, 8964K reserved, 0K highmem)
May 5 00:05:30 kernel: Virtual kernel memory layout:
May 5 00:05:30 kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB)
May 5 00:05:30 kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
May 5 00:05:30 kernel: vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
May 5 00:05:30 kernel: lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
May 5 00:05:30 kernel: pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
May 5 00:05:30 kernel: modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
May 5 00:05:30 kernel: .text : 0xc0208000 - 0xc0766be8 (5499 kB)
May 5 00:05:30 kernel: .init : 0xc0767000 - 0xc0793180 ( 177 kB)
May 5 00:05:30 kernel: .data : 0xc0794000 - 0xc07c6174 ( 201 kB)
May 5 00:05:30 kernel: .bss : 0xc07c6174 - 0xc084c6a8 ( 538 kB)
May 5 00:05:30 kernel: _ Reboot message ... _______________________________________________________
May 5 00:05:30 kernel: >>> Emergency Sync complete
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> IDPfw: Exit IDPfw
May 5 00:05:30 kernel: >>> mod epilog takes 0 jiffies
May 5 00:05:30 kernel: >>> IDPfw: Exit IDPfw
May 5 00:05:30 kernel: >>> Exit chrdev /dev/idpfw with major 191
May 5 00:05:30 kernel: >>> *** ERROR: [udb_shell_mod_exit:661] Udb static = 0, dynamic = 16
May 5 00:05:30 kernel: >>>
May 5 00:05:30 kernel: >>> Exit chrdev /dev/idp with major 190
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> nvram_commit(): pid 1 comm [init]
May 5 00:05:30 kernel: >>> _nvram_free: 1(init) nvram_idx(0 / 2)
May 5 00:05:30 kernel: >>> found private data block and skip it
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
May 5 00:05:30 kernel: >>> br0: received packet on eth1 with own address as source address
 

Attachments

  • Asus ct8 log.txt
    103.6 KB · Views: 77
You may have to reset your system to factory default and set it up again manually. Don't use saved configuration files from previous firmware versions. I would do basic setup first to check Router and Node connection stability. Keep Wireless settings close to default. Avoid use of DFS channels. Don't use the router as NAS, it may cause system instability. May 5th indicates router reboot.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top