Firmware: Signature Version: 2.376 2023/10/17 - Filling System Log with errors

[Rooke]

Router: RT-AC66U B1 (AC1750); Firmware Version: 3.0.0.4.51665 ;
On Tuesday, 2023/10/17, I noticed the entire System Log filled with the same repeating errors, all starting with error: "kernel: dcd/22609: potentially unexpected fatal signal 6." The only difference between the errors is the dcd number.

I checked the Administration menu, Firmware Upgrade tab, and found that the Firmware Signature Version had been updated to "2.376 2023/10/17 09:04" which was a couple of hours before I checked the logs.

After seeing that, I unplugged the Router for a few minutes and plugged it in again and let it boot up.

The errors went away for about an hour then came back. Subsequent (4) power off/on resulted in the same situation.

The errors do not seem to be affecting the router's performance, but the problem needs to be addressed by Asus. Attached is a snippet of the errors.

[RandyF]

Just installed the stable release of 386.12_2 last night and DCD errors are no longer occurring.

[Rooke]

@Adam_M- Thanks Adam, that did the trick for me too.  No more errors and also a slightly improved UI.
I'm sticking with the Merlin firmware from here on.

[jzchen]

Signature 2.380 released overnight (PST).  Hopefully this helps ASUSwrt users...

[kevinkar]

I did a manual check and updated the signature but the log started filling with the same info almost immediately.  So it did not help with stock FW.

[Rooke]

I also got the 2.380 night before last and it also gets the dcd errors, but I was lucky enough to see when it got installed in the log before the log wrapped. I sent the feedback from the router as soon as I saw the install errors:

Nov 16 02:23:12 kernel: Control: 10c53c7d Table: 98e6004a DAC: 00000015
[-----]
Nov 16 02:24:45 rc_service: rc 29081:notify_rc restart_wrs
Nov 16 02:25:12 BWDPI: fun bitmap = 83
Nov 16 02:25:13 A.QoS: qos_count=0, qos_check=0
Nov 16 02:25:13 A.QoS: qos rule is less than 22
Nov 16 02:25:13 A.QoS: restart A.QoS because set_qos_conf / set_qos_on / setup rule fail
Nov 16 02:25:14 A.QoS: qos_count=0, qos_check=1
[----]
Nov 16 02:25:16 kernel: dcd/29192: potentially unexpected fatal signal 6.
Nov 16 02:25:16 kernel: Pid: 29192, comm: dcd
Nov 16 02:25:16 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
Nov 16 02:25:16 kernel: PC is at 0x40140340
Nov 16 02:25:16 kernel: LR is at 0x401ad214
Nov 16 02:25:16 kernel: pc : [<40140340>] lr : [<401ad214>] psr: 60000010
Nov 16 02:25:16 kernel: sp : bdbfa630 ip : 401b7e5c fp : 4019d1a0
Nov 16 02:25:16 kernel: r10: 000c3188 r9 : 00000000 r8 : 00000000
Nov 16 02:25:16 kernel: r7 : 00000025 r6 : 00000006 r5 : 00007208 r4 : 401b8068
Nov 16 02:25:16 kernel: r3 : 401b8068 r2 : 00001406 r1 : 00000006 r0 : 00000000
Nov 16 02:25:16 kernel: Flags: nZCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Nov 16 02:25:16 kernel: Control: 10c53c7d Table: 9883404a DAC: 00000015

There seems to be something wrong with QoS that the signature firmware doesn't like.

I'm going to do a hard reset tomorrow and see if that helps at all, but I doubt it.   If it doesn't help, I'm going to install the latest Merlin firmware for the router.