kernel: Hardware name: Broadcom-v8A (DT)

[StefanoN]

Hi
In the system log of my router ac86u, I see these messages appear several times:
Jan 4 22:14:39 kernel: Hardware name: Broadcom-v8A (DT)
Jan 4 22:14:39 kernel: task: ffffffc0157d0100 ti: ffffffc015108000 task.ti: ffffffc015108000
Jan 4 22:14:39 kernel: PC is at 0x10772c
Jan 4 22:14:39 kernel: LR is at 0xf6fb17d4
Jan 4 22:14:39 kernel: pc : [<000000000010772c>] lr : [<00000000f6fb17d4>] pstate: 60070010
Jan 4 22:14:39 kernel: sp : 00000000f6f7f308
Jan 4 22:14:39 kernel: x12: 00000000f70bcc40
Jan 4 22:14:39 kernel: x11: 0000000000000000 x10: 0000000000000000
Jan 4 22:14:39 kernel: x9 : 0000000000168828 x8 : 0000000000000000
Jan 4 22:14:39 kernel: x7 : 0000000000000001 x6 : 00000000f763ece0
Jan 4 22:14:39 kernel: x5 : 00000000f6f7f380 x4 : 00000000f6f7f33c
Jan 4 22:14:39 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Jan 4 22:14:39 kernel: x1 : 0000000000000020 x0 : 0000000000000000

In others post, I found solutions that said to disable the airprotection or qos functions. In my case they are already disabled.
Actualy I am using version 384.14_2, but the Messages appear with any versions of 384.14_xx and also with the alpha of 384.15 or with the latest original version of asus. For all the tested versions I have always made a factory default reset and I have never used the backups that I have made. Additional software used are amtm + skynet + yazfi, but the messages are already visible before these installations.
With the previous version 384.13 the messages did not appear.
Can anyone tell me how to solve?
Thanks.

 

[Butterfly Bones]

Hi
In the system log of my router ac86u, I see these messages appear several times:
Jan 4 22:14:39 kernel: Hardware name: Broadcom-v8A (DT)
Jan 4 22:14:39 kernel: task: ffffffc0157d0100 ti: ffffffc015108000 task.ti: ffffffc015108000
Jan 4 22:14:39 kernel: PC is at 0x10772c
Jan 4 22:14:39 kernel: LR is at 0xf6fb17d4
Jan 4 22:14:39 kernel: pc : [<000000000010772c>] lr : [<00000000f6fb17d4>] pstate: 60070010
Jan 4 22:14:39 kernel: sp : 00000000f6f7f308
Jan 4 22:14:39 kernel: x12: 00000000f70bcc40
Jan 4 22:14:39 kernel: x11: 0000000000000000 x10: 0000000000000000
Jan 4 22:14:39 kernel: x9 : 0000000000168828 x8 : 0000000000000000
Jan 4 22:14:39 kernel: x7 : 0000000000000001 x6 : 00000000f763ece0
Jan 4 22:14:39 kernel: x5 : 00000000f6f7f380 x4 : 00000000f6f7f33c
Jan 4 22:14:39 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Jan 4 22:14:39 kernel: x1 : 0000000000000020 x0 : 0000000000000000

In others post, I found solutions that said to disable the airprotection or qos functions. In my case they are already disabled.
Actualy I am using version 384.14_2, but the Messages appear with any versions of 384.14_xx and also with the alpha of 384.15 or with the latest original version of asus. For all the tested versions I have always made a factory default reset and I have never used the backups that I have made. Additional software used are amtm + skynet + yazfi, but the messages are already visible before these installations.
With the previous version 384.13 the messages did not appear.
Can anyone tell me how to solve?
Thanks.

Looks like this one.
https://www.snbforums.com/threads/kernel-errors.60260/#post-527516

 

[StefanoN]

Looks like this one.
https://www.snbforums.com/threads/kernel-errors.60260/#post-527516

Thanks for the reply. But is it a report that will be resolved? because It fill the log.

 

[Butterfly Bones]

Thanks for the reply. But is it a report that will be resolved? because It fill the log.

That is a question for Broadcom to resolve in their closed source software. RMerlin has stated that many times as this keeps getting posted, it is out of his control. The syslog will not fill up, it will be purged when necessary. There is a script you can run
https://www.snbforums.com/threads/script-to-remove-dcd-crashes-from-system-log.54734/#post-461933

or install the scribe (syslog-ng and logrotate installer) that will give you complete control of your syslog, eliminating all clutter.
https://www.snbforums.com/threads/scribe-syslog-ng-and-logrotate-installer.55853/

 

[StefanoN]

Hi
I tried the script, but my problem doesn't seem to be the one related to dcd.
it doesn't always appear, sometimes every hour, sometimes every few minutes

 

[Butterfly Bones]

Hi
I tried the script, but my problem doesn't seem to be the one related to dcd.
it doesn't always appear, sometimes every hour, sometimes every few minutes

Odd, I went by the RMerlin statement about the dcd crash from the other thread. I'm not someone who can understand script, maybe post in that thread and someone will help, since your crash seems to be different?

 

[ColinTaylor]

I tried the script, but my problem doesn't seem to be the one related to dcd.
it doesn't always appear, sometimes every hour, sometimes every few minutes

See this post later in the thread. It looks like the "dcd" line isn't always there so the sed command needs to be changed slightly.

https://www.snbforums.com/threads/s...shes-from-system-log.54734/page-4#post-525190

 

[StefanoN]

Hi
Yes, with the modifications it works.
Thanks for the tips.

 

[miazza]

I found that the issue "kernel: Hardware name: Broadcom-v8A (DT)" starts to appear after having installed entware and Diversion.

I tested the router RT86U from clean:

- fresh new install 384.19--> no issue detected in the log after one week
- fresh new USB drive wxt4 formatted empty --> no issue detected in the log after two days
- SWAP file added in USB drive --> no issue detected in the log after two days
- Installed Diversion with Entware (also YouTube AD block) : issue detected immediately

The raw command

/bin/sed -i '/kernel: pgd/,/kernel: x1 /d' /tmp/syslog.log

does not work for me.