Strange events in RT-AC86U system log

[Neil Horowitz]

For the last two months or so, I have been seeing these events filling the system log in my RT-AC86U router:

Mar 31 13:08:11 kernel: pgd = ffffffc003360000
Mar 31 13:08:11 kernel: [00000000] *pgd=000000000497d003, *pud=000000000497d003, *pmd=0000000003363003, *pte=0000000000000000
Mar 31 13:09:51 kernel: pgd = ffffffc012d0e000
Mar 31 13:09:52 kernel: [00000000] *pgd=0000000015222003, *pud=0000000015222003, *pmd=0000000003387003, *pte=0000000000000000
Mar 31 13:31:46 kernel: pgd = ffffffc011237000
Mar 31 13:31:46 kernel: [00000000] *pgd=00000000152a5003, *pud=00000000152a5003, *pmd=000000001501f003, *pte=0000000000000000
Mar 31 13:41:10 kernel: pgd = ffffffc01525a000
Mar 31 13:41:10 kernel: [00000000] *pgd=000000001501f003, *pud=000000001501f003, *pmd=0000000003360003, *pte=0000000000000000
Mar 31 13:47:31 kernel: pgd = ffffffc01e0bf000
Mar 31 13:47:31 kernel: [00000000] *pgd=0000000011fac003, *pud=0000000011fac003, *pmd=00000000033fa003, *pte=0000000000000000
Mar 31 14:16:39 kernel: pgd = ffffffc011282000
Mar 31 14:16:39 kernel: [00000000] *pgd=000000001481d003, *pud=000000001481d003, *pmd=0000000015060003, *pte=0000000000000000

I had hoped that it was being caused by some quirk in the 384.9 firmware, but when I upgraded my router to 384.10, the router needed a cold boot before it would return to running in a stable fashion, but with these strange events in the system log still occurring. I have the "default message logging level" set to Error, and "log only messages more urgent than" set to Warning. This may be a coincidence, but prior to the 384.9 firmware, I had no problems whatsoever with this router or the system log.
Does anyone have any idea what may be causing these logged events and how to stop them from occurring?

 

[L&LD]

For the last two months or so, I have been seeing these events filling the system log in my RT-AC86U router:

Mar 31 13:08:11 kernel: pgd = ffffffc003360000
Mar 31 13:08:11 kernel: [00000000] *pgd=000000000497d003, *pud=000000000497d003, *pmd=0000000003363003, *pte=0000000000000000
Mar 31 13:09:51 kernel: pgd = ffffffc012d0e000
Mar 31 13:09:52 kernel: [00000000] *pgd=0000000015222003, *pud=0000000015222003, *pmd=0000000003387003, *pte=0000000000000000
Mar 31 13:31:46 kernel: pgd = ffffffc011237000
Mar 31 13:31:46 kernel: [00000000] *pgd=00000000152a5003, *pud=00000000152a5003, *pmd=000000001501f003, *pte=0000000000000000
Mar 31 13:41:10 kernel: pgd = ffffffc01525a000
Mar 31 13:41:10 kernel: [00000000] *pgd=000000001501f003, *pud=000000001501f003, *pmd=0000000003360003, *pte=0000000000000000
Mar 31 13:47:31 kernel: pgd = ffffffc01e0bf000
Mar 31 13:47:31 kernel: [00000000] *pgd=0000000011fac003, *pud=0000000011fac003, *pmd=00000000033fa003, *pte=0000000000000000
Mar 31 14:16:39 kernel: pgd = ffffffc011282000
Mar 31 14:16:39 kernel: [00000000] *pgd=000000001481d003, *pud=000000001481d003, *pmd=0000000015060003, *pte=0000000000000000

I had hoped that it was being caused by some quirk in the 384.9 firmware, but when I upgraded my router to 384.10, the router needed a cold boot before it would return to running in a stable fashion, but with these strange events in the system log still occurring. I have the "default message logging level" set to Error, and "log only messages more urgent than" set to Warning. This may be a coincidence, but prior to the 384.9 firmware, I had no problems whatsoever with this router or the system log.
Does anyone have any idea what may be causing these logged events and how to stop them from occurring?

A more direct solution may be available for what you're seeing. My suggestion is to do a full reset to factory defaults and then minimally and manually configure the router to secure it and connect to your ISP.

Please see my signature below for links and further details.

 

[ColinTaylor]

https://www.snbforums.com/threads/rt-ac86u-possible-kernel-crash.54221/#post-456324

 

[Neil Horowitz]

Gentlemen, thanks for the quick replies. The cause of my problem was my use of the Trend Micro AiProtection provided in the firmware. Once I disabled this feature, I was able to lower the logging parameters "default message log level" to warning and "log only messages more urgent than" to notice with no resulting events logged over several hours. This is how this router was performing prior to Merlin firmware 384.9 I believe. The question is of course is this an Asus or a Merlin problem and is there an awareness of this problem and is it being addressed.