Help..My AC66R router is rebooting continuously

[sunghoon5192]

My router is rebooting continuously

All LED signs are continuously lit,
Is broken into the internal network and external network.

Above symptoms occur repeatedly.

Please Help me!.

Attach the log and the symptoms of my videos.

Video link : http://youtu.be/VXHd0JB5ZYk
System Log
Jan 1 09:00:08 syslogd started: BusyBox v1.17.4
Jan 1 09:00:08 kernel: klogd started: BusyBox v1.17.4 (2013-10-03 07:13:28 CST)
Jan 1 09:00:08 kernel: Linux version 2.6.22.19 (root@asus) (gcc version 4.2.4) #1 Thu Oct 3 07:16:35 CST 2013
Jan 1 09:00:08 kernel: CPU revision is: 00019749
Jan 1 09:00:08 kernel: Found an ST compatible serial flash with 32 64KB blocks; total size 2MB
Jan 1 09:00:08 kernel: Determined physical RAM map:
Jan 1 09:00:08 kernel: memory: 07fff000 @ 00000000 (usable)
Jan 1 09:00:08 kernel: memory: 08000000 @ 87fff000 (usable)
Jan 1 09:00:08 kernel: Built 1 zonelists. Total pages: 585216
Jan 1 09:00:08 kernel: Kernel command line: root=/dev/mtdblock3 console=ttyS0,115200 init=/sbin/preinit
Jan 1 09:00:08 kernel: Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Jan 1 09:00:08 kernel: Primary data cache 32kB, 4-way, linesize 32 bytes.
Jan 1 09:00:08 kernel: PID hash table entries: 2048 (order: 11, 8192 bytes)
Jan 1 09:00:08 kernel: CPU: BCM5300 rev 1 pkg 0 at 600 MHz
Jan 1 09:00:08 kernel: Using 300.000 MHz high precision timer.
Jan 1 09:00:08 syslog: module ledtrig-usbdev not found in modules.dep
Jan 1 09:00:08 syslog: module leds-usb not found in modules.dep
Jan 1 09:00:08 kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Jan 1 09:00:08 kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Jan 1 09:00:08 kernel: Mount-cache hash table entries: 512
Jan 1 09:00:08 kernel: PCI: Initializing host
Jan 1 09:00:08 kernel: PCI: Reset RC
Jan 1 09:00:08 kernel: PCI: Initializing host
Jan 1 09:00:08 kernel: PCI: Reset RC
Jan 1 09:00:08 kernel: PCI: Fixing up bus 0
Jan 1 09:00:08 kernel: PCI/PCIe coreunit 0 is set to bus 1.
Jan 1 09:00:08 kernel: PCI: Fixing up bridge
Jan 1 09:00:08 kernel: PCI: Fixing up bridge
Jan 1 09:00:09 kernel: PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
Jan 1 09:00:09 kernel: PCI: Fixing up bus 1
Jan 1 09:00:09 kernel: PCI/PCIe coreunit 1 is set to bus 2.
Jan 1 09:00:09 kernel: PCI: Fixing up bridge
Jan 1 09:00:09 kernel: PCI: Fixing up bridge
Jan 1 09:00:09 kernel: PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
Jan 1 09:00:09 kernel: PCI: Fixing up bus 2
Jan 1 09:00:09 kernel: IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan 1 09:00:09 kernel: TCP established hash table entries: 16384 (order: 5, 131072 bytes)
Jan 1 09:00:09 kernel: TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
Jan 1 09:00:09 kernel: highmem bounce pool size: 64 pages
Jan 1 09:00:09 kernel: pflash: found no supported devices
Jan 1 09:00:09 kernel: Boot partition size = 262144(0x40000)
Jan 1 09:00:09 kernel: Creating 2 MTD partitions on "sflash":
Jan 1 09:00:09 kernel: 0x00000000-0x00040000 : "pmon"
Jan 1 09:00:09 kernel: 0x001f0000-0x00200000 : "nvram"
Jan 1 09:00:09 kernel: Found a Samsung NAND flash with 2048B pages or 128KB blocks; total size 128MB
Jan 1 09:00:09 kernel: lookup_nflash_rootfs_offset: offset = 0x0
Jan 1 09:00:09 kernel: nflash: squash filesystem with lzma found at block 9
Jan 1 09:00:09 kernel: Creating 4 MTD partitions on "nflash":
Jan 1 09:00:09 kernel: 0x00000000-0x02000000 : "linux"
Jan 1 09:00:09 kernel: 0x00132ea0-0x02000000 : "rootfs"
Jan 1 09:00:09 kernel: 0x04000000-0x06000000 : "linux2"
Jan 1 09:00:09 kernel: 0x04132ea0-0x06000000 : "rootfs2"
Jan 1 09:00:09 kernel: Creating 3 MTD partitions on "brcmnand":
Jan 1 09:00:09 kernel: 0x00000000-0x02000000 : "trx"
Jan 1 09:00:09 kernel: 0x02000000-0x04000000 : "jffs2"
Jan 1 09:00:09 kernel: 0x04000000-0x07f00000 : "brcmnand"
Jan 1 09:00:09 kernel: dev_nvram_init: _nvram_init
Jan 1 09:00:09 kernel: _nvram_init: allocat size= 65536
Jan 1 09:00:09 kernel: u32 classifier
Jan 1 09:00:09 kernel: OLD policer on
Jan 1 09:00:09 kernel: Netfilter messages via NETLINK v0.30.
Jan 1 09:00:09 kernel: nf_conntrack version 0.5.0 (2048 buckets, 16384 max)
Jan 1 09:00:09 kernel: ipt_time loading
Jan 1 09:00:09 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 09:00:09 kernel: net/ipv4/netfilter/tomato_ct.c [Oct 3 2013 07:15:57]
Jan 1 09:00:09 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 09:00:09 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 09:00:09 kernel: Warning: unable to open an initial console.
Jan 1 09:00:09 kernel: Failed to execute /sbin/preinit. Attempting defaults...
Jan 1 09:00:09 kernel: ctf: module license 'Proprietary' taints kernel.
Jan 1 09:00:09 kernel: et_module_init: passivemode set to 0x0
Jan 1 09:00:09 kernel: et_module_init: et_txq_thresh set to 0x400
Jan 1 09:00:09 kernel: bcm_robo_enable_switch: EEE is disabled
Jan 1 09:00:09 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.30.102.9 (r366174)
Jan 1 09:00:09 kernel: PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
Jan 1 09:00:09 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.102.9 (r366174)
Jan 1 09:00:09 kernel: PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
Jan 1 09:00:09 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.102.9 (r366174)
Jan 1 09:00:09 kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 09:00:09 kernel: SCSI subsystem initialized
Jan 1 09:00:09 kernel: ufsd: driver (8.6 U86_r187446_b122, LBD=ON, acl, ioctl, rwm, ws, sd) loaded at c0209000
Jan 1 09:00:09 kernel: NTFS (with native replay) support included
Jan 1 09:00:09 kernel: optimized: speed
Jan 1 09:00:09 kernel: Build_for__asus_n66u_2011-10-27_U86_r187446_b122
Jan 1 09:00:10 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Jan 1 09:00:11 stop_nat_rules: apply the redirect_rules!
Jan 1 09:00:11 WAN Connection: ISP's DHCP did not function properly.
Jan 1 09:00:11 RT-AC66R: start httpd
Jan 1 09:00:16 disk monitor: be idle
Jan 1 09:00:16 miniupnpd[335]: HTTP listening on port 58654
Jan 1 09:00:16 miniupnpd[335]: Listening for NAT-PMP traffic on port 5351
Jan 1 09:00:19 kernel: wlc_dump_aggfifo:
Jan 1 09:00:19 kernel: framerdy 0x2 bmccmd 7 framecnt 1024
Jan 1 09:00:19 kernel: AQM agg params 0x3f maxlen hi/lo 0x0 0xffff minlen 0x0 adjlen 0x0
Jan 1 09:00:19 kernel: AQM agg results 0xa000 len hi/lo: 0x0 0x0 BAbitmap(0-3) 0 0 0 0
Jan 1 09:00:22 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 1 09:00:23 kernel: nf_conntrack_rtsp v0.6.21 loading
Jan 1 09:00:23 kernel: nf_nat_rtsp v0.6.21 loading
Jan 1 09:00:23 rc_service: udhcpc 342:notify_rc stop_upnp
Jan 1 09:00:23 miniupnpd[335]: received signal 15, good-bye
Jan 1 09:00:23 rc_service: udhcpc 342:notify_rc start_upnp
Jan 1 09:00:23 miniupnpd[398]: HTTP listening on port 58022
Jan 1 09:00:23 miniupnpd[398]: Listening for NAT-PMP traffic on port 5351
Jan 1 09:00:23 rc_service: udhcpc 342:notify_rc stop_ntpc
Jan 1 09:00:23 rc_service: udhcpc 342:notify_rc start_ntpc
Jan 1 09:00:23 rc_service: start_ntpc is waitting stop_ntpc...
Jan 1 09:00:24 dhcp client: bound 59.12.52.223 via 59.12.52.1 during 3600 seconds.
Jan 1 09:00:28 WAN Connection: WAN was restored.
Jan 12 00:08:19 rc_service: ntp 399:notify_rc restart_upnp
Jan 12 00:08:19 miniupnpd[398]: received signal 15, good-bye
Jan 12 00:08:19 miniupnpd[408]: HTTP listening on port 54064
Jan 12 00:08:19 miniupnpd[408]: Listening for NAT-PMP traffic on port 5351
Jan 12 00:08:19 rc_service: ntp 399:notify_rc restart_diskmon
Jan 12 00:08:19 disk monitor: be idle

 

[L&LD]

What firmware are you running? Do you have any USB devices attached? When did it start doing this? Was there a power outage?

Much more info is needed.

 

[sinshiva]

i was watching your video and notice you spent a lot of time playing with IPTV settings... can you tell us more about your internet connection and how you are trying to use your router? does it work correctly for internet with the IPTV set to default values;

ISP Profile: None

enable multicast: disable
enable efficient multicast: disable

 

[sunghoon5192]

Power is supplied to the stable. The firmware is operating normally in both.
After purchasing the product, and be from this anomalous behavior. Merlin official firmware and the firmware is all the same symptoms. USB devices are not connected to either state.
And all settings are disabled by IPTV.

Network Structure
WAN -> IPTV -> Routers -> Wired Desktop

While writing this article, I have no connection to the router does not even have to repeat the reboot.

 

[sinshiva]

hey

can you rearrange your network like this;

WAN > AC66 > IPTV && LAN port of extra routers

forgive me, i'm not familiar with IPTV and i may have misinterpreted you

 

[sunghoon5192]

Still have the same symptoms. IPTV does not properly broken phenomenon can also

 

[sinshiva]

yes, i assumed your IPTV settings would need to be properly configured on the ac66; what is your internet connection and firmware? have you updated the firmware recently?

 

[sunghoon5192]

After I received the product passes through a simple network test it after the firmware update.
But the symptoms are the same since the first firmware update.

ASUS RT-AC66R Firmware version 3.0.0.4.374.979
ASUS RT-AC66R Firmware Version 3.0.0.4.374.726
ASUS RT-AC66R Firmware version 3.0.0.4.374.130
ASUS RT-AC66R Firmware version 3.0.0.4.372

Symptoms of the same on all versions.

 

[RMerlin]

Try disabling HW acceleration under LAN -> Switch Control. If your router still randomly reboots itself, I would recommend having it replaced under warranty, as it's likely to be a hardware defect.

 

[TonyH]

OP did not mention whether it was working normal at the beginning or acting up like this out of box. Didn't even mention he tried the reset button. On a whim, I'd try another wall wart. Then time to decide for warranty coverage. Looking at the user id.(his name? looks like Korean, are you Korean?)

 

[sunghoon5192]

Yes I am Korean^^

 

[TonyH]

Try disabling HW acceleration under LAN -> Switch Control. If your router still randomly reboots itself, I would recommend having it replaced under warranty, as it's likely to be a hardware defect.

Hi, Merlin
Happy new year from Calgary AB. I conversed with OP in Korean via PM. The router worked alright out of box but after he updated f/w with yours, this
thing started. Maybe update was not really completed? I suggested few things to try first with recovery utility. There utility power being on 220V AC, I don't know how well wall warts work in higher voltage even if it is universal input voltage type. I have a habit of plugging in my own heavier duty ones. I don't use OEM wall warts.