What's new

ASUS RT-AC2900 crash frequently

bmn1

Regular Contributor
Hi everybody,
I have a RT-AC2900 (AC-86U) router with Merlin 384.17 and it is frequently rebooting automatically with this message:

May 5 07:05:10 kernel: xhci-hcd xhci-hcd.0: USB bus 1 deregistered
May 5 07:05:10 kernel: usb3 reseting..........
May 5 07:05:10 kernel: _ Reboot message ... _______________________________________________________
May 5 07:05:10 kernel: Unable to handle kernel paging request at virtual address ac0000000efpgd = ffffffc013ccf000[ac0000000ef] *pgd=0000000000000000, *pud=0000000000000000Internal error: Oops: 96000004 [#1] PREEMPT SMPCPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 4.1.27 #2Hardware name: Broadcom-v8A (DT)task: ffffffc0006ee380 ti: ffffffc0006dc000 task.ti: ffffffc0006dc000PC is at get_unique_tuple+0x424/0x568LR is at get_unique_tuple+0x30c/0x568pc : [<ffffffc00041ade4>] lr : [<ffffffc00041ac
May 5 07:05:10 kernel: 0000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 00000000959496b3 x3 : 0000000000000006 x2 : 0000000000000e00 x1 : 00000ac000000001 x0 : 00000ac0000000c9 Process swapper/0 (pid: 0, stack limit = 0xffffffc0006dc020)Modules linked in: usblp init_addr( (null) - (null)), core_addr(ffffffbffcabc000 - ffffffbffcabdfd8) thfsplus(O) init_addr( (null) - (null)), core_addr(ffffffbffca9a000 - ffffffbffcaa7054) tntfs(PO) init_addr( (
May 5 07:05:11 kernel: , core_addr(ffffffbffc947000 - ffffffbffc957a58) nf_nat_sip init_addr( (null) - (null)), core_addr(ffffffbffc940000 - ffffffbffc941980) nf_conntrack_sip init_addr( (null) - (null)), core_addr(ffffffbffc935000 - ffffffbffc937e80) nf_nat_h323 init_addr( (null) - (null)), core_addr(ffffffbffc92f000 - ffffffbffc9300d0) nf_conntrack_h323 init_addr( (null) - (null)), core_addr(ffffffbffc91d000 - ffffffbffc920a
May 5 07:05:11 kernel: 3b50) qmi_wwan init_addr( (null) - (null)), core_addr(ffffffbffc8f8000 - ffffffbffc8f8728) cdc_wdm init_addr( (null) - (null)), core_addr(ffffffbffc8f1000 - ffffffbffc8f28c8) cdc_ncm init_addr( (null) - (null)), core_addr(ffffffbffc8e7000 - ffffffbffc8e91e0) rndis_host init_addr( (null) - (null)), core_addr(ffffffbffc8e1000 - ffffffbffc8e1b10) cdc_ether init_addr( (null) - (null)), cor
May 5 07:05:11 kernel: ffffffbffc8a6164) mii init_addr( (null) - (null)), core_addr(ffffffbffc89e000 - ffffffbffc89eb70) xfrm_user init_addr( (null) - (null)), core_addr(ffffffbffc892000 - ffffffbffc8964f8) xfrm4_tunnel init_addr( (null) - (null)), core_addr(ffffffbffc88e000 - ffffffbffc88e170) ipcomp init_addr( (null) - (null)), core_addr(ffffffbffc88a000 - ffffffbffc88a380) esp4 init_addr( (null) - (null)
May 5 07:05:11 kernel: fffbffc83c000 - ffffffbffc83c890) ehci_hcd init_addr( (null) - (null)), core_addr(ffffffbffc82d000 - ffffffbffc8349a8) usbcore init_addr( (null) - (null)), core_addr(ffffffbffc7f0000 - ffffffbffc807ce0) usb_common init_addr( (null) - (null)), core_addr(ffffffbffc7ec000 - ffffffbffc7ec208) dhd init_addr( (null) - (null)), core_addr(ffffffbffc643000 - ffffffbffc67c3d8) dpsta(P) init_addr( (null) -
May 5 07:05:11 kernel: ddr(ffffffbffc59a000 - ffffffbffc59a818) bcmspu init_addr( (null) - (null)), core_addr(ffffffbffc582000 - ffffffbffc589910) bcmpdc init_addr( (null) - (null)), core_addr(ffffffbffc57b000 - ffffffbffc57c530) pwrmngtd(P) init_addr( (null) - (null)), core_addr(ffffffbffc577000 - ffffffbffc577540) bcmvlan(P) init_addr( (null) - (null)), core_addr(ffffffbffc551000 - ffffffbffc55fe10) wfd init_addr( (
May 5 07:05:11 kernel: (null)), core_addr(ffffffbffc33a000 - ffffffbffc34db0c) chipinfo(P) init_addr( (null) - (null)), core_addr(ffffffbffc336000 - ffffffbffc336134) rdpa_mw init_addr( (null) - (null)), core_addr(ffffffbffc32a000 - ffffffbffc32da28) rdpa(P) init_addr( (null) - (null)), core_addr(ffffffbffc17f000 - ffffffbffc1e03a0) rdpa_gpl_ext init_addr( (null) - (null)), core_addr(ffffffbffc17b000 - ffffffbffc17b0c
May 5 07:05:11 kernel: 6df400 ffffffc0 0041af80 ffffffc0f380: 00000000 00000000 0c17e1c8 ffffffc0 006df528 ffffffc0 13cc6000 ffffffc0f3a0: 6d8d7525 00000000 00000000 00000000 1909c340 ffffffc0 1f902000 00000000f3c0: 13cc6000 ffffffc0 1a9b6a4e ffffffc0 006df400 ffffffc0 0041af68 ffffffc0f3e0: 00000000 00000000 0c17e1c8 ffffffc0 006df528 ffffffc0 00475f88 ffffffc0f400: 006df4b0 ffffffc0 004809c0 ffffffc0 0c17e1c8 ffffffc0 11b2ca78 ffffffc0f420: 006df568 ffffffc0 13cc6000 ffffffc0 153db880 ffffffc0 0d01a
.....

May 5 07:05:12 kernel: ffffc000404904>] nf_iterate+0x94/0xa8[<ffffffc0004049c8>] nf_hook_slow+0xb0/0x160[<ffffffc000430f3c>] ip_output+0x12c/0x170[<ffffffc00042c3c4>] ip_forward_finish+0x6c/0x90[<ffffffc00042c794>] ip_forward+0x3ac/0x468[<ffffffc00042aa4c>] ip_rcv_finish+0x134/0x328[<ffffffc00042b120>] ip_rcv+0x2d8/0x3b8[<ffffffc0003bb310>] __netif_receive_skb_core+0x628/0xa40[<ffffffc0003be31c>] __netif_receive_skb+0x2c/0x88[<ffffffc0003be3b8>] netif_receive_skb_internal+0x40/0xc0[<ffffffc0003be448>]
May 5 07:05:12 kernel: 06dfd80 to 0xffffffc0006dfea0)fd80: 58dc0672 00013379 1ffd92f0 ffffffc0 006dfec0 ffffffc0 003721bc ffffffc0fda0: 58dc0672 00013379 52077e30 00307ee1 0005def5 00000000 13fffc47 00000000fdc0: 0407b1e4 00000000 00000018 00000000 43e27c3d 00300976 13d414a8 ffffffc0fde0: 006ee8a0 ffffffc0 006dfe70 ffffffc0 000789e8 00000000 0007a1f2 00000000fe00: 00000000 00000000 f6a24bf8 00000000 f6a25930 00000000 00000000 00000000fe20: 000f5c40 ffffffc0 00000000 00000000 00000000 00000000 58dc0672
May 5 07:05:12 kernel: e ]---Kernel panic - not syncing: Fatal exception in interrupt
May 5 07:05:12 kernel: ____________________________________________________________________________
May 5 07:05:12 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,202: Could not rdpa_ucast_ipv6_host_address_table_find^[[0m
May 5 07:05:12 kernel: device eth1 entered promiscuous mode
I have this problem in different version of Merlin firmware. I've already try to reset nvram and restore all the settings.

Do you have any idea of the reason?
If I well understood from the log the reboot (crash) reason is:
Code:
^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,202: Could not rdpa_ucast_ipv6_host_address_table_find^[[0m
 
Last edited:

Jack Yaz

Part of the Furniture
It sounds like you are restoring a backup of your settings after resetting, is that correct? If so, don't do that, re-configure things manually and see how it goes.
 

bmn1

Regular Contributor
It sounds like you are restoring a backup of your settings after resetting, is that correct? If so, don't do that, re-configure things manually and see how it goes.
It's correct. How you can know this?
There is a way to quickly import part of the settings? because I have hundreds of settings.

Thanks
 

OzarkEdge

Part of the Furniture
It's correct. How you can know this?
There is a way to quickly import part of the settings? because I have hundreds of settings.
You said 'restore all the settings'... that usually means you restored a saved configuration.

Reset the firmware and configure a minimal configuration from scratch to see if the router is stable. Then add necessary settings gradually over time... some feature you are using may be the culprit.

https://www.snbforums.com/threads/faq-nvram-and-factory-default-reset.22822/

OE
 

bmn1

Regular Contributor
I've followed your suggestion

but after two days I have another crash, In the last part of the log I see:
Code:
May  5 07:05:10 kernel: _ Reboot message ... _______________________________________________________
May  5 07:05:10 kernel: Unable to handle kernel paging request at virtual address dead0000000002eepgd = ffffffc012d8b000[dead0000000002ee] *pgd=0000000017059003, *pud=0000000017059003, *pmd=000000001515a003, *pte=0000000000000000Internal error: Oops: 96000004 [#1] PREEMPT SMPCPU: 0 PID: 0 Comm: swapper/0 Tainted: P           O    4.1.27 #2Hardware name: Broadcom-v8A (DT)task: ffffffc0006ee380 ti: ffffffc0006dc000 task.ti: ffffffc0006dc000PC is at get_unique_tuple+0x424/0x568LR is at get_unique_tuple+0x
May  5 07:05:11 kernel: ____________________________________________________________________________
May  5 07:05:11 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,202: Could not rdpa_ucast_ipv6_host_address_table_find^[[0m
I also checked and IPv6 is disabled.
It's a very annoying issue. I see that this problem was already present in the past for example:
https://www.snbforums.com/threads/r...urity-enhancements.16798/page-234#post-491399
https://www.snbforums.com/threads/kernel-panic-on-rt-ac86u-running-384-11.56537/
https://www.snbforums.com/threads/new-ac86u-bad-peb-a-problem.49205/#post-436614
 
Last edited:

bmn1

Regular Contributor
bump!
Anyone of the AC-RT86U user have this issue (crash every 2 days)?
Can I try to enable Firewall: Drop IPv6 neighbour solicitation broadcasts, can this setting help?
 

L&LD

Part of the Furniture
Non of the RT-AC86U's that I have set up for customers have the issues you're reporting.

What good will enabling that setting do, when you state that you have IPv6 disabled?

If you do a full M&M Config/Nuclear Reset and the router doesn't stay stable for you without any further customizations than what is suggested, it is time to replace or junk it if it is past the warranty for your region.

See my signature below for the link to the guides I suggest above.

The following link may also help too.

https://www.snbforums.com/threads/ax88-packet-loss.62891/#post-563326

When testing for stability, do not import any settings at all. Do not blindly copy any old settings manually or otherwise either, that you may have used previously. :)

HTH. :)
 

bmn1

Regular Contributor
L&LD,
thank you very much for your answer.
I've already followed but I've enabled some basic feature as custom-DDNS and VPN IPSEC.
I will try again to follow the procedure in your link without enabling any features for 2-3 days and I will post here the result.

Anyway I was just curious about understanding the log message, because seems related to IPv6 in such way, but I have IPv6 disabled...

Thanks again for your help
 
Last edited:

L&LD

Part of the Furniture
@bmn1, give a few hours for others to answer your question directly, but your routers issues seem very unique, to me. :)
 

JJohnson1988

Occasional Visitor
My 86U seems to be crashing periodically as well, though I'm not sure it's that specific error being logged. I'll check next time it happens. I have the suspicion that it's memory related, but I could be wrong.
 

bmn1

Regular Contributor
My 86U seems to be crashing periodically as well, though I'm not sure it's that specific error being logged. I'll check next time it happens. I have the suspicion that it's memory related, but I could be wrong.
Ok, you can update me in this post as soon as you have the log.
Anyway in my case is not memory related infact my free ram is more than 50% and also in flash memory I have space.
You can check as soon as you noticed the crash looking for "Reboot message" in the log.
 
Last edited:

JJohnson1988

Occasional Visitor
I just had another crash a few minutes ago (requires a manual reboot), but I'm checking the logs and I can't find any information related to the crash. Is there a specific file not being displayed in the admin UI that I need to run a cat or tail command on?

The crash happened in between this section of the log.

Code:
May 16 19:16:16 AC86U kernel: net_ratelimit: 42415 callbacks suppressed
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
May 16 19:16:16 AC86U kernel: br0: received packet on eth3 with own address as source address
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               May  4 22:05:11 syslogd started: BusyBox v1.25.1
May  4 22:05:11 kernel: klogd started: BusyBox v1.25.1 (2020-04-25 22:28:50 EDT)
May  4 22:05:11 kernel: Booting Linux on physical CPU 0x0
May  4 22:05:11 kernel: Linux version 4.1.27 ([email protected]) (gcc version 5.3.0 (Buildroot 2016.02) ) #2 SMP PREEMPT Sun Apr 26 00:13:17 EDT 2020
May  4 22:05:11 kernel: CPU: AArch64 Processor [420f1000] revision 0
May  4 22:05:11 kernel: Detected VIPT I-cache on CPU0
May  4 22:05:11 kernel: alternatives: enabling workaround for ARM erratum 845719
May  4 22:05:11 kernel: PERCPU: Embedded 15 pages/cpu @ffffffc01ffd6000 s21376 r8192 d31872 u61440
May  4 22:05:11 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 122112
May  4 22:05:11 kernel: Kernel command line: coherent_pool=1M cpuidle_sysfs_switch
May  4 22:05:11 kernel: PID hash table entries: 2048 (order: 2, 16384 bytes)
May  4 22:05:11 kernel: Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
May  4 22:05:11 kernel: Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
May  4 22:05:11 kernel: Memory: 440192K/495616K available (4698K kernel code, 294K rwdata, 1572K rodata, 228K init, 470K bss, 55424K reserved, 0K cma-reserved)
May  4 22:05:11 kernel: Virtual kernel memory layout:
 

bmn1

Regular Contributor
@bmn1, give a few hours for others to answer your question directly, but your routers issues seem very unique, to me. :)
Nothing, even after your nuclear procedure I had a crash after 2 days.
Same reboot message. With no active services.
 

L&LD

Part of the Furniture
How long does it last after a full reset/Initialize and with only the M&M Config defaults changed?
 

bmn1

Regular Contributor
Router lasted 49 hours configuring only WAN for connecting to my ISP and WiFi with wpa2 password. No other options.

I’m from Italy and I had Vodafone FTTH, so the asus is connected to a Huawei ONT and I set VID=1036 under LAN - IPTV
It’s required to allow my router to connect to my isp.
This is the only setting I’ve done. No VPN no firewall. Nothing!
 

Escape70

New Around Here
I have seen frequent similar reboots on my ac86u for months. Firmware updates (all Merlin) did not fix them. Yesterday I reset the router to factory defaults and reconfigured everything manually on firmware version 384.18. Tonight it had a kernel oops again:

Aug 4 03:45:49 kernel: Unable to handle kernel paging request at virtual address dead0000000002ee
Aug 4 03:45:49 kernel: pgd = ffffffc0140b9000
Aug 4 03:45:50 kernel: [dead0000000002ee] *pgd=0000000013330003, *pud=0000000013330003, *pmd=00000000153c9003, *pte=0000000000000000
Aug 4 03:45:50 kernel: Internal error: Oops: 96000004 [#1] PREEMPT SMP
Aug 4 03:45:50 kernel: Process swapper/0 (pid: 0, stack limit = 0xffffffc0006dc020)
 

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