linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Pkshih <pkshih@realtek.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Funny log entries for rtw88_8821ce
Date: Mon, 31 Jan 2022 16:53:44 -0600	[thread overview]
Message-ID: <c356d5ae-a7b3-3065-1121-64c446e70333@lwfinger.net> (raw)

Ping-Ke and list,

Within the last couple of days, I was testing rtw88 with an rtl8821ce card. I 
noticed that whenever the device is not connected to an AP, the log is flooded 
with messages like the following:
[130462.603539] rtw_8821ce 0000:02:00.0: stop vif ee:a4:95:4e:53:8b on port 0
[130463.116843] rtw_8821ce 0000:02:00.0: start vif aa:fc:19:66:5e:e2 on port 0
[130874.613430] rtw_8821ce 0000:02:00.0: stop vif aa:fc:19:66:5e:e2 on port 0
[130875.122641] rtw_8821ce 0000:02:00.0: start vif d2:e6:23:ba:98:76 on port 0
[131286.677828] rtw_8821ce 0000:02:00.0: stop vif d2:e6:23:ba:98:76 on port 0
[131287.192108] rtw_8821ce 0000:02:00.0: start vif 82:c4:33:96:2e:c6 on port 0\

After ~411 secs, the callback routine for remove_interface() in struct 
ieee80211_ops is called. After <1 sec, the add_interface() callback is called to 
restart the vif. Is this normal behavior and I see it in the logs because this 
driver is the only one that logs the start/stop calls, or is something else 
going on? It would be easy to disable those log entries, but I would like to 
know if there is some other condition?

On my kernel, HZ is 250, thus the interval is roughly 103,000 jiffies.

Thanks,

Larry


             reply	other threads:[~2022-01-31 22:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 22:53 Larry Finger [this message]
2022-02-01  6:26 ` Funny log entries for rtw88_8821ce Pkshih
2022-02-03 20:06   ` Larry Finger
2022-02-08  9:01     ` Kalle Valo
2022-02-08 12:02       ` Pkshih
2022-02-10 14:26         ` Kalle Valo
2022-02-11  0:25           ` Pkshih

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c356d5ae-a7b3-3065-1121-64c446e70333@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).