The showstopper 'I saw error 'xx' in my logs', now what?

[L&LD]

As the title may suggest, I'd like to start a consolidated list of showstopper errors as shown in the system log, if there is interest, of course. Be they security, performance or hardware issues.

Specifically after updating to a new/different firmware, what errors are the most serious (and we should be immediately concerned about) and what errors are simply a different firmware that may just simply be logging at a different log/verbosity level, (and that is less of immediate concern to us, if at all).

Including, if possible, the proper steps or method to deal with and either fix/eliminate them or possibly 'hide' them, as appropriate.

These would be errors that show up either with or without a full reset to factory defaults having been performed, or, errors that appear after enabling router features such as AiProtection, DDNS service, OpenVPN or even possibly from user scripts, (everything else except installation errors of those scripts).

Anyone that has anything to contribute is welcome! I will update the first three posts as necessary.

• This post (1) will be an overview of the intent here.
• The second post (2) will be the showstopper errors.
• The third post (3) will be errors that can be ignored.

My goal here is to have a one-stop shop where new and existing members can quickly track down their error and respond appropriately without needing to repeatedly create new threads or needing to necropost in long-forgotten ones. Alternately, new errors will be consolidated here rather than having to remember which post a certain (new) error was first posted in.

I will be collecting examples of these that I know about as I run across them and update the posts here.

I also welcome any suggestions to improve this thread in any way, if it is within my capabilities.

 

[L&LD]

Reserved Post (2)

 

[L&LD]

The errors listed here are not critical and are waiting for Asus to address them directly.
RMerlin cannot fix these errors as the code is closed source or otherwise beyond his control.

• infamous "dcd tainted" fault
• bcm963xx-pcie: failed to bring up core [2] link^M this one is posted here tentatively until further information can be traced down.

 

[jsbeddow]

How timely this thread is for me, as I just upgraded to a new RT-AC86U (from a trusty old 68U) and even though I followed your full M&M config guide with this new device, I am seeing a lot more errors in the system log than I am used to.

Specifically, this one (or is all of this related to the famous "dcd tainted" fault that can be safely ignored)

Apr 5 19:15:15 kernel: dcd[15286]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Apr 5 19:15:15 kernel: pgd = ffffffc017712000
Apr 5 19:15:15 kernel: [00000000] *pgd=00000000032b4003, *pud=00000000032b4003, *pmd=00000000025b4003, *pte=0000000000000000
Apr 5 19:15:15 kernel: CPU: 1 PID: 15286 Comm: dcd Tainted: P O 4.1.27 #2
Apr 5 19:15:15 kernel: Hardware name: Broadcom-v8A (DT)
Apr 5 19:15:15 kernel: task: ffffffc00683abc0 ti: ffffffc0125c0000 task.ti: ffffffc0125c0000
Apr 5 19:15:15 kernel: PC is at 0xf7363f44
Apr 5 19:15:15 kernel: LR is at 0x1dc74
Apr 5 19:15:15 kernel: pc : [<00000000f7363f44>] lr : [<000000000001dc74>] pstate: 600e0010
Apr 5 19:15:15 kernel: sp : 00000000ff8126f8
Apr 5 19:15:15 kernel: x12: 000000000009ff10
Apr 5 19:15:15 kernel: x11: 00000000f65ff024 x10: 00000000000a02b4
Apr 5 19:15:16 kernel: x9 : 00000000f65ff97c x8 : 00000000000a076c
Apr 5 19:15:16 kernel: x7 : 00000000f65ff9b4 x6 : 00000000000a0766
Apr 5 19:15:16 kernel: x5 : 0000000000000000 x4 : 00000000f65ff960
Apr 5 19:15:16 kernel: x3 : 0000000000000000 x2 : 00000000ff8126d4
Apr 5 19:15:16 kernel: x1 : 000000000007c674 x0 : 0000000000000000

Other than that, so far I am pretty impressed with the 86U; noticeably snappier page load times on a wired connection, and a modest boost in range (RSSI levels are better throughout the house). Plus, yes, the FreshJR Adaptive QOS does seem to work at near gigabit speed, although hard to manually set max throughput numbers as they seem to vary significantly by time of day, which speedtest I use, etc...

 

[L&LD]

How timely this thread is for me, as I just upgraded to a new RT-AC86U (from a trusty old 68U) and even though I followed your full M&M config guide with this new device, I am seeing a lot more errors in the system log than I am used to.

Specifically, this one (or is all of this related to the famous "dcd tainted" fault that can be safely ignored)

Apr 5 19:15:15 kernel: dcd[15286]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Apr 5 19:15:15 kernel: pgd = ffffffc017712000
Apr 5 19:15:15 kernel: [00000000] *pgd=00000000032b4003, *pud=00000000032b4003, *pmd=00000000025b4003, *pte=0000000000000000
Apr 5 19:15:15 kernel: CPU: 1 PID: 15286 Comm: dcd Tainted: P O 4.1.27 #2
Apr 5 19:15:15 kernel: Hardware name: Broadcom-v8A (DT)
Apr 5 19:15:15 kernel: task: ffffffc00683abc0 ti: ffffffc0125c0000 task.ti: ffffffc0125c0000
Apr 5 19:15:15 kernel: PC is at 0xf7363f44
Apr 5 19:15:15 kernel: LR is at 0x1dc74
Apr 5 19:15:15 kernel: pc : [<00000000f7363f44>] lr : [<000000000001dc74>] pstate: 600e0010
Apr 5 19:15:15 kernel: sp : 00000000ff8126f8
Apr 5 19:15:15 kernel: x12: 000000000009ff10
Apr 5 19:15:15 kernel: x11: 00000000f65ff024 x10: 00000000000a02b4
Apr 5 19:15:16 kernel: x9 : 00000000f65ff97c x8 : 00000000000a076c
Apr 5 19:15:16 kernel: x7 : 00000000f65ff9b4 x6 : 00000000000a0766
Apr 5 19:15:16 kernel: x5 : 0000000000000000 x4 : 00000000f65ff960
Apr 5 19:15:16 kernel: x3 : 0000000000000000 x2 : 00000000ff8126d4
Apr 5 19:15:16 kernel: x1 : 000000000007c674 x0 : 0000000000000000

Other than that, so far I am pretty impressed with the 86U; noticeably snappier page load times on a wired connection, and a modest boost in range (RSSI levels are better throughout the house). Plus, yes, the FreshJR Adaptive QOS does seem to work at near gigabit speed, although hard to manually set max throughput numbers as they seem to vary significantly by time of day, which speedtest I use, etc...

I think this falls into the 'can be ignored' camp.

https://www.snbforums.com/threads/k...-level-3-translation-fault.49656/#post-477349

 

[martinr]

As the title may suggest, I'd like to start a consolidated list of showstopper errors as shown in the system log, if there is interest, of course. Be they security, performance or hardware issues.

Specifically after updating to a new/different firmware, what errors are the most serious (and we should be immediately concerned about) and what errors are simply a different firmware that may just simply be logging at a different log/verbosity level, (and that is less of immediate concern to us, if at all).

Including, if possible, the proper steps or method to deal with and either fix/eliminate them or possibly 'hide' them, as appropriate.

These would be errors that show up either with or without a full reset to factory defaults having been performed, or, errors that appear after enabling router features such as AiProtection, DDNS service, OpenVPN or even possibly from user scripts, (everything else except installation errors of those scripts).

Anyone that has anything to contribute is welcome! I will update the first three posts as necessary.

• This post (1) will be an overview of the intent here.
• The second post (2) will be the showstopper errors.
• The third post (3) will be errors that can be ignored.

My goal here is to have a one-stop shop where new and existing members can quickly track down their error and respond appropriately without needing to repeatedly create new threads or needing to necropost in long-forgotten ones. Alternately, new errors will be consolidated here rather than having to remember which post a certain (new) error was first posted in.

I will be collecting examples of these that I know about as I run across them and update the posts here.

I also welcome any suggestions to improve this thread in any way, if it is within my capabilities.

What an inspired idea.

Only yesterday I was searching on Goigle to try to make sense of logging levels and notification levels - and gave up unable to see the wood for all the trees.

On the syslog page we have a setting for “Default message log level” and below it, “Log only messages more urgent than”. This second setting is self explanatory. But I don’t understand the first one, which I presume corresponds to the notification level on other routers. There are explicit messages/alerts sent to the administrator?

I think this would be a great place for an explanation of these settings and the recommendations (if not the default ones) for what each should be set to under normal conditions and also when one might want to temporarily alter them.

I looked through my syslog to see if I could find any errors to report, but, as it’s an RT-AC68U, it’s clean as a whistle.

Many thanks, L&LD

 

[faria]

bcm963xx-pcie: failed to bring up core [2] link^M

The above shows after your reboot the router manually due to a router g shutdown when asked to reboot via gui.
Random event , and so far unknown cause.
Only rt-ac86u.

 

[Martineau]

My goal here is to have a one-stop shop where new and existing members can quickly track down their error and respond appropriately without needing to repeatedly create new threads or needing to necropost in long-forgotten ones. Alternately, new errors will be consolidated here rather than having to remember which post a certain (new) error was first posted in.

Admirable project, but let's be frank, few bother to search , although possibly consolidating the info in the Wiki could also be an option - that is if anyone uses it.

However, if the messages can be categorised by severity etc., perhaps a real-time solution is in the wings ? ...I'm sure given the motivation, @cmkelley could then include a scribe ruleset to Enhance syslog-ng messages

"dcd",bug-track,"Awaiting ASUS firmware fix"
"pgd",bug-track,"Already fixed by ASUS in next release"
"kernel: All bugs added by David S. Miller, ",bug-track,"NO he didn't - its a JOKE!!"


Large image

 

[Jack Yaz]

Admirable project, but let's be frank, few bother to search , although possibly consolidating the info in the Wiki could also be an option - that is if anyone uses it.

Even fewer fail to acknowledge the stickied posts in all caps (e.g. https://www.snbforums.com/threads/the-tm-ac1900-is-not-supported.48056/) so I fear this is a losing battle.

I'm all for consolidation of information, however!

 

[GuruGuy]

As the title may suggest, I'd like to start a consolidated list of showstopper errors as shown in the system log, if there is interest, of course. Be they security, performance or hardware issues.

Specifically after updating to a new/different firmware, what errors are the most serious (and we should be immediately concerned about) and what errors are simply a different firmware that may just simply be logging at a different log/verbosity level, (and that is less of immediate concern to us, if at all).

Including, if possible, the proper steps or method to deal with and either fix/eliminate them or possibly 'hide' them, as appropriate.

These would be errors that show up either with or without a full reset to factory defaults having been performed, or, errors that appear after enabling router features such as AiProtection, DDNS service, OpenVPN or even possibly from user scripts, (everything else except installation errors of those scripts).

Anyone that has anything to contribute is welcome! I will update the first three posts as necessary.

• This post (1) will be an overview of the intent here.
• The second post (2) will be the showstopper errors.
• The third post (3) will be errors that can be ignored.

My goal here is to have a one-stop shop where new and existing members can quickly track down their error and respond appropriately without needing to repeatedly create new threads or needing to necropost in long-forgotten ones. Alternately, new errors will be consolidated here rather than having to remember which post a certain (new) error was first posted in.

I will be collecting examples of these that I know about as I run across them and update the posts here.

I also welcome any suggestions to improve this thread in any way, if it is within my capabilities.

I would change Post #3 from "The third post (3) will be errors that can be ignored." to "Asus Known Issue, waiting on firmware fix."
The DCD tainted is one of those, waiting on a fix.

Also, possibly pin to the top of the main Asus forum, not necessarily within the merlin forum

 

[L&LD]

bcm963xx-pcie: failed to bring up core [2] link^M

The above shows after your reboot the router manually due to a router g shutdown when asked to reboot via gui.
Random event , and so far unknown cause.
Only rt-ac86u.

That looks like a hardware error to me (motherboard, possibly)?

Thank you and hope we get some feedback here for you!

 

[L&LD]

Admirable project, but let's be frank, few bother to search , although possibly consolidating the info in the Wiki could also be an option - that is if anyone uses it.

However, if the messages can be categorised by severity etc., perhaps a real-time solution is in the wings ? ...I'm sure given the motivation, @cmkelley could then include a scribe ruleset to Enhance syslog-ng messages

"dcd",bug-track,"Awaiting ASUS firmware fix"
"pgd",bug-track,"Already fixed by ASUS in next release"
"kernel: All bugs added by David S. Miller, ",bug-track,"NO he didn't - its a JOKE!!"


Large image

View attachment 16911

Those are great comments and excellent ideas (for scribe)! Since cmkelley doesn't have enough to do already.

 

[L&LD]

Even fewer fail to acknowledge the stickied posts in all caps (e.g. https://www.snbforums.com/threads/the-tm-ac1900-is-not-supported.48056/) so I fear this is a losing battle.

I'm all for consolidation of information, however!

I'll try my best to keep this post updated. Maybe with enough info included, it will become useful in the future.

 

[L&LD]

I would change Post #3 from "The third post (3) will be errors that can be ignored." to "Asus Known Issue, waiting on firmware fix."
The DCD tainted is one of those, waiting on a fix.

Also, possibly pin to the top of the main Asus forum, not necessarily within the merlin forum

I really like that suggestion to change the third post. I will do it!

If enough information is included, it may be time then to pin it then, as Tim sees fit, of course.

Thanks, GuruGuy!

 

[L&LD]

What an inspired idea.

Only yesterday I was searching on Goigle to try to make sense of logging levels and notification levels - and gave up unable to see the wood for all the trees.

On the syslog page we have a setting for “Default message log level” and below it, “Log only messages more urgent than”. This second setting is self explanatory. But I don’t understand the first one, which I presume corresponds to the notification level on other routers. There are explicit messages/alerts sent to the administrator?

I think this would be a great place for an explanation of these settings and the recommendations (if not the default ones) for what each should be set to under normal conditions and also when one might want to temporarily alter them.

I looked through my syslog to see if I could find any errors to report, but, as it’s an RT-AC68U, it’s clean as a whistle.

Many thanks, L&LD

Glad to hear that your 'AC68U is so shiny and 'new'!

The suggestion to have an explanation of the different log levels is excellent too!

I hope we have some input in this area. Would make a great addition to the first post.

 

[faria]

That looks like a hardware error to me (motherboard, possibly)?

Thank you and hope we get some feedback here for you!

Hell no if thats the case then i would like to find out , but info about that log is scarce , found one other user here witch had the same entry in the log.
Perhaps people with rt-ac86 could search their logs for that entry so we could determinate if is a common entry or have i a faulty unit.

 

[cmkelley]

Hell no if thats the case then i would like to find out , but info about that log is scarce , found one other user here witch had the same entry in the log.
Perhaps people with rt-ac86 could search their logs for that entry so we could determinate if is a common entry or have i a faulty unit.

"grep core messages" tells me I it every on boot-up, before the system clock is set.

 

[faria]

"grep core messages" tells me I it every on boot-up, before the system clock is set.

Sorry man, my native language ain't English
Are you saying that you also found the entry in your logs at every boot before the system clock is set?

 

[Martineau]

Sorry man, my native language ain't English
Are you saying that you also found the entry in your logs at every boot before the system clock is set?

Same on my RT-AC86U

May  5 06:05:05 kernel:   bcm963xx-pcie: failed to bring up core [2] link^M

 

[faria]

Same on my RT-AC86U

May  5 06:05:05 kernel:   bcm963xx-pcie: failed to bring up core [2] link^M

thanks @Martineau and @cmkelley for taking the time to check, much appreciated .
I feel much at ease now