Others have reported that this router is pretty sensitive to the quality of the cable. Somebody actually returned 6 units thinking they had a bad router before using the included Ethernet cable which resolved his/her issues.
You've probably tried this, but just thought I'd share.
Hi,
I think those issues were with the WAN port, where mine is with no1 LAN port
Cables have been changed, different PC used and issue persists. Noticed on the last connection issue when link rate was negotiated and the router crashed that there was a CPU stall:
Jul 11 11:28:38 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jul 11 11:28:43 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 100 mbps full duplex
Jul 11 11:28:57 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
Jul 11 11:29:48 kernel: INFO: rcu_preempt self-detected stall on CPU { 0} (t=6001 jiffies g=114008 c=114007 q=11613)
Jul 11 11:29:48 kernel: rcu_preempt kthread starved for 6001 jiffies!
Jul 11 11:29:48 kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 2, t=6002 jiffies, g=114008, c=114007, q=11613)
Jul 11 11:29:48 kernel: Call trace:
Jul 11 11:29:48 kernel: [<ffffffc00008573c>] __switch_to+0x64/0x80
Jul 11 11:29:48 kernel: rcu_preempt kthread starved for 6002 jiffies!
Jul 11 11:29:48 kernel: Call trace:
Jul 11 11:29:48 kernel: [<ffffffc0000876d8>] dump_backtrace+0x0/0x150
Jul 11 11:29:48 kernel: [<ffffffc00008783c>] show_stack+0x14/0x20
Jul 11 11:29:48 kernel: [<ffffffc0000b7afc>] sched_show_task+0xa4/0x100
Jul 11 11:29:48 kernel: [<ffffffc0000bab28>] dump_cpu_task+0x40/0x50
Jul 11 11:29:48 kernel: [<ffffffc0000d5ce8>] rcu_dump_cpu_stacks+0xa0/0xf0
Jul 11 11:29:48 kernel: [<ffffffc0000d9c94>] rcu_check_callbacks+0x4bc/0x8b8
Jul 11 11:29:48 kernel: [<ffffffc0000dc3d4>] update_process_times+0x3c/0x70
Jul 11 11:29:48 kernel: [<ffffffc0000ea37c>] tick_nohz_handler+0xa4/0x108
Jul 11 11:29:48 kernel: [<ffffffc00036da78>] arch_timer_handler_phys+0x30/0x40
Jul 11 11:29:48 kernel: [<ffffffc0000d1c8c>] handle_percpu_devid_irq+0x7c/0xa0
Jul 11 11:29:48 kernel: [<ffffffc0000cd9c4>] generic_handle_irq+0x34/0x50
Jul 11 11:29:48 kernel: [<ffffffc0000cdcd4>] __handle_domain_irq+0x5c/0xb8
Jul 11 11:29:48 kernel: [<ffffffc000080c20>] gic_handle_irq+0x38/0x90
Jul 11 11:29:48 kernel: Exception stack(0xffffffc032a2f3a0 to 0xffffffc032a2f4c0)
Jul 11 11:29:48 kernel: f3a0: fc66ed48 ffffffbf 2e4069c0 ffffffc0 32a2f4e0 ffffffc0 004eab50 ffffffc0
Jul 11 11:29:48 kernel: f3c0: 80e9c70a 00000000 80e9c308 00000000 00000000 00000000 008fa1d0 ffffff80
Jul 11 11:29:48 kernel: f3e0: 0000788a 00000000 80666208 00000000 c57eec51 00000000 00000056 00000000
Jul 11 11:29:48 kernel: f400: 00000008 00000000 fffffee6 00000000 00000000 00000000 a7debb01 00000000
Jul 11 11:29:48 kernel: f420: 00caa000 ffffff80 00000000 00000000 00000000 00000000 00000000 00000000
Jul 11 11:29:48 kernel: f440: 00000001 00000000 00000003 00000000 0000001a 00000000 fc66ed48 ffffffbf
Jul 11 11:29:48 kernel: f460: 2e4069c0 ffffffc0 2e4069c0 ffffffc0 340d1800 ffffffc0 006e0a30 ffffffc0
Jul 11 11:29:48 kernel: f480: 006e0a20 ffffffc0 00000000 00000000 00000000 00000000 34023000 ffffffc0
Jul 11 11:29:48 kernel: f4a0: 2e406cc0 ffffffc0 32a2f4e0 ffffffc0 003b9e40 ffffffc0 32a2