AX92U - rc_service: cfg_server 1392:notify_rc restart_wireless

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

screamjojo

Occasional Visitor
Hello all,

Can you please help me with the error log :

Code:
Jan 27 00:02:56 rc_service: cfg_server 1392:notify_rc restart_wireless
Jan 27 00:02:57 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Jan 27 00:02:57 kernel: ubi1: attaching mtd10
Jan 27 00:02:57 kernel: ubi1: scanning is finished
Jan 27 00:02:57 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
Jan 27 00:02:57 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jan 27 00:02:57 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jan 27 00:02:57 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Jan 27 00:02:57 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Jan 27 00:02:57 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Jan 27 00:02:57 kernel: ubi1: max/mean erase counter: 19/8, WL threshold: 4096, image sequence number: 60959913
Jan 27 00:02:57 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Jan 27 00:02:57 kernel: ubi1: background thread "ubi_bgt1d" started, PID 14696
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 14725
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID XXXX, small LPT model
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Jan 27 00:02:58 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
Jan 27 00:02:58 kernel: ubi1: detaching mtd10
Jan 27 00:02:58 kernel: ubi1: mtd10 is detached
Jan 27 00:03:02 acsd: eth5: Selecting 2g band ACS policy
Jan 27 00:03:02 wlceventd: wlceventd Start...
Jan 27 00:03:04 wlceventd: wlceventd_proc_event(499): eth7: Auth 04:D9:F5:xxxx, status: Successful (0)
Jan 27 00:03:04 wlceventd: wlceventd_proc_event(527): eth7: Assoc 04:D9:F5:Bxxxx, status: Successful (0)
Jan 27 00:03:04 kernel: wfd_registerdevice Successfully registered dev wds2.0.1 ifidx 1 wfd_idx 2
Jan 27 00:03:04 kernel: Register interface [wds2.0.1]  MAC: 04:d9xxxx
Jan 27 00:03:05 acsd: eth5: selected channel spec: 0x1001 (1)
Jan 27 00:03:05 acsd: eth5: Adjusted channel spec: 0x1001 (1)
Jan 27 00:03:05 acsd: eth5: selected channel spec: 0x1001 (1)
Jan 27 00:03:05 acsd: acs_set_chspec: 0x1001 (1) for reason APCS_INIT
Jan 27 00:03:05 acsd: eth6: Selecting 5g band ACS policy
Jan 27 00:03:08 acsd: eth6: selected channel spec: 0xe03a (52/80)
Jan 27 00:03:08 acsd: eth6: Adjusted channel spec: 0xe03a (52/80)
Jan 27 00:03:08 acsd: eth6: selected channel spec: 0xe03a (52/80)
Jan 27 00:03:08 acsd: acs_set_chspec: 0xe03a (52/80) for reason APCS_INIT
Jan 27 00:03:13 kernel: wfd_registerdevice Successfully registered dev wds0.0.1 ifidx 1 wfd_idx 0
Jan 27 00:05:16 rc_service: cfg_server 1392:notify_rc restart_wireless
Jan 27 00:05:17 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Jan 27 00:05:17 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Jan 27 00:05:17 kernel: ubi1: attaching mtd10
Jan 27 00:05:17 kernel: ubi1: scanning is finished
Jan 27 00:05:17 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
Jan 27 00:05:17 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jan 27 00:05:17 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jan 27 00:05:17 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Jan 27 00:05:17 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Jan 27 00:05:17 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Jan 27 00:05:17 kernel: ubi1: max/mean erase counter: 19/8, WL threshold: 4096, image sequence number: 60959913
Jan 27 00:05:17 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Jan 27 00:05:17 kernel: ubi1: background thread "ubi_bgt1d" started, PID 15326
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 15373
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): reserved for root: 0 bytes (0 KiB)
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID XXXX, small LPT model
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Jan 27 00:05:18 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
Jan 27 00:05:18 kernel: ubi1: detaching mtd10
Jan 27 00:05:18 kernel: ubi1: mtd10 is detached
Jan 27 00:05:22 acsd: eth5: Selecting 2g band ACS policy
Jan 27 00:05:22 wlceventd: wlceventd Start...
Jan 27 00:05:22 wlceventd: wlceventd_proc_event(464): eth5: Deauth_ind F4:81:39:31xx, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 27 00:05:22 wlceventd: wlceventd_proc_event(464): eth5: Deauth_ind F4:81:39:xx, status: 0, reason: Class 3 frame received from nonassociated station (7)
Jan 27 00:05:23 wlceventd: wlceventd_proc_event(499): eth6: Auth 84:C5:A6:xxx, status: Successful (0)
Jan 27 00:05:23 wlceventd: wlceventd_proc_event(509): eth6: ReAssoc 84:C5:A6xxx, status: Successful (0)
Jan 27 00:05:26 acsd: eth5: selected channel spec: 0x1009 (9)
Jan 27 00:05:26 acsd: eth5: Adjusted channel spec: 0x1009 (9)
Jan 27 00:05:26 acsd: eth5: selected channel spec: 0x1009 (9)
Jan 27 00:05:26 acsd: acs_set_chspec: 0x1009 (9) for reason APCS_INIT
Jan 27 00:05:26 acsd: eth6: Selecting 5g band ACS policy
Jan 27 00:05:28 acsd: eth6: selected channel spec: 0xe03a (52/80)
Jan 27 00:05:28 acsd: eth6: Adjusted channel spec: 0xe03a (52/80)
Jan 27 00:05:28 acsd: eth6: selected channel spec: 0xe03a (52/80)
Jan 27 00:05:28 acsd: acs_set_chspec: 0xe03a (52/80) for reason APCS_INIT
Jan 27 00:05:34 kernel: wfd_registerdevice Successfully registered dev wds0.0.2 ifidx 2 wfd_idx 0
Jan 27 00:05:34 wlceventd: wlceventd_proc_event(499): eth7: Auth 04:D9:xxxx, status: Successful (0)
Jan 27 00:05:34 wlceventd: wlceventd_proc_event(527): eth7: Assoc 04:D9:xxxx, status: Successful (0)
Jan 27 00:05:34 kernel: wfd_registerdevice Successfully registered dev wds2.0.1 ifidx 1 wfd_idx 2
Jan 27 00:05:34 kernel: Register interface [wds2.0.1]  MAC: 04:d9xxxx
Jan 27 01:00:08 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Jan 27 01:00:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 01:15:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 01:30:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 01:45:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 02:00:08 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Jan 27 02:00:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 02:15:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 02:30:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 02:45:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 03:00:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 03:15:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 03:30:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 03:45:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 04:00:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 04:08:54 ahs: [read_json]Update ahs JSON file.
Jan 27 04:09:24 ahs: [read_json]Update ahs JSON file.
Jan 27 04:09:54 ahs: [read_json]Update ahs JSON file.
Jan 27 04:15:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 04:30:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 04:45:21 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 05:00:21 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 05:15:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 05:30:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 05:45:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 06:00:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 06:15:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 06:30:20 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 06:45:21 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22
Jan 27 07:00:21 acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22

Why my wifi restart with "rc_service: cfg_server 1392:notify_rc restart_wireless" ?
What is "kernel: ubi1: attaching mtd10" / "acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22" ?

I've the firmware 3.0.0.4.384_9177 with no problem during 10 days ...
AI protection : Enable
Adaptative QOS : Enable
Wireless : Control Channel : Auto
AIcloud : Disable
Smart Connect : Disable
Wifi settings is defaut settings except 2.4ghz with channel bandwidth 20 MHZ only

I notice the error log begin when I've enable wireless scheduler, but maybe it just a coincidence ?

Thanks for your help
 

L&LD

Part of the Furniture
What is the issue? You're simply curious about the logs, or is there a problem to be solved?
 

screamjojo

Occasional Visitor
Wifi crash when "rc_service: cfg_server 1392:notify_rc restart_wireless"
and for the other message I'm curious :)
 

L&LD

Part of the Furniture

leerees

Regular Contributor
It looks related to scanning the DFS channels. I'm not sure what the error means. Maybe check your wireless log and see if there's anything in there. Are you actually having trouble with the WiFi?
 

screamjojo

Occasional Visitor
Sorry I think the log "rc_service: cfg_server 1392:notify_rc restart_wireless" appears when I enable wireless scheduler, and the "acsd: acs_scan_timer_or_dfsr_check(1305): cs scan failed ret code: -22" come when the 160Mhz is disabled.
Thanks for your help and sorry.
 

Sign Up For SNBForums Daily Digest

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