Weird failure messages in log using 386.3_2 on RT-AX86U?

  • 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.

RogerSC

Part of the Furniture
I've seen this question asked a couple of times, but no answer. I'm using firmware version 386.3_2 on a RT-AX86U and see some odd failure messages in the log. Everything seems to be working as expected, so I'm wondering if this is something that I should pay attention to, or one of those things that don't matter somehow:

Code:
Oct 22 13:30:24 kernel: CONSOLE: 192046.309 wl1.0: wlc_send_bar: for 4c:20:b8:ed:79:a5 seq 0x1 tid 4
Oct 22 13:41:13 kernel: CONSOLE: 192676.350 wl1: r0hole: tx_exp_seq 0xd1, seq 0xd2
Oct 22 13:41:18 kernel: CONSOLE: 192681.584 ppr_get_vht_mcs: Failed ppr_t:0046d728 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Oct 22 13:41:18 kernel: CONSOLE: 192681.740 ppr_get_vht_mcs: Failed ppr_t:0046d728 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Oct 22 13:44:49 kernel: CONSOLE: 192886.381 ppr_get_vht_mcs: Failed ppr_t:0046d728 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f3c
Oct 22 13:44:49 kernel: CONSOLE: 192886.384 ppr_get_vht_mcs: Failed ppr_t:0046d728 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Oct 22 13:44:49 kernel: CONSOLE: 192886.740 ppr_get_vht_mcs: Failed ppr_t:0046d728 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Oct 22 13:51:21 kernel: CONSOLE: 193266.864 ppr_get_vht_mcs: Failed ppr_t:0046d728 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Oct 22 13:51:21 kernel: CONSOLE: 193266.865 ppr_get_vht_mcs: Failed ppr_t:0046d728 BW:2 Nss:1 mode:0 TX_Chain:4 rateset:00175f4c
Oct 22 13:57:05 hostapd: eth7: STA 90:cd:b6:98:e2:a3 WPA: group key handshake completed (RSN)

I don't know if the surrounding messages are significant, but are included for context.

Really wish that source code was readily available to be able to track down why messages like these are being output...So it goes.
 

Similar threads

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