Hi everyone,
starting from 2 days ago, my tuf-ax5400 log has been showing this type of messages:
Oct 27 10:42:00 acsd: acs_candidate_score_busy(1028): eth5: busy check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_intf(1080): eth5: intf check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_bgnoise(1500): eth5: bgnoise check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_txop(1758): eth5: txop check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_busy(1028): eth5: busy check failed for chanspec: 0x180b
Oct 27 10:42:00 acsd: acs_candidate_score_intf(1080): eth5: intf check failed for chanspec: 0x180b
Oct 27 10:42:00 acsd: acs_candidate_score_bgnoise(1500): eth5: bgnoise check failed for chanspec: 0x180b
Oct 27 10:42:00 acsd: acs_candidate_score_txop(1758): eth5: txop check failed for chanspec: 0x180b
It coincided with the need to reboot the router as it, for some reason, started hanging when checking the traffic analyzer tab on the firmware. Not sure if this is a coincidence or a sign of some kind of problem.
starting from 2 days ago, my tuf-ax5400 log has been showing this type of messages:
Oct 27 10:42:00 acsd: acs_candidate_score_busy(1028): eth5: busy check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_intf(1080): eth5: intf check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_bgnoise(1500): eth5: bgnoise check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_txop(1758): eth5: txop check failed for chanspec: 0x180a
Oct 27 10:42:00 acsd: acs_candidate_score_busy(1028): eth5: busy check failed for chanspec: 0x180b
Oct 27 10:42:00 acsd: acs_candidate_score_intf(1080): eth5: intf check failed for chanspec: 0x180b
Oct 27 10:42:00 acsd: acs_candidate_score_bgnoise(1500): eth5: bgnoise check failed for chanspec: 0x180b
Oct 27 10:42:00 acsd: acs_candidate_score_txop(1758): eth5: txop check failed for chanspec: 0x180b
It coincided with the need to reboot the router as it, for some reason, started hanging when checking the traffic analyzer tab on the firmware. Not sure if this is a coincidence or a sign of some kind of problem.