Search Linux Wireless

Funny log entries for rtw88_8821ce

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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




[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Wireless Regulations]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux