Asus RT-AX86U error: acs_start eth7 cannot select chanspec with the wrong info

[jorhett]

FYI, I've been seeing the same problem. I posted my details and logs in this thread https://www.snbforums.com/threads/w...s-reboot-acsd-start-up-at-exactly-11pm.90759/

Same as others: Aimesh AX86U with AC86U as the aimesh node. I use fixed channels, live with many surrounding houses with total pollution of the space and Auto never, ever works correctly. Every time I reboot acsd is not running, but it appears to start up on its own at 11pm every 4th day, just after disk_monitor in the logs. I can't find what scheduled event is causing this, as it's not in the cron. (logs and other details in the thread above)

 

[Qbcd]

I solved this problem by changing my router to an AX89X. The AX86U and AX86S both had the issue. The AX89X doesn't, I'm guessing because it uses a Qualcomm chip, not Broadcom. The wireless log looks different on the AX89X, the firmware is probably somewhat different.

However, I now want to upgrade to the BE86U. I'm afraid it's gonna have the issue given it's a Broadcom chip and generally the same product line as the AX86S/U/Pro, with probably the same firmware... So I wanted to ask if anyone with the BE86U has experienced this issue...

 

[iFrogMac]

I have an AX86U with firmware version: Version 3.0.0.4.388_24339 on it (latest version on the support site). I don't have any AIMesh nodes, and before I changed routers, I wasn't having any random disconnects, so I had no reason to look at logs. Should I fire it up at some point as the main router to see if I get the error, or since I only use it as a stand alone router with no nodes, is mine exempt from the situation ?

PS, I have it configured with manual channel selection on both bands:
Channel 36 for 5Ghz with 160Mhz enabled, and DFS disabled.
Channel 6 for 2.4Ghz.

 

[iFrogMac]

Since I haven't seen activity here for a while, I'm going to assume the problem was resolved. However, in the event it hasn't been, here is a clip from my RT-AX86U's system log this morning from the latest firmware:
I did not notice any of the reported messages reported above.

Jun 24 22:36:56 WATCHDOG: [FAUPGRADE][auto_firmware_check7952)]do webs_update
Jun 24 22:36:56 WATCHDOG: [FAUPGRADE][auto_firmware_check7970)]retrieve firmware information
Jun 24 22:36:56 WATCHDOG: [FAUPGRADE][auto_firmware_check7973)]user in use
Jun 24 22:37:26 WATCHDOG: [FAUPGRADE][auto_firmware_check7952)]do webs_update
Jun 24 22:37:26 WATCHDOG: [FAUPGRADE][auto_firmware_check7970)]retrieve firmware information
Jun 24 22:37:26 WATCHDOG: [FAUPGRADE][auto_firmware_check7973)]user in use
Jun 24 22:39:30 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link DOWN.
Jun 24 22:40:13 kernel: eth3 (Ext switch port: 2) (Logical Port: 10) (phyId: a) Link Up at 1000 mbps full duplex
Jun 24 22:40:33 wlceventd: wlceventd_proc_event(685): eth7: Auth C0:95:6D:6F:91:9A, status: Successful (0), rssi:0
Jun 24 22:40:33 wlceventd: wlceventd_proc_event(722): eth7: Assoc C0:95:6D:6F:91:9A, status: Successful (0), rssi:-52
Jun 24 22:40:38 wlceventd: wlceventd_proc_event(662): eth7: Disassoc C0:95:6D:6F:91:9A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 22:40:38 wlceventd: wlceventd_proc_event(662): eth7: Disassoc C0:95:6D:6F:91:9A, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 24 23:00:20 disk_monitor: Got SIGALRM...
Jun 25 03:42:01 ahs: [read_json]Update ahs JSON file.
Jun 25 03:42:01 get_ext_phy_id: 0/1/0/0
Jun 25 03:42:04 ahs: [self_healing]pattern_index-[9].
Jun 25 03:42:04 ahs: [self_healing]re_pattern-[get_ext_phy_id:].
Jun 25 03:42:04 ahs: [self_healing]take action-[store_state].
Jun 25 03:49:00 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind 14:C1:4E:58:A0:CD, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jun 25 03:49:21 wlceventd: wlceventd_proc_event(685): eth7: Auth 14:C1:4E:58:A0:CD, status: Successful (0), rssi:0
Jun 25 03:49:21 wlceventd: wlceventd_proc_event(722): eth7: Assoc 14:C1:4E:58:A0:CD, status: Successful (0), rssi:-36
Jun 25 03:53:26 WATCHDOG: [FAUPGRADE][auto_firmware_check7952)]do webs_update
Jun 25 03:53:36 WATCHDOG: [FAUPGRADE][auto_firmware_check7970)]retrieve firmware information
Jun 25 03:53:36 WATCHDOG: [FAUPGRADE][auto_firmware_check7985)]fimrware update check first time
Jun 25 03:53:36 WATCHDOG: [FAUPGRADE][auto_firmware_check8016)]no need to upgrade firmware

 

[Qbcd]

I have an AX86U with firmware version: Version 3.0.0.4.388_24339 on it (latest version on the support site). I don't have any AIMesh nodes, and before I changed routers, I wasn't having any random disconnects, so I had no reason to look at logs. Should I fire it up at some point as the main router to see if I get the error, or since I only use it as a stand alone router with no nodes, is mine exempt from the situation ?

PS, I have it configured with manual channel selection on both bands:
Channel 36 for 5Ghz with 160Mhz enabled, and DFS disabled.
Channel 6 for 2.4Ghz.

It seems to only affect people who have an AIMesh setup and want to use DFS channels. I seriously doubt it's been resolved. As I said, for me switching to the AX89X fixed it, but I'm about to buy a BE86U and I'll report back whether that has the issue.

 

[iFrogMac]

It seems to only affect people who have an AIMesh setup and want to use DFS channels. I seriously doubt it's been resolved. As I said, for me switching to the AX89X fixed it, but I'm about to buy a BE86U and I'll report back whether that has the issue.

I remember reading through the thread. I just wanted to follow up with providing feedback. Let u know how it goes after getting the BE86U.

 

[Squall Leonhart]

160Mhz enabled, and DFS disabled

mutually incompatible statement.

 

[Tech9]

Asuswrt allows this nonsense in settings, unfortunately.

 

[bbunge]

mutually incompatible statement.

Not really. Enabling DFS allows the primary channel to be in the DFS range. You can still use channels 36 thru 48 with 20/40/80/160 MHz enabled and get 160 MHz. If RADAR is detected the bandwidth will drop back to 80 MHz. With fixed 160 MHz the 5 GHz will shut down if RADAR is detected.

 

[Tech9]

Ah, okay... it's about the control channel only.

[Wireless Router] What is DFS (Dynamic Frequency Selection) and how does it work on ASUS router? | Official Support | ASUS Canada

 

[user114514]

Just use the backdoor to unlock UNII 4.

 

[Ripshod]

View attachment 66836
Just use the backdoor to unlock UNII 4.

Are you suggesting the member do something naughty?

 

[user114514]

Are you suggesting the member do something naughty?

This is legal in the US. FCC has approved unlicensed UNII4 use.

 

[Ripshod]

For the RT-AX86U specifically? Specs will need to be retested to comply with FCC regulations. Use a certified radio to transmit on uncertified bands and it's against FCC and Asus' terms, if not federal law.