ASUS RT-AC68U rebooting on it's own.

Status
Not open for further replies.

AllTimeMitch

New Around Here
Hello all,

Just wanted to query this with anyone who owns one of these routers or a similar one. Occasionally the router seems to restart itself, I've only noticed as the uplink time is very small. I've checked other devices in the home to see if I had a power cut and I haven't. Is this normal?

I've done all the basics such as reinstalling the firmware and resetting factory default settings straight after and it still happens. Below I've included a small snippet of my system log. At this time of this posting (15:16), the uptime is 0 days 2 hours 2 minutes 34 seconds.

Edit - Firmware Version is 3.0.0.4.374_4422. Not sure if that's the issue as it was a new release.

Thanks,
- Mitch

Feb 14 20:14:54 miniupnpd[625]: Expired NAT-PMP mapping port 20268 UDP removed
Feb 14 20:14:54 miniupnpd[625]: Expired NAT-PMP mapping port 20268 TCP removed
Feb 14 20:14:54 rc_service: ntp 629:notify_rc restart_upnp
Feb 14 20:14:54 rc_service: ntp 629:notify_rc restart_diskmon
Feb 14 20:14:54 rc_service: waitting "restart_upnp" via ntp ...
Feb 14 20:14:54 miniupnpd[625]: received signal 15, good-bye
Feb 14 20:14:54 dhcp client: bound 82.47.58.246 via 82.47.58.1 during 590239 seconds.
Feb 14 20:14:55 miniupnpd[642]: HTTP listening on port 43158
Feb 14 20:14:55 miniupnpd[642]: Listening for NAT-PMP traffic on port 5351
Feb 14 20:14:56 disk monitor: be idle
Feb 14 20:15:39 rc_service: httpd 513:notify_rc start_webs_update
Feb 14 23:14:53 miniupnpd[642]: Expired NAT-PMP mapping port 20268 UDP removed
Feb 14 23:14:53 miniupnpd[642]: Expired NAT-PMP mapping port 20268 TCP removed
Feb 14 23:53:28 miniupnpd[642]: sendto(udp): Operation not permitted
Jan 1 00:00:12 syslogd started: BusyBox v1.17.4
Jan 1 00:00:12 kernel: klogd started: BusyBox v1.17.4 (2014-02-12 23:35:03 CST)
Jan 1 00:00:12 kernel: Linux version 2.6.36.4brcmarm ([email protected]) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Wed Feb 12 23:40:38 CST 2014
Jan 1 00:00:12 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
Jan 1 00:00:12 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Jan 1 00:00:12 kernel: Machine: Northstar Prototype
Jan 1 00:00:12 kernel: Ignoring unrecognised tag 0x00000000
Jan 1 00:00:12 kernel: Memory policy: ECC disabled, Data cache writealloc
Jan 1 00:00:12 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 60416
Jan 1 00:00:12 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Jan 1 00:00:12 kernel: Memory: 255508k/255508k available, 6636k reserved, 0K highmem
Jan 1 00:00:12 syslog: module ledtrig-usbdev not found in modules.dep
Jan 1 00:00:12 syslog: module leds-usb not found in modules.dep
Jan 1 00:00:12 kernel: Virtual kernel memory layout:
Jan 1 00:00:12 kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB)
Jan 1 00:00:12 kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
Jan 1 00:00:12 kernel: DMA : 0xf7e00000 - 0xffe00000 ( 128 MB)
Jan 1 00:00:12 kernel: vmalloc : 0xd0800000 - 0xf0000000 ( 504 MB)
Jan 1 00:00:12 kernel: lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
Jan 1 00:00:12 kernel: modules : 0xbf000000 - 0xc0000000 ( 16 MB)
Jan 1 00:00:12 kernel: .init : 0xc0008000 - 0xc003d000 ( 212 kB)
Jan 1 00:00:12 kernel: .text : 0xc003d000 - 0xc03ab000 (3512 kB)
Jan 1 00:00:12 kernel: .data : 0xc03c2000 - 0xc03e4f40 ( 140 kB)
Jan 1 00:00:12 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored.
Jan 1 00:00:12 kernel: Mount-cache hash table entries: 512
Jan 1 00:00:12 kernel: CPU1: Booted secondary processor
Jan 1 00:00:12 kernel: Found a AMD NAND flash:
Jan 1 00:00:12 kernel: Total size: 128MB
Jan 1 00:00:12 kernel: Block size: 128KB
Jan 1 00:00:12 kernel: Page Size: 2048B
Jan 1 00:00:12 kernel: OOB Size: 64B
Jan 1 00:00:12 kernel: Sector size: 512B
Jan 1 00:00:12 kernel: Spare size: 16B
Jan 1 00:00:12 kernel: ECC level: 8 (8-bit)
Jan 1 00:00:12 kernel: Device ID: 0x 1 0xf1 0x 0 0x1d 0x 1 0xf1
Jan 1 00:00:12 kernel: bio: create slab <bio-0> at 0
Jan 1 00:00:12 kernel: PCI: no core
Jan 1 00:00:12 kernel: PCI: no core
Jan 1 00:00:13 kernel: PCI: Fixing up bus 0
Jan 1 00:00:13 kernel: PCI: Fixing up bus 0
Jan 1 00:00:13 kernel: PCI: Fixing up bus 1
Jan 1 00:00:13 kernel: PCI: Fixing up bus 0
Jan 1 00:00:13 kernel: PCI: Fixing up bus 2
Jan 1 00:00:13 syslog: module vfat not found in modules.dep
Jan 1 00:00:13 kernel: VFS: Disk quotas dquot_6.5.2
Jan 1 00:00:13 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan 1 00:00:13 kernel: pflash: found no supported devices
Jan 1 00:00:13 kernel: bcmsflash: found no supported devices
Jan 1 00:00:13 kernel: Boot partition size = 524288(0x80000)
Jan 1 00:00:13 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Jan 1 00:00:13 kernel: nflash: squash filesystem with lzma found at block 28
Jan 1 00:00:13 kernel: Creating 4 MTD partitions on "nflash":
Jan 1 00:00:13 kernel: 0x000000000000-0x000000080000 : "boot"
Jan 1 00:00:13 kernel: 0x000000080000-0x000000200000 : "nvram"
Jan 1 00:00:13 kernel: 0x000000200000-0x000002000000 : "linux"
Jan 1 00:00:13 kernel: 0x00000039e7d8-0x000002000000 : "rootfs"
Jan 1 00:00:13 kernel: === PPTP init ===
Jan 1 00:00:13 kernel: Registering the dns_resolver key type
Jan 1 00:00:13 kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan 1 00: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
Jan 1 00:00:13 kernel: Available 7 bytes at (off,len):
Jan 1 00:00:13 kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0)
Jan 1 00:00:13 kernel: Options: NO_AUTOINCR,NO_READRDY,BBT_SCAN2NDPAGE,
Jan 1 00:00:13 kernel: Creating 1 MTD partitions on "brcmnand":
Jan 1 00:00:13 kernel: 0x000002000000-0x000008000000 : "brcmnand"
Jan 1 00:00:13 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Jan 1 00:00:13 kernel: ctf: module license 'Proprietary' taints kernel.
Jan 1 00:00:13 kernel: Disabling lock debugging due to kernel taint
Jan 1 00:00:13 kernel: et_module_init: passivemode set to 0x0
Jan 1 00:00:13 kernel: et_module_init: txworkq set to 0x1
Jan 1 00:00:13 kernel: et_module_init: et_txq_thresh set to 0x400
Jan 1 00:00:13 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.73 (r448163)
Jan 1 00:00:13 kernel: wl_module_init: passivemode set to 0x0
Jan 1 00:00:13 kernel: wl_module_init: txworkq set to 0x1
Jan 1 00:00:13 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.73 (r448163)
Jan 1 00:00:13 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.73 (r448163)
Jan 1 00:00:13 kernel: SCSI subsystem initialized
Jan 1 00:00:13 kernel: jnl: driver (lke_8.9.0, Feb 13 2014 00:14:34, LBD=ON) loaded at bf5e6000
Jan 1 00:00:13 kernel: ufsd:: trace mask set to 0000000f
Jan 1 00:00:13 kernel: ufsd: driver (lke_8.9.0 lke_8.9.0_r219253_b22, LBD=ON, delalloc, acl, ioctl, ugm, sd(1), wb, tr) loaded at bf5f3000
Jan 1 00:00:13 kernel: NTFS support included
Jan 1 00:00:13 kernel: Hfs+/HfsJ support included
Jan 1 00:00:13 kernel: optimized: speed
Jan 1 00:00:13 kernel: Build_for__Asus_RT-AC56U_k2.6.36_2013-11-07_lke_8.9.0_r219253_b22
Jan 1 00:00:13 kernel: xhci_hcd 0000:00:0b.0: Failed to enable MSI-X
Jan 1 00:00:13 kernel: xhci_hcd 0000:00:0b.0: failed to allocate MSI entry
Jan 1 00:00:13 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values
Jan 1 00:00:14 syslog: module proxyarp not found in modules.dep
Jan 1 00:00:15 stop_nat_rules: apply the redirect_rules!
Jan 1 00:00:15 WAN Connection: ISP's DHCP did not function properly.
Jan 1 00:00:15 RT-AC68U: start httpd
Jan 1 00:00:16 syslog: Generating SSL certificate...
Jan 1 00:00:23 disk monitor: be idle
Jan 1 00:00:23 miniupnpd[552]: HTTP listening on port 55361
Jan 1 00:00:23 miniupnpd[552]: Listening for NAT-PMP traffic on port 5351
Jan 1 00:00:25 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 1 00:00:26 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 00:00:26 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 00:00:26 rc_service: udhcpc 569:notify_rc stop_upnp
Jan 1 00:00:26 rc_service: udhcpc 569:notify_rc start_upnp
Jan 1 00:00:26 miniupnpd[552]: received signal 15, good-bye
Jan 1 00:00:26 rc_service: waitting "stop_upnp" via udhcpc ...
Jan 1 00:00:27 rc_service: udhcpc 569:notify_rc stop_ntpc
Jan 1 00:00:27 rc_service: udhcpc 569:notify_rc start_ntpc
Jan 1 00:00:27 rc_service: waitting "stop_ntpc" via udhcpc ...
Jan 1 00:00:27 miniupnpd[626]: HTTP listening on port 45634
Jan 1 00:00:27 miniupnpd[626]: Listening for NAT-PMP traffic on port 5351
Jan 1 00:00:29 WAN Connection: WAN was restored.
Jan 1 00:00:38 dhcp client: bound 82.47.58.246 via 82.47.58.1 during 529175 seconds.
Feb 15 13:13:08 rc_service: ntp 629:notify_rc restart_upnp
Feb 15 13:13:08 miniupnpd[626]: received signal 15, good-bye
Feb 15 13:13:08 rc_service: ntp 629:notify_rc restart_diskmon
Feb 15 13:13:08 rc_service: waitting "restart_upnp" via ntp ...
Feb 15 13:13:08 miniupnpd[645]: HTTP listening on port 52431
Feb 15 13:13:08 miniupnpd[645]: Listening for NAT-PMP traffic on port 5351
Feb 15 13:13:10 disk monitor: be idle
Feb 15 13:17:40 miniupnpd[645]: sendto(udp): Operation not permitted
Feb 15 13:22:34 miniupnpd[645]: sendto(udp): Operation not permitted
 
Last edited:

RMerlin

Asuswrt-Merlin dev
That line here:

Code:
Feb 14 20:15:39 rc_service: httpd 513:notify_rc start_webs_update
Seem to indicate you had just started a firmware update, which would explain the reboot that occurred right after that.
 

AllTimeMitch

New Around Here
That line here:

Code:
Feb 14 20:15:39 rc_service: httpd 513:notify_rc start_webs_update
Seem to indicate you had just started a firmware update, which would explain the reboot that occurred right after that.
Thanks, RMerlin for the answer.

It's strange that the line is there. Whenever I perform a firmware update, I always reset the router back to factory defaults so it shouldn't show up in the system log that a firmware update has been attempted. Right?

I've since change the firmware to your latest build and it seems stable and has not reset once. I'll keep an eye on it and let you know how it gets on in a couple of days.

Cheers,
- Mitch
 

CoolDuckie

New Around Here
Hello all,

Just wanted to query this with anyone who owns one of these routers or a similar one. Occasionally the router seems to restart itself, I've only noticed as the uplink time is very small. I've checked other devices in the home to see if I had a power cut and I haven't. Is this normal?...
No, I have this problem after updating to the latest firmware. Never saw it before.

CD
 

TSloper

Occasional Visitor
There is definitely an issue with the latest firmware release relative to reboots. I upgraded, reset to default values, and reconfigured two days ago. While trying to watch AppleTV last night it stopped streaming twice. I went into the log this morning and found the router had rebooted multiple times since last night. There is nothing in the log as to why it is restarting.

I've reverted back to the prior version and no more reboots.
 

salieri

Occasional Visitor
Same Issue

I'm experiencing the same issue as well. I'm noticing the router reboots itself daily. Here is the latest log:

Feb 24 20:19:21 rc_service: ntp 842:notify_rc restart_upnp
Feb 24 20:19:21 rc_service: ntp 842:notify_rc restart_diskmon
Feb 24 20:19:21 rc_service: waitting "restart_upnp" via ntp ...
Feb 24 20:19:21 miniupnpd[835]: received signal 15, good-bye
Feb 24 20:19:21 miniupnpd[864]: HTTP listening on port 38604
Feb 24 20:19:21 miniupnpd[864]: Listening for NAT-PMP traffic on port 5351
Feb 24 20:19:23 disk monitor: be idle
Feb 24 20:19:24 rc_service: hotplug 790:notify_rc restart_nasapps
Feb 24 20:19:25 iTunes: daemon is stoped
Feb 24 20:19:25 FTP Server: daemon is stoped
Feb 24 20:19:26 Samba Server: smb daemon is stoped
Feb 24 20:19:26 kernel: gro disabled
Feb 24 20:19:26 Timemachine: daemon is stoped
Feb 24 20:19:26 kernel: gro enabled with interval 2
Feb 24 20:19:27 Samba Server: daemon is started
 

pille

New Around Here
same Firmware issues / rebooting probs on 3.0.0.4.374_4561

same rebooting probs here with my asus rt ac68u on fimrware 3.0.0.4.374_4561. It's horrible cause i'm using dlna via NAS via WLAN and the interrupts /reboots of the router are an absolute nogo!


Jan 1 01:00:15 kernel: Build_for__Asus_RT-AC56U_k2.6.36_2013-11-07_lke_8.9.0_r219253_b22
Jan 1 01:00:15 kernel: xhci_hcd 0000:00:0b.0: Failed to enable MSI-X
Jan 1 01:00:15 kernel: xhci_hcd 0000:00:0b.0: failed to allocate MSI entry
Jan 1 01:00:15 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values
Jan 1 01:00:15 syslog: module proxyarp not found in modules.dep
Jan 1 01:00:16 stop_nat_rules: apply the redirect_rules!
Jan 1 01:00:16 WAN Connection: Detected that the WAN Connection Type was PPPoE. But the PPPoE Setting was not complete.
Jan 1 01:00:16 RT-AC68U: start httpd
Jan 1 01:00:17 disk monitor: be idle
Jan 1 01:00:17 miniupnpd[544]: HTTP listening on port 33738
Jan 1 01:00:17 miniupnpd[544]: Listening for NAT-PMP traffic on port 5351
Jan 1 01:00:17 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 1 01:00:17 syslog: Generating SSL certificate...
Jan 1 01:00:18 miniupnpd[544]: received signal 15, good-bye
Jan 1 01:00:18 miniupnpd[594]: HTTP listening on port 50733
Jan 1 01:00:18 miniupnpd[594]: Listening for NAT-PMP traffic on port 5351
Jan 1 01:00:21 WAN Connection: WAN was restored.
Feb 25 16:18:26 rc_service: ntp 517:notify_rc restart_upnp
Feb 25 16:18:26 rc_service: ntp 517:notify_rc restart_diskmon
Feb 25 16:18:26 rc_service: waitting "restart_upnp" via ntp ...
Feb 25 16:18:26 miniupnpd[594]: received signal 15, good-bye
Feb 25 16:18:26 miniupnpd[647]: HTTP listening on port 47203
Feb 25 16:18:26 miniupnpd[647]: Listening for NAT-PMP traffic on port 5351
Feb 25 16:18:27 disk monitor: be idle
Jan 1 01:00:13 syslogd started: BusyBox v1.17.4
Jan 1 01:00:13 kernel: klogd started: BusyBox v1.17.4 (2014-02-21 13:09:50 CST)
Jan 1 01:00:13 kernel: Linux version 2.6.36.4brcmarm ([email protected]) (gcc version 4.5.3

just opened a case on asus support with all the logs...will reply if i got an answer

regards
 
Last edited:

pille

New Around Here
support from asus forced me to do the "reset to factory defaults" but the problem stillexists. My wachting on the problem is that if i view a movie via connected NAS from the Asus Router via Ethernet (TV)...there's no problem. If i start to watch a movie or something else via dlna via WLAN (Ipad,Iphone or PC (connected with a WLAN Media Bridge)) the rebooting procedure of the router begins. will give that info to official support. But i also watched, that is not only if i stream data via WLAN on the WLAN devices via dlna. Also if i download via http or normal surfin' in the web via WLAN.

regards
 
Last edited:

salieri

Occasional Visitor
Thank you for posting this pille, I got the same response from Asus tech support too and it's not working for me either. I'm going to update my support request and indicate that as well.
 

Elvis7

Occasional Visitor
my ac68u is also rebooting on its own, its very annoying and it does this about 4 times a day, it does it firmware 3.0.0.4.374_4561 and 3.0.0.4.374.4422 .

so im going back to firmware 3.0.0.4.374.583...
 

Ooook

New Around Here
Same problem here, the router reboots every night. :(
Firmware:3.0.0.4.374_4561 and I've restored settings to factory default after the install.

I noticed something strange in the log : I log both dropped and accepted packets (approx. 100 lines an hour) and it stops recording them 3 hours before the reboot :confused: .
22h24 : last log before reboot
01h28 : reboot
01h30 : back online

Code:
[B]Mar  1 22:24:13 [/B]kernel: ACCEPT IN=ppp0 OUT=br0 SRC=78.225.50.82 DST=192.168.1.99 LEN=64 TOS=0x00 PREC=0x00 TTL=50 ID=40696 DF PROTO=TCP SPT=56974 DPT=5001 SEQ=4283383966 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405AC010303040101080A07B88D820000000004020000) 
Jan  1 01:00:12 [B]syslogd started: BusyBox v1.17.4[/B]
Jan  1 01:00:12 kernel: klogd started: BusyBox v1.17.4 (2014-02-20 18:49:12 CST)
Jan  1 01:00:12 kernel: Linux version 2.6.36.4brcmarm ([email protected]) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Thu Feb 20 18:55:38 CST 2014
Jan  1 01:00:12 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
Jan  1 01:00:12 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Jan  1 01:00:12 kernel: Machine: Northstar Prototype
Jan  1 01:00:12 kernel: Ignoring unrecognised tag 0x00000000
Jan  1 01:00:12 kernel: Memory policy: ECC disabled, Data cache writealloc
Jan  1 01:00:12 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60416
Jan  1 01:00:12 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
Jan  1 01:00:12 kernel: Memory: 255508k/255508k available, 6636k reserved, 0K highmem
Jan  1 01:00:12 syslog: module ledtrig-usbdev not found in modules.dep
Jan  1 01:00:12 syslog: module leds-usb not found in modules.dep
Jan  1 01:00:12 kernel: Virtual kernel memory layout:
Jan  1 01:00:12 kernel:     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Jan  1 01:00:12 kernel:     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
Jan  1 01:00:12 kernel:     DMA     : 0xf7e00000 - 0xffe00000   ( 128 MB)
Jan  1 01:00:12 kernel:     vmalloc : 0xd0800000 - 0xf0000000   ( 504 MB)
Jan  1 01:00:12 kernel:     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
Jan  1 01:00:12 kernel:     modules : 0xbf000000 - 0xc0000000   (  16 MB)
Jan  1 01:00:12 kernel:       .init : 0xc0008000 - 0xc003d000   ( 212 kB)
Jan  1 01:00:12 kernel:       .text : 0xc003d000 - 0xc03ab000   (3512 kB)
Jan  1 01:00:12 kernel:       .data : 0xc03c2000 - 0xc03e4f40   ( 140 kB)
Jan  1 01:00:12 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored.
Jan  1 01:00:12 kernel: Mount-cache hash table entries: 512
Jan  1 01:00:12 kernel: CPU1: Booted secondary processor
Jan  1 01:00:12 kernel: Found a AMD NAND flash:
Jan  1 01:00:12 kernel: Total size:  128MB
Jan  1 01:00:12 kernel: Block size:  128KB
Jan  1 01:00:12 kernel: Page Size:   2048B
Jan  1 01:00:12 kernel: OOB Size:    64B
Jan  1 01:00:12 kernel: Sector size: 512B
Jan  1 01:00:12 kernel: Spare size:  16B
Jan  1 01:00:12 kernel: ECC level:   8 (8-bit)
Jan  1 01:00:12 kernel: Device ID: 0x 1 0xf1 0x 0 0x1d 0x 1 0xf1
Jan  1 01:00:12 kernel: bio: create slab <bio-0> at 0
Jan  1 01:00:12 kernel: PCI: no core
Jan  1 01:00:12 kernel: PCI: no core
Jan  1 01:00:13 kernel: PCI: Fixing up bus 0
Jan  1 01:00:13 kernel: PCI: Fixing up bus 0
Jan  1 01:00:13 kernel: PCI: Fixing up bus 1
Jan  1 01:00:13 syslog: module vfat not found in modules.dep
Jan  1 01:00:13 kernel: PCI: Fixing up bus 0
Jan  1 01:00:13 kernel: PCI: Fixing up bus 2
Jan  1 01:00:13 kernel: VFS: Disk quotas dquot_6.5.2
Jan  1 01:00:13 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan  1 01:00:13 kernel: pflash: found no supported devices
Jan  1 01:00:13 kernel: bcmsflash: found no supported devices
Jan  1 01:00:13 kernel: Boot partition size = 524288(0x80000)
Jan  1 01:00:13 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
Jan  1 01:00:13 kernel: nflash: squash filesystem with lzma found at block 28
Jan  1 01:00:13 kernel: Creating 4 MTD partitions on "nflash":
Jan  1 01:00:13 kernel: 0x000000000000-0x000000080000 : "boot"
Jan  1 01:00:13 kernel: 0x000000080000-0x000000200000 : "nvram"
Jan  1 01:00:13 kernel: 0x000000200000-0x000002000000 : "linux"
Jan  1 01:00:13 kernel: 0x00000039e7d4-0x000002000000 : "rootfs"
Jan  1 01:00:13 kernel: === PPTP init ===
Jan  1 01:00:13 kernel: Registering the dns_resolver key type
Jan  1 01:00:13 kernel: Spare area=64 eccbytes 56, ecc bytes located at:
Jan  1 01: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
Jan  1 01:00:13 kernel: Available 7 bytes at (off,len):
Jan  1 01:00:13 kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0) 
Jan  1 01:00:13 kernel: Bad eraseblock 367 at 0x000002de0000
Jan  1 01:00:13 kernel: Options: NO_AUTOINCR,NO_READRDY,BBT_SCAN2NDPAGE,
Jan  1 01:00:13 kernel: Creating 1 MTD partitions on "brcmnand":
Jan  1 01:00:13 kernel: 0x000002000000-0x000008000000 : "brcmnand"
Jan  1 01:00:13 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
Jan  1 01:00:13 kernel: ctf: module license 'Proprietary' taints kernel.
Jan  1 01:00:13 kernel: Disabling lock debugging due to kernel taint
Jan  1 01:00:13 kernel: et_module_init: passivemode set to 0x0
Jan  1 01:00:13 kernel: et_module_init: txworkq set to 0x1
Jan  1 01:00:13 kernel: et_module_init: et_txq_thresh set to 0x400
Jan  1 01:00:13 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.73 (r448163)
Jan  1 01:00:13 kernel: wl_module_init: passivemode set to 0x0
Jan  1 01:00:13 kernel: wl_module_init: txworkq set to 0x1
Jan  1 01:00:13 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.73 (r448163)
Jan  1 01:00:13 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.73 (r448163)
Jan  1 01:00:13 kernel: Empty flash at 0x037d9158 ends at 0x037d9800
Jan  1 01:00:13 kernel: JFFS2 notice: (332) check_node_data: wrong data CRC in data node at 0x04234648: read 0x689b482d, calculated 0x4de064f3.
Jan  1 01:00:13 kernel: SCSI subsystem initialized
Jan  1 01:00:13 kernel: jnl: driver (lke_8.9.0, Feb 20 2014 19:46:43, LBD=ON) loaded at bf5e6000
Jan  1 01:00:13 kernel: ufsd:: trace mask set to 0000000f
Jan  1 01:00:13 kernel: ufsd: driver (lke_8.9.0 lke_8.9.0_r219253_b22, LBD=ON, delalloc, acl, ioctl, ugm, sd(1), wb, tr) loaded at bf5f3000
Jan  1 01:00:13 kernel: NTFS support included
Jan  1 01:00:13 kernel: Hfs+/HfsJ support included
Jan  1 01:00:13 kernel: optimized: speed
Jan  1 01:00:13 kernel: Build_for__Asus_RT-AC56U_k2.6.36_2013-11-07_lke_8.9.0_r219253_b22
Jan  1 01:00:13 kernel: xhci_hcd 0000:00:0b.0: Failed to enable MSI-X
Jan  1 01:00:13 kernel: xhci_hcd 0000:00:0b.0: failed to allocate MSI entry
Jan  1 01:00:13 kernel: usb usb1: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
Jan  1 01:00:14 syslog: module proxyarp not found in modules.dep
Jan  1 01:00:15 stop_nat_rules: apply the redirect_rules!
Jan  1 01:00:15 WAN Connection: Fail to connect with some issues.
Jan  1 01:00:15 RT-AC68U: start httpd
Jan  1 01:00:16 syslog: Generating SSL certificate...
Jan  1 01:00:21 disk monitor: be idle
Jan  1 01:00:30 pppd[567]: pppd 2.4.5 started by admin, uid 0
Jan  1 01:00:31 pppd[567]: Connected to XX:XX:XX:XX:XX:XX via interface vlan835
Jan  1 01:00:31 pppd[567]: Connect: ppp0 <--> vlan835
Jan  1 01:00:31 pppd[567]: CHAP authentication failed
Jan  1 01:00:31 pppd[567]: Connection terminated.
Jan  1 01:00:42 pppd[567]: Connected to XX:XX:XX:XX:XX:XX via interface vlan835
[B][x 8 times][/B]
Jan  1 01:02:15 pppd[567]: Connect: ppp0 <--> vlan835
Jan  1 01:02:15 pppd[567]: CHAP authentication succeeded
Jan  1 01:02:15 pppd[567]: peer from calling number XX:XX:XX:XX:XX:XX authorized
Jan  1 01:02:15 pppd[567]: local  IP address XXX.XXX.XXX.XXX
Jan  1 01:02:15 pppd[567]: remote IP address XXX.XXX.XXX.XXX
Jan  1 01:02:15 pppd[567]: primary   DNS address XXX.XXX.XXX.XXX
Jan  1 01:02:15 pppd[567]: secondary DNS address XXX.XXX.XXX.XXX
Jan  1 01:02:16 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_vlan835)!
Jan  1 01:02:16 WAN Connection: WAN was restored.
Jan  1 01:02:16 rc_service: ip-up 688:notify_rc stop_upnp
Jan  1 01:02:16 rc_service: ip-up 688:notify_rc start_upnp
Jan  1 01:02:16 rc_service: waitting "stop_upnp" via ip-up ...
Jan  1 01:02:17 ddns: clear ddns cache file for server/hostname change
Jan  1 01:02:18 ddns update: ez-ipupdate: starting...
Jan  1 01:02:18 ddns update: connected to members.dyndns.org (XXX.XXX.XXX.XXX) on port 80.
Jan  1 01:02:18 ddns update: request successful
Jan  1 01:02:18 ddns update: asusddns_update: 0
Jan  1 01:02:18 ddns: ddns update ok
Jan  1 01:02:18 rc_service: ip-up 688:notify_rc stop_ntpc
Jan  1 01:02:18 rc_service: ip-up 688:notify_rc start_ntpc
Jan  1 01:02:18 rc_service: waitting "stop_ntpc" via ip-up ...
Mar  2 01:30:50 rc_service: ntp 740:notify_rc restart_upnp
Mar  2 01:30:50 rc_service: ntp 740:notify_rc restart_diskmon
Mar  2 01:30:50 rc_service: waitting "restart_upnp" via ntp ...
Mar  2 01:30:52 disk monitor: be idle
[B]Mar  2 01:31:30[/B] kernel: DROP IN=ppp0 OUT= MAC= SRC=XXX.XXX.XXX.XXX DST=XXX.XXX.XXX.XXX LEN=60 TOS=0x00 PREC=0x00 TTL=54 ID=60376 DF PROTO=TCP SPT=36314 DPT=51136 SEQ=795458930 ACK=0 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405AC0402080A0AC156AA0000000001030304)
 

salieri

Occasional Visitor
Not making much progress getting this issue reported. Now the tech at ASUS is telling me I should return my router. I downgraded 2 firmware versions from the latest (downgrade to: 3.0.0.4.374.583) and the behavior has stopped. Going to try and note that...hopefully they'll identify this as a bug and fix it.
 

hjogi

New Around Here
Not making much progress getting this issue reported. Now the tech at ASUS is telling me I should return my router. I downgraded 2 firmware versions from the latest (downgrade to: 3.0.0.4.374.583) and the behavior has stopped. Going to try and note that...hopefully they'll identify this as a bug and fix it.
why don't you consider to install the merlin firmware. I solve this problem yesterday evening doing it!
 

pille

New Around Here
sorry but why i must fix errors/problems as a consumer with a custom firmware ? that's not make sense to me and i feel like a beta tester atm. i have tested and tried many of the instructions given to my by the Asus support but the problem is the firmware and must be solved by Asus themselves. I have paid a lot of money for the rt68u and the solution can't be to install a custom firmware!

after i've contacted the Asus support again, got no answer after a week.
That's frustating to buy such a powerful and expensive product and after one firmware installation the horror begins...


but i must say the reboots after setting to default become more less...max 2-3 times a day.

regards
 

salieri

Occasional Visitor
The more people that step up that have this issue and report it to Asus, the faster this is going to get resolved. I'd suggest mentioning this forum topic when you put in your support request. Pille you're not alone, I've been trying as well. Here's my latest progress:

---------- Forwarded message ----------
From: joe1_song <[email protected]>
Date: Wed, Mar 5, 2014 at 10:24 PM
Subject: Re:Re:Re:Re:Re:<TSD> Wireless RT-AC68U [ID=RWTM2014030418156303-387]

Dear Customer,

Thank you for contacting ASUS Customer Service.
My name is Joe and it is my pleasure to help you with your problem.

Thank you for your feedback. Now I will help you update the issue to my supervior. And we will check if there is the bug in it. If it is turly a bug, we will fix it in the new firmware in the near future. Thank you.

Welcome to refer Troubleshooting & FAQ for ASUS products in ASUS website:
http://support.asus.com/servicehome.aspx?SLanguage=en

If you continue to experience issues in the future, please do not hesitate to contact us.

An email survey will be sent to you within the next 5 days. Please be sure to rate the service I provided to you today.


Best Regards,
Joe
ASUS Product Support Team

---------- Original Message ----------
Sent : 2014/3/3 17:08:20
To : "[email protected]"
Subject : Re:Re:Re:Re:<TSD> Wireless RT-AC68U [ID=RWTM20140228723556105-740]

[CASEID=WTM2014030418156303]

Hi Joe,

Please note that I am NOT the only one having this issue. Please see this thread:
http://forums.smallnetbuilder.com/showthread.php?t=15502

Just to let you know, the "reboot issue" started happening on versions:
3.0.0.4.374.4561 AND 3.0.0.4.374.4422.

I''ve downgraded to firmware 3.0.0.4.374.583 and the rebooting issue STOPPED.

There seems to be a problem with the TWO firmwares I''ve noted. Please advise...
 

DaveB

Occasional Visitor
Same here...

Exactly the same issue-mysterious boots-ASUS told me too I should return my router...I've downgraded the firmware to xxx4583...lets see what happens
Dave

Update:
Bingo - I've downgraded to firmware 3.0.0.4.374.583 and the rebooting issue stopped (3 days now-no boots). Have contacted ASUS Support again here in Europe-lets see what happens.
 
Last edited:

ThaGG

New Around Here
Hey guys,

Totally new to the forum, but I bought the AC68U one week ago and I am also experiencing random reboots on the latest two firmware versions. Downgraded and the problem stopped.

My question is whether the reboots happen on every AC68U router and is firmware related, or that it happens on some AC68U devices. I need to know this, because I have three days left to return the router and ask for a new model without any costs. If it is device related, I might have more luck with a new model, but if it is firmware related, I can save myself a trip to the store, because it'll happen on a new device as well.

Thanks in advance!
 
Status
Not open for further replies.

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