What's new

Both CPUs pegged at 100%

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

azdeltawye

Occasional Visitor
I recently encountered a strange problem on my RT-AC86U. I have been running Merlin 384.12 since it was released a couple weeks ago without issue. On Monday I installed the 'standard' suite of scripts (AMTM, Diversion, Skynet, YazFi). Everything appeared to be working fine except when I logged into the UI on Tues to see both CPUs at 100%! See error logs below.

Code:
Jul  9 20:29:52 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:29:54 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:29:54 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:29:55 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:29:55 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:29:56 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:29:56 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:29:59 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:29:59 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:00 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:00 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:01 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:01 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:03 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:04 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:09 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:09 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:10 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:10 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:13 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:13 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:15 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:15 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:18 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:19 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:20 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:20 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:22 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:22 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:24 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:24 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:25 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:25 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:33 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:33 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:33 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:30:34 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul  9 20:30:34 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Jul  9 20:30:34 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
Jul  9 20:30:35 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Jul  9 20:30:35 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
Jul  9 20:31:42 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Jul  9 20:31:42 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
Jul  9 20:31:45 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:31:45 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
Jul  9 20:31:46 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Jul  9 20:31:47 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
Jul  9 20:31:48 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
Jul  9 20:31:48 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0
Jul  9 20:32:10 wsdd2[2385]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jul  9 20:32:10 wsdd2[2385]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jul  9 20:32:10 ovpn-server2[6880]: event_wait : Interrupted system call (code=4)
Jul  9 20:32:11 wsdd2[2385]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Jul  9 20:32:11 wsdd2[2385]: Terminated received.
Jul  9 20:32:14 Mastiff: Got SIGTERM
Jul  9 20:32:14 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul  9 20:32:14 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
Jul  9 20:32:17 pixelserv-tls[1721]: 91560 uts, 1 log, 0 kcc, 3 kmx, 1.15 kvg, 13 krq, 1598 req, 636 avg, 984 rmx, 4 tav, 29 tmx, 0 slh, 153 slm, 0 sle, 236 slc, 1178 slu, 0 v13, 212 v12, 24 v10, 0 zrt, 506 uca, 0 ucb, 0 uce, 636 ush, 53 sct, 1360 sch, 53 scm, 0 scp, 58 ssh, 0 ssm, 0 ssp, 3 nfe, 0 gif, 3 ico, 5 txt, 0 jpg, 0 png, 0 swf, 0 ufe, 0 opt, 13 pst, 0 hed, 0 rdr, 0 nou, 0 pth, 0 204, 0 bad, 237 cls, 0 cly, 0 clt, 0 err
I rebooted the router and it seemed to clear things up for the momment however I am still seeing the following error log every 15 minutes or so:
Code:
Jul 10 06:13:06 kernel: pgd = ffffffc0024d0000
Jul 10 06:13:06 kernel: [00000000] *pgd=0000000003d7f003, *pud=0000000003d7f003, *pmd=0000000001999003, *pte=0000000000000000
Jul 10 06:32:55 kernel: pgd = ffffffc0110f9000
Jul 10 06:32:55 kernel: [00000000] *pgd=0000000015771003, *pud=0000000015771003, *pmd=000000001138c003, *pte=0000000000000000
Jul 10 06:39:53 kernel: pgd = ffffffc009221000
Jul 10 06:39:53 kernel: [00000000] *pgd=0000000008fd3003, *pud=0000000008fd3003, *pmd=0000000008cba003, *pte=0000000000000000
Jul 10 06:57:08 kernel: pgd = ffffffc002ea9000
Jul 10 06:57:08 kernel: [00000000] *pgd=0000000003727003, *pud=0000000003727003, *pmd=0000000004357003, *pte=0000000000000000
Jul 10 07:07:56 kernel: pgd = ffffffc002ea9000
Jul 10 07:07:57 kernel: [00000000] *pgd=0000000010e13003, *pud=0000000010e13003, *pmd=0000000004a04003, *pte=0000000000000000
Jul 10 07:27:19 ovpn-server1[6522]: client/216.84.89.126:26704 Connection reset, restarting [0]
Jul 10 07:38:31 kernel: pgd = ffffffc001e0c000
Jul 10 07:38:31 kernel: [00000000] *pgd=0000000015320003, *pud=0000000015320003, *pmd=000000000146b003, *pte=0000000000000000
Jul 10 07:40:19 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul 10 07:40:19 kernel: bcm63xx_nand ff801800.nand: intfc status f00000e0
Jul 10 08:09:27 kernel: pgd = ffffffc00be8f000
Jul 10 08:09:27 kernel: [00000000] *pgd=0000000001e0c003, *pud=0000000001e0c003, *pmd=0000000001932003, *pte=0000000000000000
Jul 10 08:27:46 ovpn-server1[6522]: client/216.84.89.126:23486 Connection reset, restarting [0]
Jul 10 08:31:11 kernel: pgd = ffffffc00400b000
Jul 10 08:31:11 kernel: [00000000] *pgd=0000000008d68003, *pud=0000000008d68003, *pmd=0000000001cab003, *pte=0000000000000000
Jul 10 08:43:01 kernel: pgd = ffffffc011271000
Jul 10 08:43:01 kernel: [00000000] *pgd=0000000003eee003, *pud=0000000003eee003, *pmd=0000000011381003, *pte=0000000000000000
Jul 10 08:57:48 kernel: pgd = ffffffc0016af000
Jul 10 08:57:48 kernel: [00000000] *pgd=000000000499f003, *pud=000000000499f003, *pmd=000000001015f003, *pte=0000000000000000
Jul 10 09:00:01 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Jul 10 09:00:01 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
Jul 10 09:00:51 kernel: pgd = ffffffc003e15000
Jul 10 09:00:51 kernel: [00000000] *pgd=0000000001f2d003, *pud=0000000001f2d003, *pmd=0000000001cf8003, *pte=0000000000000000
Jul 10 09:28:41 kernel: pgd = ffffffc0042c1000
Jul 10 09:28:41 kernel: [00000000] *pgd=00000000024b8003, *pud=00000000024b8003, *pmd=0000000004bb7003, *pte=0000000000000000
Jul 10 09:34:44 ovpn-server1[6522]: client/216.84.89.126:34862 Connection reset, restarting [0]
Jul 10 09:48:53 kernel: pgd = ffffffc00bcbf000
Jul 10 09:48:53 kernel: [00000000] *pgd=0000000010f15003, *pud=0000000010f15003, *pmd=000000001138b003, *pte=0000000000000000
Jul 10 10:00:59 kernel: pgd = ffffffc001c92000
Jul 10 10:00:59 kernel: [00000000] *pgd=0000000003ed1003, *pud=0000000003ed1003, *pmd=00000000110ff003, *pte=0000000000000000
Any ideas what could be wrong?
Thx
 
I have the same issue with CPU, but different errors.
I'm trying to run the new "alpha" test.
But still having the same issue.
It spikes to 100%, here and there.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top