AX86U: Does this indicate a hardware fault?

[John Fitzgerald]

Does this code indicate a hardware fault, Nand or Radio (in 2 section snips)?

The update from 388.8_4 to 388.9_2 did not go well. The logs show I am getting hammered with "China" blocks and the router is unusable, (thinking it might be a DOS attack)???
The router has become unusable even after flashing stock and rebuilding from scratch.

May  5 01:05:08 kernel: nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda
May  5 01:05:08 kernel: nand: Macronix MX30LF2G189C
May  5 01:05:08 kernel: nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
May  5 01:05:08 kernel: bcm63xx_nand ff801800.nand: Adjust timing_1 to 0x65324458 timing_2 to 0x80040e54
May  5 01:05:08 kernel: bcm63xx_nand ff801800.nand: detected 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, BCH-4
May  5 01:05:08 kernel: Bad block table found at page 131008, version 0x01
May  5 01:05:08 kernel: Bad block table found at page 130944, version 0x01
May  5 01:05:08 kernel: nand_read_bbt: bad block at 0x00000ab80000


May  5 01:05:12 acsd: acs_candidate_score_busy(1060): eth6: busy check failed for chanspec: 0x1907 (9u)
May  5 01:05:12 acsd: acs_candidate_score_intf(1112): eth6: intf check failed for chanspec: 0x1907 (9u)
May  5 01:05:12 acsd: acs_candidate_score_bgnoise(1577): eth6: bgnoise check failed for chanspec: 0x1907 (9u)
May  5 01:05:12 acsd: acs_candidate_score_txop(1835): eth6: txop check failed for chanspec: 0x1907 (9u)
May  5 01:05:12 acsd: acs_candidate_score_cns(1671): eth6: knoise check failed for chanspec: 0x1907 (9u)
May  5 01:05:12 acsd: acs_candidate_score_busy(1060): eth6: busy check failed for chanspec: 0x1808 (6l)
May  5 01:05:12 acsd: acs_candidate_score_intf(1112): eth6: intf check failed for chanspec: 0x1808 (6l)
May  5 01:05:12 acsd: acs_candidate_score_bgnoise(1577): eth6: bgnoise check failed for chanspec: 0x1808 (6l)
May  5 01:05:12 acsd: acs_candidate_score_txop(1835): eth6: txop check failed for chanspec: 0x1808 (6l)
May  5 01:05:12 acsd: acs_candidate_score_cns(1671): eth6: knoise check failed for chanspec: 0x1808 (6l)
May  5 01:05:12 acsd: acs_candidate_score_busy(1060): eth6: busy check failed for chanspec: 0x1908 (10u)
May  5 01:05:12 acsd: acs_candidate_score_intf(1112): eth6: intf check failed for chanspec: 0x1908 (10u)
May  5 01:05:12 acsd: acs_candidate_score_bgnoise(1577): eth6: bgnoise check failed for chanspec: 0x1908 (10u)
May  5 01:05:12 acsd: acs_candidate_score_txop(1835): eth6: txop check failed for chanspec: 0x1908 (10u)
May  5 01:05:12 acsd: acs_candidate_score_cns(1671): eth6: knoise check failed for chanspec: 0x1908 (10u)
May  5 01:05:12 acsd: acs_candidate_score_busy(1060): eth6: busy check failed for chanspec: 0x1809 (7l)
May  5 01:05:12 acsd: acs_candidate_score_intf(1112): eth6: intf check failed for chanspec: 0x1809 (7l)
May  5 01:05:12 acsd: acs_candidate_score_bgnoise(1577): eth6: bgnoise check failed for chanspec: 0x1809 (7l)
May  5 01:05:12 acsd: acs_candidate_score_txop(1835): eth6: txop check failed for chanspec: 0x1809 (7l)
May  5 01:05:12 acsd: acs_candidate_score_cns(1671): eth6: knoise check failed for chanspec: 0x1809 (7l)
May  5 01:05:12 acsd: acs_candidate_score_busy(1060): eth6: busy check failed for chanspec: 0x1909 (11u)
May  5 01:05:12 acsd: acs_candidate_score_intf(1112): eth6: intf check failed for chanspec: 0x1909 (11u)
May  5 01:05:12 acsd: acs_candidate_score_bgnoise(1577): eth6: bgnoise check failed for chanspec: 0x1909 (11u)
May  5 01:05:12 acsd: acs_candidate_score_txop(1835): eth6: txop check failed for chanspec: 0x1909 (11u)
May  5 01:05:12 acsd: acs_candidate_score_cns(1671): eth6: knoise check failed for chanspec: 0x1909 (11u)
May  5 01:05:12 acsd: eth6: selected channel spec: 0x1803 (1l)
May  5 01:05:12 acsd: eth6: Adjusted channel spec: 0x1803 (1l)
May  5 01:05:12 acsd: eth6: selected channel spec: 0x1803 (1l)
May  5 01:05:12 acsd: acs_set_chspec: 0x1803 (1l) for reason APCS_INIT

 

[dave14305]

No. Set a fixed WiFi channel and the acsd messages should stop.

Disable Skynet logging if the logs are overrun. Don’t watch.

 

[John Fitzgerald]

No. Set a fixed WiFi channel and the acsd messages should stop.

Disable Skynet logging if the logs are overrun. Don’t watch.

The 2.4 band WPA2 (20/40) was on auto and the 5G WPA3 was on Chan: 40 (20/40/80). Plus guest slot 2 on 2.4 same and 5G mixed WPA2/3. All separate SSID's and passwords.

Would the logs or excessive logging (refresh enabled) cause the router to prevent web pages from loading or going really slow to eventually failing? (like too much is causing a crash)
Memory runs around 442ish. Cores have been bouncing around a lot when it fails and sometimes just barely creeps a graph line.(not consistent)

I have rebuilt several times, including going back to stock this morning for a test. It eventually (shortly) fails the same way. Or after the WPS resets works then the next morning fails the same way around the 20 hour mark.

I'm thinking that this could be hardware related. The MT6000 is what I'm using just to connect now.

The update to the most recent firmware appears to have broken something: 2 WPS resets, newest stock, 388.8_4 and retry of 388.9_2 and all fail the same way.

Using Firefox which is up to date.

This has just been bizarre.

If you tell me to rebuild again, I'll do it. Tell me which firmware to be on.

Thanks!!!

 

[dave14305]

The MT6000 is what I'm using just to connect now.

Find the wan mac address of the MT6000 and use that as the cloned WAN MAC address on the Asus. It should then keep the same WAN IP as the MT6000 and you can see how the router behaves.

I’ve gone back to my MT6000 recently since my Asus couldn’t match the low wireless latency I get from my MT6000. I wouldn’t consider the MT6000 to be second-class in your situation. If it works better, use it!

 

[John Fitzgerald]

@dave14305
The flip back to stock seems to have sorted the issue out.
The original bad update flash hanged at the end where it said it was complete but it did not take me back to the login page.
The ASUS signed cert was updated after the factory reset, after the bad flash. (the only change I noticed)

After the stock update I rolled forward to the .8_4 for 20 hours and then the .9_2.
I also have recreated the storage drive now for the 3rd time with a reformat and reloading the scripts.

Thanks!