What's new

Random kernel reboot message popped up overnight

  • 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!

ZenitH-AT

Occasional Visitor
The router restarted and there was this following block of messages:
Code:
May  5 07:05:02 kernel: _ Reboot message ... _______________________________________________________
May  5 07:05:02 kernel: <1>Unable to handle kernel paging request at vir�U� address 400d003b
May  5 07:05:02 kernel: <1>pgd = c0004000
May  5 07:05:02 kernel: <1>[400d003b] *pgd=00000000
May  5 07:05:02 kernel: <0>Internal error: Oops: 17 [#1] PREEMPT SMP
May  5 07:05:02 kernel: <0>last sysfs file: /sys/class/net/vlan1/brport/porc9000     26092
May  5 07:05:02 kernel: <4>module:  tdts_udtdts     bf770000     416313
May  5 07:05:02 kernel: <4>modulenf_conntrack_h323     bf74b000     3385000     3202
May  5 07:05:02 kernel: <4>module:  nf_conntrack_rtsp     bf73f000     4067
May  5 07:05:02 kernel: <4>module:  nf_nat_ftp     bf739000     1144
May  5 07:05:02 kernel: e_mangle     bf72c000     934
May  5 07:05:02 kernel: <4>modul00     52776
May  5 07:05:02 kernel: <4>module:  ext4     bf5fe000     221674
May  5 07:05:02 kernel: <4>module:  jbd2     b mbcache     bf5ab000     4599
May  5 07:05:02 kernel: <4>modu21983
May  5 07:05:02 kernel: <4>module:  scsi_wait_scan
May  5 07:05:02 kernel: <4>module:  ebt_ip     bf50b000     1bf505000     873
May  5 07:05:02 kernel: <4>module:  ebtablle:  ebtables     bf4f6000     15643
May  5 07:05:02 kernel: <494
May  5 07:05:02 kernel: <4>module:  ip6table_filter     ehci_hcd     bf4d1000     32382
May  5 07:05:02 kernel: <4>mo     bf473000     887
May  5 07:05:02 kernel: <4>module:  nf_c0     15225
May  5 07:05:02 kernel: <4>Modules linked in: t nf_conntrack_ftp ip6table_mangl mii ebt_ip ebtable_broute ebtable_filter ebtables ip6t_LOG ip6t c03c3b18  ip : 0000e7cc  fp : ctrol: 10c53c7d  Table: 9df7404a 270)
May  5 07:05:02 kernel: <0>Stack: (0xc03c3b18 to 0xe4 bf7b23e4
May  5 07:05:02 kernel: <0>3b40: bf7b23e4 00000000 00000000 00000000 00000003b60: 00000000 00000000 0002e7cc0000 00061cbf
May  5 07:05:02 kernel: <0>3b80: 6f01a8c0 82f8 c78bc130 c03c3c20 c0386658 00
May  5 07:05:02 kernel: <0>3c20: c03e1844 d8ce8388 000000
May  5 07:05:02 kernel: <0>3c60: c023d608 c027602c cf9e5100 ca0fb240 c03e1478 c6d7f7cd04 c023d608 cf80a000
May  5 07:05:02 kernel: <0>3cc0:0000000 cf9ed800 c03c3d14
May  5 07:05:02 kernel: <0>3d03c2000 c0420588 c03e167c 0000000�^Ba80 cf80a000
May  5 07:05:02 kernel: <0>3d60: c041fed4 c80 c037ec4c cf80a000 00000001
May  5 07:05:02 kernel: <0a80 0000e2bf cfbcf800 cfbcf800 c03c2000 00000000
May  5 07:05:02 kernel: <0>3de0: 00000000 c037b9d8 00000000 c037b900 800
May  5 07:05:02 kernel: <0>3e00: 0000c020 c03c3dfc cfbcf3d7a20 c01f84ec 00000000 1553090 00001553 c03c2000
May  5 07:05:02 kernel: <0>3e60: cf4 00200200 c041ff98 00100100 c03c0413f20 00000000 c0387b28
May  5 07:05:02 kernel: <0>3f 00000002 00000001 c03872a8 00000002 cf820600
May  5 07:05:02 kernel: <0>3f80: c03c3fc0 b80 c03ceb78 000263d0 413fc090
May  5 07:05:02 kernel: <00 c03c3fc0 c003ebe4 c003ebe8 60000013 ffffffff
May  5 07:05:02 kernel: <0>3fc0: c003ebc4 c003ed88 c041788c c03e6000 c003c7d c03e61c4 c0028024 00008084 00000000 00000000
May  5 07:05:02 kernel: <4>[<c0273228>3fc/0x690)
May  5 07:05:02 kernel: <4>[<c0273228>] (nf_n[<c02771d8>] (masquerade_tg+0xc8de_tg+0xc8/0xe4) from [<c0386658n+0xfc/0x130)
May  5 07:05:02 kernel: <4>[<c02761c8>] (nf_nat_fn+0xfc/0x130) from [<c037>[<c037cd04>] (nf_iterate+0x94/00x84/0x98) from [<c037ec4c>] (ip48c/0x54c) from [<c037b9d8>] (ne2b77f4>] (br_handle_frame+0x1ac/
May  5 07:05:02 kernel: ____________________________________________________________________________

Does anyone know what this means? I'm on 384.6 firmware on an RT-AC68U.
 
I don't know the answer, someone more knowledgeable will be here soon

but there are clues about flash and/or virtual memory having problems:

"jbd2" is a kernel thread that updates the filesystem journal, according to Google.
"Unable to handle kernel paging request" could be a memory address access problem.

So, you have to check which additional things you are running on Asus Merlin (ad blocker, DNS, etc..) and update them, or shut them off until you can narrow down which one is causing memory address problems (ie..expecting something to be at a certain address, and it's not there)

If you are running only Asus Merlin and nothing additional, then it's possible this is a hardware issue that is unique to your device as there would be massive reports of virtual memory errors after alpha, beta, or final release. Or it could be just a tiny random one-off fluke, ie..random power fluctuation, the sun flipped a bit, etc...
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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