Manjaro is crashing AC86U router when connecting after reboot (Manjaro forums suggested posting here)

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Fattage

Occasional Visitor
Wireless adapter: [TP-Link wireless AX 3000 (ax200 chipset) with bluetooth 5.1] (https://www.amazon.com/gp/product/B07X462KRK/?tag=snbforums-20)

Router: Asus AC86u running aswrt-merlin RT-AC86U_386.3_2

Running Manjaro 21.1 (fresh install). I have tried the LTS kernel as well as the latest non-experimental kernel but neither of those worked either.

When first booting up Manjaro after logging into my account it attempts to autoconnect to my wifi but then crashes the router. Following that it may crash a second or third time before finally allowing me to connect to the router without it crashing. After that if I manually disconnect and reconnected it doesn’t crash the router. It only happens after a reboot. I have also tried not automatically connecting to wifi on login but it crashes the router then as well once I try to connect manually.

(no issues on windows running a dual boot system)

Manjaro forum: https://forum.manjaro.org/t/tp-link-ax3000-wireless-adapter-is-crashing-router-firmware/81135
 

Centrifuge

Senior Member
What do the system logs (of the router) say?
 

Fattage

Occasional Visitor
What do the system logs (of the router) say?
The only logs I found on the web GUI was the general system logs and they appear to be temporary as they get cleared after the crash. Nothing else useful was listed after that except for successful connections also something about kernel: protocol 0800 is buggy. I can post what I get though once I am home. If there are other logs where do I find them?
 

Morris

Senior Member
While the router should no crash, I've had mine crash when "Wi-Fi Agile Multiband" is enabled. It is off by default and you can try disabling it if enabled. Also try the latest Intel AX200 Linux drivers.

Good luck,

Morris
 

Crimliar

Occasional Visitor
Okay, so this is only anecdotal! I've seen the protocol 0800 is buggy error message on my own RT-AC86U; but only when I tried running Diversion on the router! And Manjaro works just fine with the router here!
 

Fattage

Occasional Visitor
Code:
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br1: port 7(eth6.501) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br1: port 6(eth5.501) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br1: port 5(eth4.501) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br1: port 4(eth3.501) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br1: port 3(eth2.501) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br1: port 1(wl0.1) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: Init chrdev /dev/idp with major 190
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: tdts: tcp_conn_max = 8000
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: tdts: tcp_conn_timeout = 300 sec
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br2: port 7(eth6.502) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br2: port 6(eth5.502) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br2: port 5(eth4.502) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br2: port 4(eth3.502) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br2: port 3(eth2.502) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: br2: port 1(wl1.1) entered forwarding state
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: DROP IN=eth0 OUT= MAC= SRC= DST= LEN=86 TOS=0x00 PREC=0x00 TTL=235 ID=24937 DF PROTO=TCP SPT=443 DPT=495>
2021-09-03T17:16:44-06:00 RT-AC86U-B180-12ED2A1-C kernel: DROP IN=eth0 OUT= MAC= SRC= DST= LEN=83 TOS=0x00 PREC=0x00 TTL=241 ID=51875 DF PROTO=TCP SPT=443 DPT=47>
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: ACCEPT IN=br0 OUT=eth0 MAC= SRC= DST= LEN=84 TOS=0x00 PREC=0x00 TTL=63 ID=43793 DF PROTO=ICMP TYPE=8 >
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: DROP IN=eth0 OUT=eth0 MAC= SRC= DST= LEN=93 TC=0 HO>
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: DROP IN=eth0 OUT= MAC= SRC= DST= LEN=111 TOS=0x00 PREC=0x00 TTL=111 ID=16837 DF PROTO=TCP SPT=443 DPT=61>
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: tun: Universal TUN/TAP device driver, 1.6
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: DROP IN=eth0 OUT= MAC= SRC= DST= LEN=83 TOS=0x00 PREC=0x00 TTL=44 ID=17769 DF PROTO=TCP SPT=443 DPT=4555>
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: DROP IN=eth0 OUT= MAC= SRC= DST= LEN=144 TOS=0x08 PREC=0x40 TTL=118 ID=51524 PROTO=UDP SPT=27027 DPT=56>
2021-09-03T17:16:45-06:00 RT-AC86U-B180-12ED2A1-C kernel: ACCEPT IN=br0 OUT=eth0 MAC= SRC= DST= LEN=52 TOS=0x00 PREC=0x00 TTL=127 ID=60475 DF PROTO=TCP SPT=59205 DPT=>
2021-09-03T17:16:46-06:00 RT-AC86U-B180-12ED2A1-C kernel: ACCEPT IN=br0 OUT=eth0 MAC= SRC= DST= LEN=66 TOS=0x00 PREC=0x00 TTL=63 ID=3948 DF PROTO=TCP SPT=51810 >
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: ACCEPT IN=br0 OUT=eth0 MAC= SRC= DST= LEN=105 TOS=0x00 PREC=0x00 TTL=63 ID=3094 DF PROTO=UDP SPT=51037 DPT=5>
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: DROP IN=eth0 OUT= MAC= SRC= DST= LEN=111 TOS=0x00 PREC=0x00 TTL=111 ID=16838 DF PROTO=TCP SPT=443 DPT=61>
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: SHN Release Version: 2.0.1 851496c
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: UDB Core Version: 0.2.18
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: Init chrdev /dev/idpfw with major 191
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: IDPfw: flush fc
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: IDPfw: IDPfw is ready
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: sizeof forward pkt param = 280
2021-09-03T17:16:47-06:00 RT-AC86U-B180-12ED2A1-C kernel: ACCEPT IN=br0 OUT=eth0 MAC=redacted SRC=redacted DST=redacted LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=23366 DF PROTO=TCP SPT=37084 >
2021-09-03T17:16:48-06:00 RT-AC86U-B180-12ED2A1-C kernel: ACCEPT IN=br0 OUT=eth0 MAC=redacted SRC=redacted DST=redacted LEN=105 TOS=0x00 PREC=0x00 TTL=63 ID=3146 DF PROTO=UDP SPT=44360 DPT=5>
2021-09-03T17:16:48-06:00 RT-AC86U-B180-12ED2A1-C kernel: protocol 0800 is buggy, dev eth6

I just crashed the router on purpose and set up a log server and this is what was outputted to the kernel.log file before going back to a normal state. Let me know if you want other logs. List here:

A.QoS.log dhcp6_client.log dropbear.log kernel.log ovpn-server1.log stubby.log
avahi-daemon.log dhcp_client.log hour_monitor.log lldpd.log rc_service.log vpnserver1.log
BWDPI.log disk_monitor.log httpd.log Mastiff.log roamast.log WAN_Connection.log
cfg_server.log dnsmasq-dhcp.log inadyn.log ntpd.log Samba_Server.log wan.log
crond.log dnsmasq.log jffs2.log odhcp6c.log start_ddns.log wlceventd.log
 

L&LD

Part of the Furniture
How did you crash it?
 

Fattage

Occasional Visitor
Restarted windows then in the grub menu selected manjaro then logged into my account. Once logged in it auto connects to my wifi then disconnects/crashes the router. surprisingly it actually did it again after rebooting manjaro and going back to windows. with the same log output errors. excluding the accept/reject log which I don't think is the important bit of the logs.
 

Centrifuge

Senior Member
Inspect your Network manager in Manjaro, check to see that IP4 and IP6 are set to auto. Have you applied any specialized settings to the router?

edit: could it be related to this kernel module issue with Realtek?
 
Last edited:

Fattage

Occasional Visitor
Inspect your Network manager in Manjaro, check to see that IP4 and IP6 are set to auto. Have you applied any specialized settings to the router?

edit: could it be related to this kernel module issue with Realtek?
Manjaro is set to auto. Nothing too crazy on the router. I have some port forwarding, vpn server, guest networks, QoS, DDNS, IPv6 support enabled, smart connect disabled, and McAfee. As far as the Realtek goes it sounds similar but not realtek card.
 

ColinTaylor

Part of the Furniture
I just crashed the router on purpose and set up a log server and this is what was outputted to the kernel.log file before going back to a normal state.
There is nothing in that segment of the logs that indicates that any crash occurred. The router should retain its previous log files even after a crash. I suggest that you look for /jffs/syslog.log and /jffs/syslog.log-1, upload them to pastebin and post a link to them.
 

sfx2000

Part of the Furniture
Once logged in it auto connects to my wifi then disconnects/crashes the router. surprisingly it actually did it again after rebooting manjaro and going back to windows.

Take a look at /var/log/syslog on the manjaro box - see what is happening there - maybe something in wpa_supplicant at first guess...

I would also check the nm items, if I recall, Manjaro does use NetworkManager..
 

Fattage

Occasional Visitor
There is nothing in that segment of the logs that indicates that any crash occurred. The router should retain its previous log files even after a crash. I suggest that you look for /jffs/syslog.log and /jffs/syslog.log-1, upload them to pastebin and post a link to them.

This is the log of the last week or so. Sorry for the late response. Just to make sure I did the Manjaro thing again just before getting the log.

@sfx2000 I also could not find the syslog in that directory.
 

ColinTaylor

Part of the Furniture
There is still almost no information in your syslog which is very odd. What logging levels do you have set (System Log - General Log)?

Untitled.png
 

Fattage

Occasional Visitor
Currently warning and up. Here is the log with debug and all after crashing it. Sorry with it higher I end up getting so many logs about accepted packets it's hard to read.
There is still almost no information in your syslog which is very odd. What logging levels do you have set (System Log - General Log)?

View attachment 36339
I had it on error and above. Now it's set to all. I have issues with getting too many logs about accepted packets. Also it seems that since the date is reset it messes things up and it difficult to find the log. Here is what I have after updating the logging level. https://pastebin.com/qtMWppuL
 

ColinTaylor

Part of the Furniture
Sorry with it higher I end up getting so many logs about accepted packets it's hard to read.
Just turn of the logging of accepted packets (Firewall > General), it's not useful.
 

ColinTaylor

Part of the Furniture
Thanks. Well in both log files the error message is the same:
Code:
BUG: failure at mm/slab.c:2744/cache_free_debugcheck()!
Kernel panic - not syncing: BUG!
So some sort of memory error :rolleyes:. The currently running module varies so there's no smoking gun there.

I think the most practical approach (other than just ignoring it) would be to factory reset your router, do the minimum amount of configuration, and then see if the problem still persists. You can then restore back to where you were before if you take a backup of your current settings and JFFS (Administration - Restore/Save/Upload Setting).
 

Fattage

Occasional Visitor
Thanks. Well in both log files the error message is the same:
Code:
BUG: failure at mm/slab.c:2744/cache_free_debugcheck()!
Kernel panic - not syncing: BUG!
So some sort of memory error :rolleyes:. The currently running module varies so there's no smoking gun there.

I think the most practical approach (other than just ignoring it) would be to factory reset your router, do the minimum amount of configuration, and then see if the problem still persists. You can then restore back to where you were before if you take a backup of your current settings and JFFS (Administration - Restore/Save/Upload Setting).
Unfortunately I have tried that and it sill had the issue even with minimal configuration on the router. Possible a different network card fix it?
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top