I get this error even after a reset. can anyone help?

[Lars Hjortshøj Andersen]

Sorry I am quite a noob. and i need help to understand this
I have this error repeating constantly in my log

May 5 07:05:05 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
May 5 07:05:05 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
May 5 07:05:05 kernel: brcmboard registered
May 5 07:05:05 kernel: broadcomThermalDrv brcm-therm: init (CPU count 2 2 2 2)
May 5 07:05:05 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
May 5 07:05:05 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Feb 8 08:52:26 kernel: pgd = ffffffc00b79c000
Feb 8 08:52:26 kernel: [00000000] *pgd=000000001484d003, *pud=000000001484d003, *pmd=0000000012cbb003, *pte=0000000000000000
Feb 8 08:57:22 kernel: pgd = ffffffc014938000
Feb 8 08:57:22 kernel: [00000000] *pgd=0000000012f62003, *pud=0000000012f62003, *pmd=0000000012cbe003, *pte=0000000000000000
Feb 8 09:13:44 kernel: pgd = ffffffc014a3b000
Feb 8 09:13:44 kernel: [00000000] *pgd=0000000012c90003, *pud=0000000012c90003, *pmd=0000000012e02003, *pte=0000000000000000
Feb 8 09:22:53 kernel: pgd = ffffffc0157c7000
Feb 8 09:22:53 kernel: [00000000] *pgd=0000000019332003, *pud=0000000019332003, *pmd=0000000012dc7003, *pte=0000000000000000
Feb 8 09:43:11 kernel: pgd = ffffffc0150a7000
Feb 8 09:43:11 kernel: [00000000] *pgd=000000000b78f003, *pud=000000000b78f003, *pmd=0000000012d37003, *pte=0000000000000000
Feb 8 09:50:04 kernel: pgd = ffffffc012ecb000
Feb 8 09:50:04 kernel: [00000000] *pgd=0000000011c7f003, *pud=0000000011c7f003, *pmd=0000000012d41003, *pte=0000000000000000
Feb 8 10:04:21 kernel: pgd = ffffffc017209000
Feb 8 10:04:21 kernel: [00000000] *pgd=0000000012de8003, *pud=0000000012de8003, *pmd=0000000012e02003, *pte=0000000000000000
Feb 8 10:19:19 kernel: pgd = ffffffc012e16000
Feb 8 10:19:19 kernel: [00000000] *pgd=0000000011c79003, *pud=0000000011c79003, *pmd=0000000014a04003, *pte=0000000000000000
Feb 8 10:45:04 kernel: pgd = ffffffc0157e4000
Feb 8 10:45:04 kernel: [00000000] *pgd=0000000012de7003, *pud=0000000012de7003, *pmd=0000000014a27003, *pte=0000000000000000
Feb 8 11:14:22 kernel: pgd = ffffffc012de7000
Feb 8 11:14:22 kernel: [00000000] *pgd=000000001508f003, *pud=000000001508f003, *pmd=0000000011d4a003, *pte=0000000000000000


Maybe this is related. My configuration is set to restart the RT-AC86U every morning at 04:30.
But after 04:30 the router is on, but wireless is off and no internet connection on cable.
I can access the router GUI and restart the router from there

 

[Treadler]

Welcome to the forum Lars.

I am no expert, but my experience has been that scheduled reboot is broken.
Not necessarily every time, but often the reboot is incomplete, or fails altogether, sometimes just turning the router off.
Maybe try not scheduling a reboot? The current firmware appears to be very stable in my use, & seldom requires reboot.

Disclaimer: I haven’t tested scheduled reboot for some months now, so things may have changed! ;-)

 

[Zonkd]

Welcome to the forum Lars.

I am no expert, but my experience has been that scheduled reboot is broken.
Not necessarily every time, but often the reboot is incomplete, or fails altogether, sometimes just turning the router off.
Maybe try not scheduling a reboot? The current firmware appears to be very stable in my use, & seldom requires reboot.

Disclaimer: I haven’t tested scheduled reboot for some months now, so things may have changed! ;-)

It’s not just the scheduler. My AC86U regularly fails to soft reboot. I’ll click the reboot button in web GUI, the lights go out and the router is dead. I’m forced to use power button on router. Moral of the story is never rely on reboot to work.

 

[Treadler]

It’s not just the scheduler. My AC86U regularly fails to soft reboot. I’ll click the reboot button in web GUI, the lights go out and the router is dead. I’m forced to use power button on router. Moral of the story is never rely on reboot to work.

Yes, a known issue.
Later firmwares appear to have lessened, but not fixed the issue.
(In my experience anyhow......)