What's new

Asus/Merlin Noob: Lots of Kernel entries in sys log

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

EagleCity

New Around Here
Hi there. I'm relatively new to the world of Asus routers and Merlin, so please be gentle.

I've been running an AX86U for about 5 months now, currently on 386.3_2. I absolutely love it. Came home after spending a week away from the house and after about 24 hours I wasn't getting anything to connect. Had full wifi signal, but websites weren't loading on any of our devices. On a whim- I changed out AdGuard's DNS for Cloudflare in the router and that seemed to fix things, however, I'm now seeing a ton of activity in the sys log.

I've reboooted a few times and re-installed the firmware, but am still seeing these types of entries. Connectivity seems to be fine, but I'm concerned about what I'm seeing now. Any ideas on a fix based on the below, or what this may be indicating?

Code:
Nov 29 20:40:09 kernel: CONSOLE: 147449.360 tx:prep:802.1x
Nov 29 20:40:09 kernel: CONSOLE: 147449.360 tx:prep:802.1x
Nov 29 20:40:10 kernel: CONSOLE: 147449.877 tx:prep:802.1x
Nov 29 20:40:10 kernel: CONSOLE: 147450.178 tx:prep:802.1x
Nov 29 20:40:10 kernel: CONSOLE: 147450.288 tx:prep:802.1x
Nov 29 21:10:31 kernel: CONSOLE: 149262.267 wl1: r0hole: tx_exp_seq 0x755, seq 0x756
Nov 29 21:24:32 kernel: CONSOLE: 150098.969 wl1: r0hole: tx_exp_seq 0x44d, seq 0x44e
Nov 29 21:40:09 kernel: CONSOLE: 151030.951 tx:prep:802.1x
Nov 29 21:40:09 kernel: CONSOLE: 151031.049 tx:prep:802.1x
Nov 29 21:40:09 kernel: CONSOLE: 151031.050 wl1.0: wlc_send_bar: for xx:xx:xx:xx:xx:xx seq 0x4 tid 5
Nov 29 21:40:09 kernel: CONSOLE: 151031.190 wl1: xx:xx:xx:xx:xx:xx: addba timed out 0
Nov 29 21:40:10 kernel: CONSOLE: 151031.361 tx:prep:802.1x
Nov 29 21:40:10 kernel: CONSOLE: 151031.460 tx:prep:802.1x
Nov 29 21:40:10 kernel: CONSOLE: 151031.462 wl1.0: wlc_send_bar: for xx:xx:xx:xx:xx:xx seq 0x4 tid 5
Nov 29 21:40:10 kernel: CONSOLE: 151031.564 tx:prep:802.1x
Nov 29 21:54:34 kernel: CONSOLE: 151891.268 wl1: r0hole: tx_exp_seq 0xd39, seq 0xd3a
Nov 29 22:05:58 kernel: CONSOLE: 152571.852 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 22:05:58 kernel: CONSOLE: 152572.060 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 22:05:58 kernel: CONSOLE: 152572.081 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 22:05:58 kernel: CONSOLE: 152572.113 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 22:05:58 kernel: CONSOLE: 152572.227 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 22:05:58 kernel: CONSOLE: 152572.547 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 29 22:05:59 kernel: CONSOLE: 152572.656 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 22:05:59 kernel: CONSOLE: 152572.703 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 22:06:00 kernel: CONSOLE: 152573.784 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 29 22:06:00 kernel: CONSOLE: 152573.804 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 29 22:06:00 kernel: CONSOLE: 152573.824 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 29 22:06:00 kernel: CONSOLE: 152573.846 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
 
Last edited:
These entries are just piling on now

Code:
Nov 29 23:01:20 kernel: CONSOLE: 155877.186 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 29 23:01:20 kernel: CONSOLE: 155877.210 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 23:01:22 kernel: CONSOLE: 155878.910 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 29 23:01:22 kernel: CONSOLE: 155878.929 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 23:01:22 kernel: CONSOLE: 155878.938 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 23:01:22 kernel: CONSOLE: 155878.944 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 23:01:22 kernel: CONSOLE: 155878.990 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 29 23:01:22 kernel: CONSOLE: 155879.001 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 29 23:01:22 kernel: CONSOLE: 155879.077 ppr_get_vht_mcs: Failed ppr_t:0045fd0c BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
 
Last edited:
Did a full reset. Still seeing the same:

Code:
Nov 30 22:11:50 kernel: CONSOLE: 153149.805 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:11:52 kernel: CONSOLE: 153152.167 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:11:52 kernel: CONSOLE: 153152.305 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:11:54 kernel: CONSOLE: 153153.412 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:11:58 kernel: CONSOLE: 153157.639 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:11:58 kernel: CONSOLE: 153157.743 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:11:58 kernel: CONSOLE: 153157.859 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:12:02 kernel: CONSOLE: 153161.405 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:12:02 kernel: CONSOLE: 153161.885 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:12:08 kernel: CONSOLE: 153167.855 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
 
After the full reset, how did you set up the router?
 
Manually reconfigured everything. Set up new SSID + pw, enabled DNS privacy. Am pretty much on default config.
Then slowly reconnected devices to see if there was something on the network causing the issue and didn't notice anything out of the ordinary.

Let it run overnight and there are 1k+ kernel entries in the log that are now all over the place. Seeing a bunch of things like this now in addition to what I was previously getting

Code:
Dec  1 08:26:41 kernel: CONSOLE: 189837.701 wlc_ap_authresp: status 0
Dec  1 08:26:41 kernel: CONSOLE: 189837.752 wlc_ap_process_assocreq_done status 0
Dec  1 08:26:41 kernel: CONSOLE: 189837.756 iov:SCB_DEAUTH
Dec  1 08:26:41 kernel: CONSOLE: 189837.757 tx:prep:802.1x
Dec  1 08:26:41 kernel: CONSOLE: 189837.761 wl1.0: wlc_send_bar: for xx:xx:xx:xx:xx:xx seq 0x1 tid 5
Dec  1 08:26:41 kernel: CONSOLE: 189837.761 tx:prep:802.1x
Dec  1 08:26:41 kernel: CONSOLE: 189837.787 iov:SCB_AUTH
Dec  1 08:26:41 kernel: CONSOLE: 189838.397 wl1: xx:xx:xx:xx:xx:xx: addba timed out 0
 
Last edited:
Did a full reset. Still seeing the same:

Code:
Nov 30 22:11:50 kernel: CONSOLE: 153149.805 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:11:52 kernel: CONSOLE: 153152.167 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:11:52 kernel: CONSOLE: 153152.305 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:11:54 kernel: CONSOLE: 153153.412 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:11:58 kernel: CONSOLE: 153157.639 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:11:58 kernel: CONSOLE: 153157.743 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:11:58 kernel: CONSOLE: 153157.859 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Nov 30 22:12:02 kernel: CONSOLE: 153161.405 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:12:02 kernel: CONSOLE: 153161.885 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Nov 30 22:12:08 kernel: CONSOLE: 153167.855 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
My guess is that these messages are caused by one specific client device. You could try powering off devices one at a time until you find it. This is a bit of a long shot but try setting the 5GHz band to a fixed channel and 80MHz bandwidth.

Manually reconfigured everything. Set up new SSID + pw, enabled DNS privacy. Am pretty much on default config.
Then slowly reconnected devices to see if there was something on the network causing the issue and didn't notice anything out of the ordinary.

Let it run overnight and there are 1k+ kernel entries in the log that are now all over the place. Seeing a bunch of things like this now in addition to what I was previously getting

Code:
Dec  1 08:26:41 kernel: CONSOLE: 189837.701 wlc_ap_authresp: status 0
Dec  1 08:26:41 kernel: CONSOLE: 189837.752 wlc_ap_process_assocreq_done status 0
Dec  1 08:26:41 kernel: CONSOLE: 189837.756 iov:SCB_DEAUTH
Dec  1 08:26:41 kernel: CONSOLE: 189837.757 tx:prep:802.1x
Dec  1 08:26:41 kernel: CONSOLE: 189837.761 wl1.0: wlc_send_bar: for xx:xx:xx:xx:xx:xx seq 0x1 tid 5
Dec  1 08:26:41 kernel: CONSOLE: 189837.761 tx:prep:802.1x
Dec  1 08:26:41 kernel: CONSOLE: 189837.787 iov:SCB_AUTH
Dec  1 08:26:41 kernel: CONSOLE: 189838.397 wl1: xx:xx:xx:xx:xx:xx: addba timed out 0
Those messages are the normal "syslog noise".
 
Overnight there were a lot of Kernal entries that seem to likely be caused by our iPhones. Both my wife and I have iPhone 13's.

On my iPhone- I see a Privacy Warning now when connected to the network. Never had this before.

Privacy Warning
This network is blocking encrypted DNS traffic



Here are the WAN DNS settings. Am not using DNSFilter.

Screen Shot 2021-12-02 at 9.12.05 AM.png
 
Based on the above- my theory is that this is somehow DNS related.

This all started when a few days ago I couldn't connect to any websites. The network was up, devices were connected, everything fine with the modem. But our phones and computers couldn't get anything to load.

I was using AdGuard (with DNS Privacy), as I had been for the last 6 months. I switched over to Cloudflare and magically everything started working. 2 days later and I still can't get adguard working on the router. It seems like it's unable to resolve domains- if I ping an ip address it seems to be fine.

Could just be a coincidence, but I'm leaning towards something DNS related in the router.
 
Update! I've kept both my and my wife's iPhones off wifi for the last 24 hours, and we haven't seen a single one of these Kernel entries since:

Code:
kernel: CONSOLE: 153161.885 ppr_get_vht_mcs: Failed ppr_t:0045b420 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c

I'm wondering what on the iPhone could be causing this... could it be the phone switching between 2.4 and 5g bands?
 
Oddly enough for me- the issue has seemed to take care of itself. I suspected a correlation between our iPhone 13's and the log entries, but never confirmed. Only changes have been the phones have been upgraded to latest iOS, and Merlin now running 386.4
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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