Suspicious sudden restart RT-AC87U

[Ojee]

I own an Asus RT-AC87U, running the Asus provided firmware. I haven't upgraded it to Merlin or any other third party firmware yet as it is currently running fine, but I might in the future for giggles. It was running flawlessly for months, until it suddenly restarted on the 24th of november. There is no new firmware out, so I thought it was weird.

Here is the log. As you can see, nothing happened for almost 4 months until the sudden restart:

Aug 1 02:00:41 ntp: start NTP update
Nov 24 17:20:17 rc_service: ntp 823:notify_rc restart_upnp
Nov 24 17:20:18 rc_service: ntp 823:notify_rc restart_diskmon
Nov 24 17:20:18 disk_monitor: Finish
Nov 24 17:20:19 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Nov 24 17:20:21 disk monitor: be idle
Nov 24 17:20:21 kernel: sizeof forward param = 160
Nov 24 17:20:27 rc_service: udhcpc 571:notify_rc start_firewall
Nov 24 17:20:27 dhcp client: bound [IP ADDRESS] via [IP ADDRESS] during 259200 seconds.
Nov 24 17:20:28 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Nov 24 17:20:37 crond[477]: time disparity of 1219220 minutes detected
Nov 24 17:20:38 qtn: bootcfg.tgz exists
Nov 24 17:20:53 dnsmasq-dhcp[468]: [REDACTED]
Nov 24 17:21:46 rc_service: rc 1568:notify_rc restart_wrs
Nov 24 17:22:08 hour monitor: ntp sync fail, will retry after 120 sec
Nov 24 17:23:55 ALERT MAIL: AiProtection send mail
Nov 24 17:24:25 ALERT MAIL: AiProtection send mail
Nov 24 17:41:25 ALERT MAIL: AiProtection send mail
Nov 24 18:00:21 disk_monitor: Got SIGALRM...
Nov 24 18:39:43 dnsmasq-dhcp[468]: [REDACTED]
Nov 24 23:00:21 disk_monitor: Got SIGALRM...

I have to admit I'm a bit of a novice when it comes to networking, so I don't know what any of this means. I tried searching this forum before I posted, but could find anything similar. Can you guys help me find out why it restarted itself?

 

[ColinTaylor]

There wasn't a 4 month gap. The router doesn't have a battery-backed clock so when it reboots the date and time are reset to a default value (1st August @ 02:00 in your case). As soon as the internet comes back online it corrects the date/time with NTP.

But to understand why it rebooted we'd need to see the log before it restarted not after.

 

[Ojee]

You are correct. The log file shows that the entries for 1st of august came after 23rd of november.

Here is the log for that day before the restart:

Aug 1 02:00:12 syslogd started: BusyBox v1.17.4
Aug 1 02:00:12 kernel: klogd started: BusyBox v1.17.4 (2017-06-01 23:40:39 CST)
Aug 1 02:00:12 kernel: Linux version 2.6.36.4brcmarm (root@asus) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Thu Jun 1 23:49:59 CST 2017
Aug 1 02:00:12 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
Aug 1 02:00:12 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Aug 1 02:00:12 kernel: Machine: Northstar Prototype
Aug 1 02:00:12 kernel: Ignoring unrecognised tag 0x00000000
Aug 1 02:00:12 kernel: Memory policy: ECC disabled, Data cache writealloc
Aug 1 02:00:12 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60416
Aug 1 02:00:12 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Aug 1 02:00:12 kernel: Memory: 255512k/255512k available, 6632k reserved, 0K highmem
Aug 1 02:00:12 kernel: Virtual kernel memory layout:
Aug 1 02:00:12 kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB)
Aug 1 02:00:12 kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
Aug 1 02:00:12 kernel: DMA : 0xf7e00000 - 0xffe00000 ( 128 MB)
Aug 1 02:00:12 kernel: vmalloc : 0xd0800000 - 0xf0000000 ( 504 MB)
Aug 1 02:00:12 kernel: lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
Aug 1 02:00:12 kernel: modules : 0xbf000000 - 0xc0000000 ( 16 MB)
Aug 1 02:00:12 kernel: .init : 0xc0008000 - 0xc003d000 ( 212 kB)
Aug 1 02:00:12 kernel: .text : 0xc003d000 - 0xc03a5000 (3488 kB)
Aug 1 02:00:12 kernel: .data : 0xc03bc000 - 0xc03df160 ( 141 kB)
Aug 1 02:00:12 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored.
Aug 1 02:00:12 kernel: Mount-cache hash table entries: 512
Aug 1 02:00:12 kernel: CPU1: Booted secondary processor
Aug 1 02:00:12 kernel: Found a AMD NAND flash:
Aug 1 02:00:12 kernel: Total size: 128MB
Aug 1 02:00:12 kernel: Block size: 128KB
Aug 1 02:00:12 kernel: Page Size: 2048B
Aug 1 02:00:12 kernel: OOB Size: 64B
Aug 1 02:00:12 kernel: Sector size: 512B
Aug 1 02:00:12 kernel: Spare size: 16B
Aug 1 02:00:12 kernel: ECC level: 8 (8-bit)
Aug 1 02:00:12 kernel: Device ID: 0x 1 0xf1 0x80 0x1d 0x 1 0xf1
Aug 1 02:00:12 kernel: bio: create slab <bio-0> at 0
Aug 1 02:00:13 kernel: PCI: no core
Aug 1 02:00:13 kernel: PCI: no core
Aug 1 02:00:13 kernel: PCI: Fixing up bus 0
Aug 1 02:00:13 kernel: PCI: Fixing up bus 0
Aug 1 02:00:13 kernel: PCI: Fixing up bus 1
Aug 1 02:00:13 kernel: VFS: Disk quotas dquot_6.5.2
Aug 1 02:00:13 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Aug 1 02:00:13 kernel: pflash: found no supported devices
Aug 1 02:00:13 kernel: bcmsflash: found no supported devices
Aug 1 02:00:13 kernel: Boot partition size = 524288(0x80000)
Aug 1 02:00:13 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Aug 1 02:00:13 kernel: nflash: squash filesystem with lzma found at block 28
Aug 1 02:00:13 kernel: Creating 4 MTD partitions on "nflash":
Aug 1 02:00:13 kernel: 0x000000000000-0x000000080000 : "boot"
Aug 1 02:00:13 kernel: 0x000000080000-0x000000200000 : "nvram"
Aug 1 02:00:13 kernel: 0x000000200000-0x000004000000 : "linux"
Aug 1 02:00:13 kernel: 0x00000039b01c-0x000004000000 : "rootfs"
Aug 1 02:00:13 kernel: Registering the dns_resolver key type
Aug 1 02:00:13 kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Aug 1 02:00:13 kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
Aug 1 02:00:13 kernel: Available 7 bytes at (off,len):
Aug 1 02:00:13 kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0)
Aug 1 02:00:13 kernel: Options: NO_AUTOINCR,NO_READRDY,BBT_SCAN2NDPAGE,
Aug 1 02:00:13 kernel: Creating 2 MTD partitions on "brcmnand":
Aug 1 02:00:13 kernel: 0x000004000000-0x000007ec0000 : "brcmnand"
Aug 1 02:00:13 kernel: 0x000007ec0000-0x000008000000 : "asus"
Aug 1 02:00:13 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Aug 1 02:00:13 kernel: ctf: module license 'Proprietary' taints kernel.
Aug 1 02:00:13 kernel: Disabling lock debugging due to kernel taint
Aug 1 02:00:13 kernel: et_module_init: passivemode set to 0x0
Aug 1 02:00:13 kernel: et_module_init: txworkq set to 0x0
Aug 1 02:00:13 kernel: et_module_init: et_txq_thresh set to 0xce4
Aug 1 02:00:13 kernel: =================
Aug 1 02:00:13 kernel: robo chk regs:
Aug 1 02:00:13 kernel: ===================
Aug 1 02:00:13 kernel: (0x00,0x5d)Port 5 States Override: 0xfb
Aug 1 02:00:13 kernel: (0x00,0x5f)Port 7 States Override: 0xfb
Aug 1 02:00:13 kernel: (0x00,0x0e)Port 8 States Override: 0x0a
Aug 1 02:00:13 kernel: (0x00,0x08)Port 8 IMP Control Register: 0x00
Aug 1 02:00:13 kernel: (0x02,0x00) Global Management Config: 0x00
Aug 1 02:00:13 kernel: (0x02,0x00) 802.1Q VLAN Control 5: 0x00
Aug 1 02:00:13 kernel: (0x02,0x03) BRCM HDR Control Register: 0x00
Aug 1 02:00:13 kernel: (0x00,0x0b) Switch Mode Register: 0x06
Aug 1 02:00:13 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller [IP ADDRESS] (r561982)
Aug 1 02:00:13 kernel: wl_module_init: passivemode set to 0x0
Aug 1 02:00:13 kernel: wl_module_init: igs set to 0x0
Aug 1 02:00:13 kernel: wl_module_init: txworkq set to 0x0
Aug 1 02:00:13 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller [IP ADDRESS] (r561982)
Aug 1 02:00:13 kernel: _ Reboot message ... _______________________________________________________
Aug 1 02:00:13 kernel: <1>Unable to handle kernel NULL pointer derefere�U�at virtual address 00000000
Aug 1 02:00:13 kernel: <1>pgd = ceeb4000
Aug 1 02:00:13 kernel: <1>[00000000] *pgd=9de35031, *pte=00000000, *ppte=00000000
Aug 1 02:00:13 kernel: <0>Internal error: Oops: 817 [#1] PREEMPT SMP
Aug 1 02:00:13 kernel: <0>last sysfs file: /sys/module/bw_forward/parameters/dev_wan

Can you make sense of this? Also, I removed the IP addresses and MAC addresses from the logs above before posting. Is there any other information that I should keep private?

Also I've seem to have hit a character limit. I'll split this up into two posts

 

[Ojee]

Aug 1 02:00:13 kernel: <4>module: nf_nat_sip bf71d000 5031

Aug 1 02:00:14 kernel: <4>module: nf_conntrack_sip bf714000 15713

Aug 1 02:00:14 kernel: <4>module: nf_nat_h323 bf70d000 4761

Aug 1 02:00:14 kernel: <4>module: nf_conntrack_h323 bf6ff000 33807

Aug 1 02:00:14 kernel: <4>module: nf_nat_rtsp bf6f9000 3202

Aug 1 02:00:14 kernel: <4>module: nf_conntrack_rtsp bf6f3000 4067

Aug 1 02:00:14 kernel: <4>module: nf_nat_ftp bf6ed000 1144

Aug 1 02:00:14 kernel: <4>module: nf_conntrack_ftp bf6e6000 4909

Aug 1 02:00:14 kernel: <4>module: ip6table_mangle bf6e0000 934

Aug 1 02:00:14 kernel: <4>module: cdc_mbim bf6da000 3129

Aug 1 02:00:14 kernel: <4>module: qmi_wwan bf6d3000 5780

Aug 1 02:00:14 kernel: <4>module: cdc_wdm bf6cc000 7252

Aug 1 02:00:14 kernel: <4>module: cdc_ncm bf6c4000 8750

Aug 1 02:00:14 kernel: <4>module: rndis_host bf6bd000 4936

Aug 1 02:00:14 kernel: <4>module: cdc_ether bf6b7000 3187

Aug 1 02:00:14 kernel: <4>module: asix bf6af000 10832

Aug 1 02:00:14 kernel: <4>module: usbnet bf6a6000 11161

Aug 1 02:00:14 kernel: <4>module: mii bf6a0000 3367

Aug 1 02:00:14 kernel: <4>module: usblp bf698000 10321

Aug 1 02:00:14 kernel: <4>module: ohci_hcd bf68e000 17918

Aug 1 02:00:14 kernel: <4>module: ehci_hcd bf681000 31565

Aug 1 02:00:14 kernel: <4>module: xhci_hcd bf66e000 50352

Aug 1 02:00:14 kernel: <4>module: thfsplus bf652000 81793

Aug 1 02:00:14 kernel: <4>module: tntfs bf5d6000 454497

Aug 1 02:00:14 kernel: <4>module: tfat bf59d000 188546

Aug 1 02:00:14 kernel: <4>module: ext2 bf589000 52776

Aug 1 02:00:14 kernel: <4>module: ext4 bf548000 221674

Aug 1 02:00:14 kernel: <4>module: jbd2 bf535000 48993

Aug 1 02:00:14 kernel: <4>module: crc16 bf52f000 1007

Aug 1 02:00:14 kernel: <4>module: ext3 bf50d000 106409

Aug 1 02:00:14 kernel: <4>module: jbd bf4fc000 42367

Aug 1 02:00:14 kernel: <4>module: mbcache bf4f5000 4599

Aug 1 02:00:14 kernel: <4>module: usb_storage bf4e6000 34110

Aug 1 02:00:14 kernel: <4>module: sg bf4db000 19855

Aug 1 02:00:14 kernel: <4>module: sd_mod bf4cf000 21983

Aug 1 02:00:14 kernel: <4>module: scsi_wait_scan bf4c9000 416

Aug 1 02:00:14 kernel: <4>module: scsi_mod bf4a4000 108738

Aug 1 02:00:14 kernel: <4>module: usbcore bf481000 101810

Aug 1 02:00:14 kernel: <4>module: ebt_ip bf47b000 1322

Aug 1 02:00:14 kernel: <4>module: ebtable_broute bf475000 873

Aug 1 02:00:14 kernel: <4>module: ebtable_filter bf46f000 1061

Aug 1 02:00:14 kernel: <4>module: ebtables bf466000 15643

Aug 1 02:00:14 kernel: <4>module: ip6t_LOG bf45f000 4494

Aug 1 02:00:14 kernel: <4>module: ip6table_filter bf459000 750

Aug 1 02:00:14 kernel: <4>module: jffs2 bf43b000 91274

Aug 1 02:00:14 kernel: <4>module: zlib_deflate bf431000 19489

Aug 1 02:00:14 kernel: <4>module: wl bf033000 3938142

Aug 1 02:00:14 kernel: <4>module: igs bf02b000 11887

Aug 1 02:00:14 kernel: <4>module: emf bf022000 15225

Aug 1 02:00:14 kernel: <4>module: et bf00b000 61445

Aug 1 02:00:14 kernel: <4>module: ctf bf000000 20515

Aug 1 02:00:14 kernel: <4>Modules linked in: nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_rtsp nf_conntrack_rtsp nf_nat_ftp nf_conntrack_ftp ip6table_mangle cdc_mbim qmi_wwan cdc_wdm cdc_ncm rndis_host cdc_ether asix usbnet mii usblp ohci_hcd ehci_hcd xhci_hcd thfsplus tntfs(P) tfat(P) ext2 ext4 jbd2 crc16 ext3 jbd mbcache usb_storage sg sd_mod scsi_wait_scan scsi_mod usbcore ebt_ip ebtable_broute ebtable_filter ebtables ip6t_LOG ip6table_filter jffs2 zlib_deflate wl(P) igs(P) emf(P

Aug 1 02:00:14 kernel: <4>CPU: 0 Tainted: P (2.6.36.4brcmarm #1)

Aug 1 02:00:14 kernel: <4>PC is at __bug+0x1c/0x28

Aug 1 02:00:14 kernel: <4>LR is at __bug+0x18/0x28

Aug 1 02:00:14 kernel: <4>pc : [<c004113c>] lr : [<c0041138>] psr: 60000013

Aug 1 02:00:14 kernel: <4>sp : ca947e20 ip : 0000005f fp : cf53b39c

Aug 1 02:00:14 kernel: <4>r10: cdd0a288 r9 : 00000000 r8 : 00000000

Aug 1 02:00:14 kernel: <4>r7 : cae8feb0 r6 : cf971600 r5 : 00000000 r4 : cf53b380

Aug 1 02:00:14 kernel: <4>r3 : 00000000 r2 : ca946000 r1 : 60000013 r0 : 00000027

Aug 1 02:00:14 kernel: <4>Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user

Aug 1 02:00:14 kernel: <4>Control: 10c53c7d Table: 9eeb404a DAC: 00000015

Aug 1 02:00:14 kernel: <0>Process bwdpi_sqlite (pid: 5128, stack limit = 0xca946270)

Aug 1 02:00:14 kernel: <0>Stack: (0xca947e20 to 0xca948000)

Aug 1 02:00:14 kernel: <0>7e20: 00000002 bf446298 cf971600 00000023 00000000 cae8feb0 cdd0a288 00000023

Aug 1 02:00:14 kernel: <0>7e40: cdd0a288 bf4488c0 00000000 00000000 00000000 00000007 c03c3b3c ca946000

Aug 1 02:00:14 kernel: <0>7e60: c0412cbc c003b9d0 ca946000 00000000 ca946000 cfb7c008 cf9716f8 c00678ec

Aug 1 02:00:14 kernel: <0>7e80: 000000b4 c03830c0 ffffffff f0100100 000000b4 00000002 00000001 cf971600

Aug 1 02:00:14 kernel: <0>7ea0: cf971600 00000023 00000000 cae8feb0 cdd0a288 bf448f84 cf97163c 0000b46c

Aug 1 02:00:14 kernel: <0>7ec0: cae8feb0 cf971600 cf971700 cf97163c 00000001 cae8feb0 cdd0a288 cf53b380

Aug 1 02:00:14 kernel: <0>7ee0: cf97172c bf44678c 00000001 00000000 00000000 00014b94 00000000 00000000

Aug 1 02:00:14 kernel: <0>7f00: 00000000 00000000 00000000 ffffffff 7fffffff cf971600 cf97163c 03421800

Aug 1 02:00:14 kernel: <0>7f20: 000004e0 c003dc68 ca946000 00000000 00015b70 bf44a980 cf971a00 00000000

Aug 1 02:00:14 kernel: <0>7f40: 7fffffff cf53b7bc cef4d8c0 bf43d270 bf43d254 c00ebde0 ffffffff 7fffffff

Aug 1 02:00:14 kernel: <0>7f60: 00000006 ffffffff 7fffffff 00000000 00000094 c00ebe98 ffffffff 7fffffff

Aug 1 02:00:14 kernel: <0>7f80: 00000001 bee4f2e0 00015b70 cef4d8c0 00000001 c00ebec0 401b9c0c 00015b40

Aug 1 02:00:14 kernel: <0>7fa0: 40221e0c c003dac0 00015b40 40221e0c 00000006 00000002 00000000 401b9c0c

Aug 1 02:00:14 kernel: <0>7fc0: 00015b40 40221e0c 00000000 00000094 00000000 00000000 bee4f2e0 00015b70

Aug 1 02:00:14 kernel: <0>7fe0: 40221ef4 bee4f298 401b9c1c 40109a68 80000010 00000006 00000000 00000000

Aug 1 02:00:14 kernel: <4>[<c004113c>] (PC is at __bug+0x1c/0x28)

 

[Ojee]

Aug 1 02:00:14 kernel: <4>LR is at __bug+0x18/0x28
Aug 1 02:00:14 kernel: <4>pc : [<c004113c>] lr : [<c0041138>] psr: 60000013

Aug 1 02:00:14 kernel: <4>sp : ca947e20 ip : 0000005f fp : cf53b39c

Aug 1 02:00:14 kernel: <4>r10: cdd0a288 r9 : 00000000 r8 : 00000000

Aug 1 02:00:14 kernel: <4>r7 : cae8feb0 r6 : cf971600 r5 : 00000000 r4 : cf53b380

Aug 1 02:00:14 kernel: <4>r3 : 00000000 r2 : ca946000 r1 : 60000013 r0 : 00000027

Aug 1 02:00:14 kernel: <4>Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user

Aug 1 02:00:14 kernel: <4>Control: 10c53c7d Table: 9eeb404a DAC: 00000015

Aug 1 02:00:14 kernel: <0>Process bwdpi_sqlite (pid: 5128, stack limit = 0xca946270)

Aug 1 02:00:14 kernel: <0>Stack: (0xca947e20 to 0xca948000)

Aug 1 02:00:14 kernel: <0>7e20: 00000002 bf446298 cf971600 00000023 00000000 cae8feb0 cdd0a288 00000023

Aug 1 02:00:14 kernel: <0>7e40: cdd0a288 bf4488c0 00000000 00000000 00000000 00000007 c03c3b3c ca946000

Aug 1 02:00:14 kernel: <0>7e60: c0412cbc c003b9d0 ca946000 00000000 ca946000 cfb7c008 cf9716f8 c00678ec

Aug 1 02:00:14 kernel: <0>7e80: 000000b4 c03830c0 ffffffff f0100100 000000b4 00000002 00000001 cf971600

Aug 1 02:00:14 kernel: <0>7ea0: cf971600 00000023 00000000 cae8feb0 cdd0a288 bf448f84 cf97163c 0000b46c

Aug 1 02:00:14 kernel: <0>7ec0: cae8feb0 cf971600 cf971700 cf97163c 00000001 cae8feb0 cdd0a288 cf53b380

Aug 1 02:00:14 kernel: <0>7ee0: cf97172c bf44678c 00000001 00000000 00000000 00014b94 00000000 00000000

Aug 1 02:00:14 kernel: <0>7f00: 00000000 00000000 00000000 ffffffff 7fffffff cf971600 cf97163c 03421800

Aug 1 02:00:14 kernel: <0>7f20: 000004e0 c003dc68 ca946000 00000000 00015b70 bf44a980 cf971a00 00000000

Aug 1 02:00:14 kernel: <0>7f40: 7fffffff cf53b7bc cef4d8c0 bf43d270 bf43d254 c00ebde0 ffffffff 7fffffff

Aug 1 02:00:14 kernel: <0>7f60: 00000006 ffffffff 7fffffff 00000000 00000094 c00ebe98 ffffffff 7fffffff

Aug 1 02:00:14 kernel: <0>7f80: 00000001 bee4f2e0 00015b70 cef4d8c0 00000001 c00ebec0 401b9c0c 00015b40

Aug 1 02:00:14 kernel: <0>7fa0: 40221e0c c003dac0 00015b40 40221e0c 00000006 00000002 00000000 401b9c0c

Aug 1 02:00:14 kernel: <0>7fc0: 00015b40 40221e0c 00000000 00000094 00000000 00000000 bee4f2e0 00015b70

Aug 1 02:00:14 kernel: <0>7fe0: 40221ef4 bee4f298 401b9c1c 40109a68 80000010 00000006 00000000 00000000

Aug 1 02:00:14 kernel: <4>[<c004113c>] (PC is at __bug+0x1c/0x28)

Aug 1 02:00:14 kernel: <4>[<c004113c>] (__bug+0x1c/0x28) from [<bf446298>] (jffs2_rotate_lists+0x172c/0x18ac [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf446298>] (jffs2_rotate_lists+0x172c/0x18ac [jffs2]) from [<bf44678c>] (jffs2_garbage_collect_pass+0x374/0x7d8 [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf44678c>] (jffs2_garbage_collect_pass+0x374/0x7d8 [jffs2]) from [<bf44a980>] (jffs2_flush_wbuf_gc+0x90/0x134 [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf44a980>] (jffs2_flush_wbuf_gc+0x90/0x134 [jffs2]) from [<bf43d270>] (jffs2_fsync+0x1c/0x24 [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf43d270>] (jffs2_fsync+0x1c/0x24 [jffs2]) f ^C[<c00ebde0>] (vfs_fsync_range+0x6c/0x84)

Aug 1 02:00:14 kernel: <4>[<c00ebde0>] (vfs_fsync_range+0x6c/0x84) from [<c00ebe98>] (vfs_fsync+0x24/0x2c)

Aug 1 02:00:14 kernel: <4>[<c00ebe98>] (vfs_fsync+0x24/0x2c) from [<c00ebec0>] (do_fsync+0x20/0x34)

Aug 1 02:00:14 kernel: <4>[<c00ebec0>] (do_fsync+0x20/0x34) from [<c003dac0>] (ret_fast_syscall+0x0/0x30)

Aug 1 02:00:14 kernel: <0>Code: e59f0010 e1a01003 eb0a1be2 e3a03000 (e5833000)

Aug 1 02:00:14 kernel: <4>---[ end trace 5b3db3e8dbec04d8 ]---

Aug 1 02:00:14 kernel: <0>Kernel panic - not syncing: Fatal exception

Aug 1 02:00:14 kernel: <4>[<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c02c7f98>] (panic+0x7c/0x1a8)

Aug 1 02:00:14 kernel: <4>[<c02c7f98>] (panic+0x7c/0x1a8) from [<c00416f0>] (die+0x1a4/0x1dc)

Aug 1 02:00:14 kernel: <4>[<c00416f0>] (die+0x1a4/0x1dc) from [<c004515c>] (__do_kernel_fault+0x6c/0x8c)

Aug 1 02:00:14 kernel: <4>[<c004515c>] (__do_kernel_fault+0x6c/0x8c) from [<c00452cc>] (do_page_fault+0x150/0x1ec)

Aug 1 02:00:14 kernel: <4>[<c00452cc>] (do_page_fault+0x150/0x1ec) from [<c003d3a4>] (do_DataAbort+0x30/0x9c)

Aug 1 02:00:14 kernel: <4>[<c003d3a4>] (do_DataAbort+0x30/0x9c) from [<c0382b8c>] (__dabt_svc+0x4c/0x60)

Aug 1 02:00:14 kernel: <4>Exception stack(0xca947dd8 to 0xca947e20)

Aug 1 02:00:14 kernel: <4>7dc0: 00000027 60000013

Aug 1 02:00:14 kernel: <4>7de0: ca946000 00000000 cf53b380 00000000 cf971600 cae8feb0 00000000 00000000

Aug 1 02:00:14 kernel: <4>7e00: cdd0a288 cf53b39c 0000005f ca947e20 c0041138 c004113c 60000013 ffffffff

Aug 1 02:00:14 kernel: <4>[<c0382b8c>] (__dabt_svc+0x4c/0x60) from [<c004113c>] (__bug+0x1c/0x28)

Aug 1 02:00:14 kernel: <4>[<c004113c>] (__bug+0x1c/0x28) from [<bf446298>] (jffs2_rotate_lists+0x172c/0x18ac [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf446298>] (jffs2_rotate_lists+0x172c/0x18ac [jffs2]) from [<bf44678c>] (jffs2_garbage_collect_pass+0x374/0x7d8 [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf44678c>] (jffs2_garbage_collect_pass+0x374/0x7d8 [jffs2]) from [<bf44a980>] (jffs2_flush_wbuf_gc+0x90/0x134 [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf44a980>] (jffs2_flush_wbuf_gc+0x90/0x134 [jffs2]) from [<bf43d270>] (jffs2_fsync+0x1c/0x24 [jffs2])

Aug 1 02:00:14 kernel: <4>[<bf43d270>] (jffs2_fsync+0x1c/0x24 [jffs2]) from [<c00ebde0>] (vfs_fsync_range+0x6c/0x84)

Aug 1 02:00:14 kernel: <4>[<c00ebde0>] (vfs_fsync_range+0x6c/0x84) from [<c00ebe98>] (vfs_fsync+0x24/0x2c)

Aug 1 02:00:14 kernel: <4>[<c00ebe98>] (vfs_fsync+0x24/0x2c) from [<c00ebec0>] (do_fsync+0x20/0x34)

Aug 1 02:00:14 kernel: <4>[<c00ebec0>] (do_fsync+0x20/0x34) from [<c003dac0>] (ret_fast_syscall+0x0/0x30)

Aug 1 02:00:14 kernel: <0>Rebooting in 3 seconds..: stopping

Aug 1 02:00:14 kernel: <4>[<c0043ff8>] (unwi03d334>] (do_IPI+0x114/0x154)

Aug 1 02:00:14 kernel: <4>[<c003d334>] (do_IPI+0x114/0x154) from [<c0382be8>] (__irq_svc+0x48/0xe8)

Aug 1 02:00:14 kernel: <4>Exception stack(0xcb8d1ad8 to 0xcb8d1b20)

Aug 1 02:00:14 kernel: <4>1ac0:60000013

Aug 1 02:00:14 kernel: <4>1ae0: c03ca03c c03ca0407a10 00000000 c0407ad0

Aug 1 02:00:14 kernel: <4>1b0q_svc+0x48/0xe8) from [<c0062f58>] (vprintk+0x2dc/0x488)

Aug 1 02:00:14 kernel: <4>[<c034)

Aug 1 02:00:14 kernel: <4>[<c02c80e4>] (printk+0x2000414f0>] (dump_backtrace_entry+wind_backtrace+0x74/0xf8)

Aug 1 02:00:14 kernel: <4>[<clowpath_common+0x4c/0x64)

Aug 1 02:00:14 kernel: <4>[<c0x4c/0x64) from [<c0061db4>] (warn_slowpath_null+0x1c/0x24)

Aug 1 02:00:14 kernel: <4>

Aug 1 02:00:14 stop_nat_rules: apply the redirect_rules!

Aug 1 02:00:14 kernel: ____________________________________________________________________________

Aug 1 02:00:14 qcsapi: write qcsapi conf ok

Aug 1 02:00:14 WAN Connection: ISP's DHCP did not function properly.

Aug 1 02:00:15 kernel: JFFS2 notice: (338) check_node_data: wrong data CRC in data node at 0x034217a0: read 0x7a7f97b5, calculated 0x39743039.

Aug 1 02:00:31 RT-AC87U: start httpd - SSL

Aug 1 02:00:31 RT-AC87U: start httpd

Aug 1 02:00:32 jffs2: valid logs(1)

Aug 1 02:00:32 hour monitor: daemon is starting

Aug 1 02:00:32 disk monitor: be idle

Aug 1 02:00:32 syslog: Generating SSL certificate...

Aug 1 02:00:32 syslog: Generating SSL certificate...

Aug 1 02:00:32 wan: mac clone: [wan0_hwaddr] == [MAC ADDRESS]

Aug 1 02:00:33 rc_service: udhcpc 571:notify_rc start_firewall

Aug 1 02:00:33 rc_service: udhcpc 571:notify_rc stop_upnp

Aug 1 02:00:33 rc_service: waitting "start_firewall" via udhcpc ...

Aug 1 02:00:33 kernel: SCSI subsystem initialized

Aug 1 02:00:34 WAN Connection: WAN was restored.

Aug 1 02:00:35 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X

Aug 1 02:00:35 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry

Aug 1 02:00:35 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values

Aug 1 02:00:37 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!

Aug 1 02:00:38 kernel: nf_conntrack_rtsp v0.6.21 loading

Aug 1 02:00:38 kernel: nf_nat_rtsp v0.6.21 loading

Aug 1 02:00:39 rc_service: udhcpc 571:notify_rc start_upnp

Aug 1 02:00:39 rc_service: waitting "stop_upnp" via udhcpc ...

Aug 1 02:00:41 ntp: start NTP update

Nov 24 17:20:17 rc_service: ntp 823:notify_rc restart_upnp

 

[ColinTaylor]

You're still only showing the entries after the router restarted, indicated by "Aug 1 02:00:12 syslogd started: BusyBox v1.17.4". It would be useful to see if there were any messages immediately before this point.

That said, the crash dump indicates that there was a kernel panic that might be related to an attempt to write to jffs. There seems to be quite a few similar reports of these kind of message on the forum recently.

I would suggest that you flash the latest firmware, perform a factory default restore and then reconfigure your router manually (do not reload saved settings).

 

[Ojee]

What is jffs?

The log entries before aug 1 are the following:

Nov 7 17:48:53 WAN Connection: WAN was restored.
Nov 7 17:48:55 rc_service: udhcpc 2529:notify_rc start_firewall
Nov 7 17:48:55 dhcp client: bound [IP ADDRESS] via [IP ADDRESS] during 140632 seconds.
Nov 7 17:48:56 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Nov 7 18:00:44 disk_monitor: Got SIGALRM...
Nov 7 23:00:44 disk_monitor: Got SIGALRM...
Nov 11 09:06:05 dnsmasq-dhcp[466]: Ignoring domain [REDACTED]
Nov 11 21:06:04 dnsmasq-dhcp[466]: Ignoring domain [REDACTED]
Nov 12 02:00:11 rc_service: rc 28687:notify_rc restart_wrs
Nov 24 08:30:38 dnsmasq-dhcp[466]: Ignoring domain [REDACTED]

I scrolled through the entire log, and Aug 1st seems to pop up more often, with the same time of kernel crash dump: July 7th, October 14th, Oct 30th, Nov 7th...

I am running the latest firmware.

 

[ColinTaylor]

JFFS is an area of non-volatile storage on the router that is used to store things like log files (a bit like a USB flash drive). If that has become corrupted it can result in the kind of crash you are seeing. By re-flashing the firmware and resetting to factory defaults such corruptions can usually be fixed.

 

[st3v3n]

Ojee, greetings, (hi ColinTaylor), this just an idle thought, looking at your post, are you using the Asus.comm.com DDNS for your server? I ask because this was very similar to what happened to our unit a while back. May not be related, but reminded me of what I saw with ours while it was going on.

 

[Ojee]

Good question, I hadn't looked at that. My ISP requires the router to be set to discover setting automatically, so I assumed de DNS server would be provided by my ISP? Or am I now mixing up terms?

 

[st3v3n]

You don't have to use the ISP's DNS, unless that's what you prefer, seems they're instituting some draconian customer TOS I wouldn"t subscribe to

 

[ColinTaylor]

Good question, I hadn't looked at that. My ISP requires the router to be set to discover setting automatically, so I assumed de DNS server would be provided by my ISP? Or am I now mixing up terms?

Yes, Asus DDNS and your WAN DNS are two completely different things.

 

[st3v3n]

G'Morning gents, I didn't intend to interject or confuse the issue involved, if my question somehow inadvertently intimated to anyone that DDNS/WAN DNS, were related or causing OPs issue, which isn't the case; pardon if my question and thought process caused consternation. I know what I was thinking. I will retire back into the ether with coffee in hand Carry on

 

[Ojee]

You don't have to use the ISP's DNS, unless that's what you prefer, seems they're instituting some draconian customer TOS I wouldn"t subscribe to

Such as? I've never heard of this before.

Also, I've installed the merlin firmware now, let's see if this is a little more stable.

 

[st3v3n]

Ojee, I hope the new version of Merlin is working out well for you.

If you don't enter an DNS server address in WAN DNS setting, (depending on your model and what version you're running), if you untick the "connect to DNS server automatically" box, as long as your traffic is using an OpenVPN config/tunnel and your devices are routed appropriately, they will use the VPN provider's 'smart/private DNS' server, and/or the alternate DNS server(s) you list on the LAN DHCP server page, where you can manually assign the IPs around the list.

Sometimes (not always) if a device is balky or lags with a VPN provider's internal solution, say like certain WiFi tablets/phones, I've foung that by entering google's 8.8.8.8 (or any other you prefer) in the LAN page may append on the OpenVPN config depending on the provider., I've seen it show up in the logs. There's a lot more to it that that, but if you aren't using your VPN provider's internal DNS solution, choose your DNS carefully; many use OpenNIC no log DNS, but it depends on your needs. Google swears it doesn't keep all of the DNS info very long, if you believe that, but since most of the planet uses it, the amount of internet noise and laws of probability, will give you fast response and a better margin of blending in than you'll have by settling for using your ISP's DNS. You could run GRC.org's DNS test to find the fastest DNS resolver if all you require is speed.

As for 'draconian TOS' some of the ISPs are now throttling OpenVPN traffic, whereas before they didn't care as much what you looked at or researched, as long as you weren't engaged in conduct that would get you warned or kicked off. If The ISP hasn't specifically agreed that they won't give away/sell all of your internet history as their DNS servers store and show, they're probably doing it. That seems draconian enough to the many who value their privacy, especially if they aren't doing anything illegal, immoral or fattening (tip of the hat to Flo & Eddie). If you don't mind that sort of invasive treatment by your ISP, it's whatever DNS you choose to use.

If your traffic isn't secured by using a VPN provider who offers OpenVPN as you can use in your Asus router with Merlin, it's a safe bet the ISP will log, mine and sell everything. It's not right, but to each his/her own, and you have to be able to trust the VPN provider you pay to honor their promises not to spy on you or sell your data. I'd rather put up with an ISP throttling my OpenVPN traffic, since they all throttle these days, even if they state they don't, ala ATT. Not using the ISP's DNS is a choice you have to make, otherwise every click and swipe stored on the ISP's DNS servers are subject to mining/selling to whomever they please. None of the ISPs publicly say they won't sell the DNS history, but ATT will sell you the supposed right to 'turn off' their mining/storing/selling of your history. That's why no one believes them. It's whether you believe enough in a certain right or level of personal privacy, that we used to take for granted, that's at stake.

If your VPN service obscures/secures your traffic with an OpenVPN tunnel the info from their DNS servers should exit with your VPN's IP address, not yours. Most of the VPN companies have good DNS, and if you're using an OpenVPN shared or modulated tunnel, there's much less chance your history is going to be of much value to anyone, to be sold or mined, the same as it will be if you utilize your local ISP's servers.

The smaller ISPs are into the data-selling game as much as the big cats, since they pay whatever the large providers want for the bandwidth you're paying for, and the price gets only higher. The private ISPs don't usually make their peering contracts public. Even though they aren't starving, they cry poverty every so often and hit the customers with yet another hike every year unless you renegotiate, have a contract or lock your bandwidth rate price in some way. It's probably not draconian, but since you can't turn the tables and sell all of your ISP's private browsing history, it seems draconian. The latest law of the land states they can do it if they feel like it, and there's nothing users can do, except bend over and tie their shoes. Hope that helps, Cheers.

 

[ColinTaylor]

TL;DR

 

[st3v3n]

But it took longer to bother to reply

 

[st3v3n]

It's what I get for feeling helpful at Christmas, but no one has to read it, Scrooged again

 

[ColinTaylor]

I'm just joking, I wasn't being critical. - Unlike flash memory my reading (and comprehending) rate is 5 times slower than my writing rate.

 

[st3v3n]

Bosh, no problem or offense taken. Try to stay thick skinned even on such a well mannered forum. I've always enjoyed all of the longer instructional essays and other posts from VSMs and POTFurniture wizards, going way back when all I did was lurk and read. Now I have to talk it in, the fingers are no longer nimble enough, so I forget talking makes it so longish; speed reading, I still cherish. Maybe we can put in for a human NVRAM implant, nope, none of that. I get a kick out of everyone who remembers all of the old and new abbreviations, but then I still remember DOS tricks banished for years Ho Ho good sirs