Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARNING in nl80211 when connecting to wifi on Jetson Xavier NX #25

Open
brgl opened this issue Mar 9, 2021 · 7 comments
Open

WARNING in nl80211 when connecting to wifi on Jetson Xavier NX #25

brgl opened this issue Mar 9, 2021 · 7 comments

Comments

@brgl
Copy link
Contributor

brgl commented Mar 9, 2021

When connecting to the wifi network with wpa_supplicant on Jetson Xavier NX, the following warning is emitted:

[   13.364004] ------------[ cut here ]------------
[   13.364219] WARNING: CPU: 0 PID: 4434 at net/wireless/nl80211.c:14141 cfg80211_ch_switch_notify+0x138/0x158 [cfg80211]
[   13.364396] Modules linked in: rtl8822ce mttcan rtk_btusb can_dev btusb btrtl btbcm btintel cfg80211 spidev nvgpu overlay
[   13.364681] 
[   13.364717] CPU: 0 PID: 4434 Comm: RTW_CMD_THREAD Not tainted 4.9.201-l4t-r32.5+ge443483e8c9c #1
[   13.364860] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[   13.364968] task: ffffffc1efd57000 task.stack: ffffffc1d9c74000
[   13.365145] PC is at cfg80211_ch_switch_notify+0x138/0x158 [cfg80211]
[   13.365746] LR is at rtw_cfg80211_ch_switch_notify+0x94/0x98 [rtl8822ce]
[   13.365866] pc : [<ffffff8001169eb0>] lr : [<ffffff8001328fc0>] pstate: 60c00045
[   13.365991] sp : ffffffc1d9c77c30
[   13.366054] x29: ffffffc1d9c77c30 x28: 0000000000000000 
[   13.366163] x27: ffffff80012bc190 x26: ffffffc1dbabd200 
[   13.366466] x25: ffffff800bf721bc x24: 0000000000000000 
[   13.366886] x23: ffffffc1da779000 x22: ffffffc1efd7b400 
[   13.368562] x21: ffffffc1da78b800 x20: 0000000000000001 
[   13.374338] x19: ffffffc1d9c77cb8 x18: 0000000000000000 
[   13.380023] x17: 0000000000000002 x16: 0000000000000000 
[   13.385710] x15: 0000000000000030 x14: 0000000000000008 
[   13.391650] x13: 7f1201c7fffc002a x12: 0105c00363fffa03 
[   13.397338] x11: 0000000000000004 x10: 0000000000000002 
[   13.403025] x9 : 0000000000000004 x8 : ffffffc1d9c77d4a 
[   13.408801] x7 : 0000000000000000 x6 : 0000000000000001 
[   13.414312] x5 : 0000000000000040 x4 : ffffffc1da78d748 
[   13.419650] x3 : 000000000000143c x2 : 0000000000000001 
[   13.424988] x1 : 0000145a00000003 x0 : 0000000000000000 
[   13.430073] 
[   13.431727] ---[ end trace 90ada372a32d1e76 ]---
[   13.436191] Call trace:
[   13.438725] [<ffffff8001169eb0>] cfg80211_ch_switch_notify+0x138/0x158 [cfg80211]
[   13.446037] [<ffffff8001328fc0>] rtw_cfg80211_ch_switch_notify+0x94/0x98 [rtl8822ce]
[   13.453204] [<ffffff80012bc0fc>] rtw_chk_start_clnt_join+0x424/0x4b8 [rtl8822ce]
[   13.460457] [<ffffff80012bc3c8>] join_cmd_hdl+0x238/0x328 [rtl8822ce]
[   13.466310] [<ffffff800127a4dc>] rtw_cmd_thread+0x3f4/0x5f8 [rtl8822ce]
[   13.471987] [<ffffff80080d9d7c>] kthread+0xec/0xf0
[   13.476795] [<ffffff80080838a0>] ret_from_fork+0x10/0x30

This doesn't seem to cause any problems with connectivity. The kernel revision is: e443483e8c9c25d878caf33e7b97193eee22fef2 and the system is just regular yocto system based on meta-tegra.

@madisongh
Copy link
Member

madisongh commented Mar 9, 2021

It is just a WARN_ON, but it looks like there was a change in the 80211 core code that expects some different behavior from drivers than before. The realtek drivers that NVIDIA imported may not have the corresponding change. Might be worth investigating. Upstream change that added this warning is here. Looks like it came in when NVIDIA patched in the update to 4.9.201.

@jchillerup
Copy link

jchillerup commented Jul 15, 2021

Replying in the thread to say I'm also seeing the same dumps in my dmesg (and to subscribe to the thread). Hard to say if the issue affects performance, since we're also battling a performance issue. Could be unrelated.

@dat-tran-matternet
Copy link

Any updates with this issue? I am also seeing the same with the latest kernel updates from dunfell 4.9.253-l4t-r32.6

thanks

@Gabryss
Copy link

Gabryss commented Apr 26, 2022

It seems that this issue is still there. I am using a Jetson Nano with the kernel version 4.9.253 tegra running on ubuntu 20. How can we approach this ?

@sheuschkel
Copy link

I have similar dumps in my logfiles and then I get an "CTRL-EVENT-SCAN-FAILED ret=-16" error and no wifi networks can be found until a reboot.

@ichergui
Copy link
Member

Hello @sheuschkel
Could you please share the branch you are using and steps you followed to creat an access point ?
I tried to creat an access point in past and it was working fine to me on my Jetson Xavier NX

@eldo-frederick
Copy link

eldo-frederick commented Jan 4, 2023

It seems that this issue is still there. I am using a Jetson Nano with the kernel version 4.9.253 tegra running on ubuntu 20.

Hello @Gabryss
I am facing the same issue in Jetson nano and same kernel version and wifi disconnects and not connecting back. Have you resolved the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants