Wifi driver crash on Tx1

Wifi module crash was reported in Tx1 with following logs in syslog

Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: Disconnect event - remove keys
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: State: DISCONNECTED -> DISCONNECTED
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Set wlan0 operstate 0->0 (DORMANT)
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: netlink: Operstate: ifindex=7 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: EAPOL: External notification - portEnabled=0
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: EAPOL: External notification - portValid=0
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: l2_packet_receive: src=8c:94:1f:08:22:ed len=121
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: RX EAPOL from 8c:94:1f:08:22:ed
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: RX EAPOL - hexdump(len=121): 02 03 00 75 02 00 8a 00 10 00 00 00 00 00 00 00 00 0a 11 47 c8 e2 13 61 c8 25 a7 1a 88 e0 7e 2c bf d7 ae 51 c6 6e 14 ae 31 90 d0 5a 74 17 16 7a 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 16 dd 14 00 0f ac 04 25 04 6a b0 45 d3 c5 69 68 cc 33 a6 58 65 57 74
Mar  4 13:52:17 bot-6218 kernel: [74433.649582] CFG80211-ERROR) wl_notify_connect_status : wl_bss_connect_done succeeded with 8c:94:1f:08:22:ed
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: Not associated - Delay processing of received EAPOL frame (state=DISCONNECTED bssid=00:00:00:00:00:00)
Mar  4 13:52:17 bot-6218 kernel: [74433.664585] cfg80211: World regulatory domain updated:
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: State: DISCONNECTED -> SCANNING
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: Starting AP scan for wildcard SSID
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: Optimize scan based on previously generated frequency list
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: Add radio work 'scan'@0x55702671e0
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: First radio work item in the queue - schedule start immediately
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: Starting radio work 'scan'@0x55702671e0 after 0.000019 second wait
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: wlan0: nl80211: scan request
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Scan frequency 5240 MHz
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Scan frequency 2412 MHz
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Scan frequency 5180 MHz
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Scan frequency 5220 MHz
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Scan frequency 2462 MHz
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Scan frequency 2437 MHz
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Scan frequency 5200 MHz
Mar  4 13:52:17 bot-6218 kernel: [74433.675260] cfg80211:  DFS Master region: unset
Mar  4 13:52:17 bot-6218 kernel: [74433.677815] CFG80211-ERROR) wl_bss_connect_done : Report connect result - connection succeeded
Mar  4 13:52:17 bot-6218 kernel: [74433.677822] CFG80211-ERROR) wl_is_linkdown : Link down Reason : WLC_E_DEAUTH
Mar  4 13:52:17 bot-6218 kernel: [74433.677828] CFG80211-ERROR) wl_notify_connect_status : link down if wlan0 may call cfg80211_disconnected. event : 5, reason=7 from 8c:94:1f:34:f5:ed
Mar  4 13:52:17 bot-6218 kernel: [74433.677986] CFG80211-ERROR) wl_notify_connect_status : BSSID of event is not the connected BSSID(ignore it) cur: 8c:94:1f:08:22:ed event: 8c:94:1f:34:f5:ed e->ifidx:0
Mar  4 13:52:17 bot-6218 kernel: [74433.677993] CFG80211-ERROR) wl_notify_connect_status : wl_bss_connect_done succeeded with 8c:94:1f:08:22:ed
Mar  4 13:52:17 bot-6218 kernel: [74433.733265] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Mar  4 13:52:17 bot-6218 kernel: [74433.743018] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Mar  4 13:52:17 bot-6218 kernel: [74433.751042] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Mar  4 13:52:17 bot-6218 kernel: [74433.759138] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Mar  4 13:52:17 bot-6218 kernel: [74433.767220] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Mar  4 13:52:17 bot-6218 kernel: [74433.776754] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Mar  4 13:52:17 bot-6218 kernel: [74433.786278] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Mar  4 13:52:17 bot-6218 kernel: [74433.794405] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Mar  4 13:52:17 bot-6218 kernel: [74433.802464] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Mar  4 13:52:17 bot-6218 kernel: [74433.810728] ------------[ cut here ]------------
Mar  4 13:52:17 bot-6218 kernel: [74433.815342] WARNING: at /dvs/git/dirty/git-master_linux/kernel/kernel-4.4/net/wireless/sme.c:714
Mar  4 13:52:17 bot-6218 kernel: [74433.824107] Modules linked in: xt_addrtype br_netfilter bcmdhd e1000e ptp pps_core bluedroid_pm
Mar  4 13:52:17 bot-6218 kernel: [74433.832845] 
Mar  4 13:52:17 bot-6218 kernel: [74433.834332] CPU: 0 PID: 18684 Comm: kworker/u8:2 Tainted: G        W       4.4.38-tegra #1
Mar  4 13:52:17 bot-6218 kernel: [74433.842576] Hardware name: jetson_tx1 (DT)
Mar  4 13:52:17 bot-6218 kernel: [74433.846668] Workqueue: cfg80211 cfg80211_event_work
Mar  4 13:52:17 bot-6218 kernel: [74433.851538] task: ffffffc0594e8c80 ti: ffffffc06a0b4000 task.ti: ffffffc06a0b4000
Mar  4 13:52:17 bot-6218 kernel: [74433.859006] PC is at __cfg80211_connect_result+0x1a8/0x234
Mar  4 13:52:17 bot-6218 kernel: [74433.864477] LR is at __cfg80211_connect_result+0xf0/0x234
Mar  4 13:52:17 bot-6218 kernel: [74433.869860] pc : [<ffffffc000b05580>] lr : [<ffffffc000b054c8>] pstate: 40000145
Mar  4 13:52:17 bot-6218 kernel: [74433.877238] sp : ffffffc06a0b7c90
Mar  4 13:52:17 bot-6218 kernel: [74433.880542] x29: ffffffc06a0b7ca0 x28: 0000000000000000 
Mar  4 13:52:17 bot-6218 kernel: [74433.885853] x27: 0000000000000000 x26: ffffffc001481278 
Mar  4 13:52:17 bot-6218 kernel: [74433.891165] x25: ffffffc061dfc218 x24: ffffffc000d73a40 
Mar  4 13:52:17 bot-6218 kernel: [74433.896473] x23: ffffffc0f4b64eb0 x22: ffffffc061dfc218 
Mar  4 13:52:17 bot-6218 kernel: [74433.901781] x21: 0000000000000000 x20: 0000000000000000 
Mar  4 13:52:17 bot-6218 kernel: [74433.907092] x19: ffffffc0f4b64e00 x18: 00000000006c1000 
Mar  4 13:52:17 bot-6218 kernel: [74433.912402] x17: 0000007f8c4f1c80 x16: 000000000068f718 
Mar  4 13:52:17 bot-6218 kernel: [74433.917711] x15: 00000000ffffffff x14: 0a01060104010200 
Mar  4 13:52:17 bot-6218 kernel: [74433.923021] x13: 002e6e002f326200 x12: 5e43420000a42700 
Mar  4 13:52:17 bot-6218 kernel: [74433.928330] x11: 00a4030080010102 x10: 0000000000000001 
Mar  4 13:52:17 bot-6218 kernel: [74433.933639] x9 : 0000000000000010 x8 : ffffffbffc1033c8 
Mar  4 13:52:17 bot-6218 kernel: [74433.938948] x7 : 0000000000000001 x6 : 0000000000000002 
Mar  4 13:52:17 bot-6218 kernel: [74433.944258] x5 : 00000000fffffffe x4 : 0000000000000009 
Mar  4 13:52:17 bot-6218 kernel: [74433.949568] x3 : ffffffc0014ba700 x2 : ffffffc06a0b7be0 
Mar  4 13:52:17 bot-6218 kernel: [74433.954877] x1 : 0000000000000000 x0 : 0000000000000000 
Mar  4 13:52:17 bot-6218 kernel: [74433.960187] 
Mar  4 13:52:17 bot-6218 kernel: [74433.961891] ---[ end trace 23e6b01c5f56e876 ]---
Mar  4 13:52:17 bot-6218 kernel: [74433.966496] Call trace:
Mar  4 13:52:17 bot-6218 kernel: [74433.968935] [<ffffffc000b05580>] __cfg80211_connect_result+0x1a8/0x234
Mar  4 13:52:17 bot-6218 kernel: [74433.975448] [<ffffffc000adf3d0>] cfg80211_process_wdev_events+0xe8/0x1a8
Mar  4 13:52:17 bot-6218 kernel: [74433.982134] [<ffffffc000adf4dc>] cfg80211_process_rdev_events+0x4c/0x68
Mar  4 13:52:17 bot-6218 kernel: [74433.988733] [<ffffffc000ad9fbc>] cfg80211_event_work+0x1c/0x28
Mar  4 13:52:17 bot-6218 kernel: [74433.994554] [<ffffffc0000ba7c0>] process_one_work+0x234/0x45c
Mar  4 13:52:17 bot-6218 kernel: [74434.000286] [<ffffffc0000bac30>] worker_thread+0x248/0x428
Mar  4 13:52:17 bot-6218 kernel: [74434.005758] [<ffffffc0000c0888>] kthread+0xf8/0x100
Mar  4 13:52:17 bot-6218 kernel: [74434.010624] [<ffffffc0000847a0>] ret_from_fork+0x10/0x30
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: Scan requested (ret=0) - scan timeout 30 seconds
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Event message available
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Drv Event 36 (NL80211_CMD_REG_CHANGE) received for p2p-dev-wlan0
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: nl80211: Regulatory domain change
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]:  * initiator=0
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]:  * type=1
Mar  4 13:52:17 bot-6218 kernel: [74434.038521] cfg80211: Regulatory domain changed to country: KR
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: p2p-dev-wlan0: Event CHANNEL_LIST_CHANGED (28) received
Mar  4 13:52:17 bot-6218 wpa_supplicant[6392]: p2p-dev-wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar  4 13:52:18 bot-6218 kernel: [74434.048494] cfg80211:  DFS Master region: JP
Mar  4 13:52:18 bot-6218 kernel: [74434.052945] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Mar  4 13:52:18 bot-6218 kernel: [74434.062847] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Mar  4 13:52:18 bot-6218 kernel: [74434.071281] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Mar  4 13:52:18 bot-6218 kernel: [74434.081048] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Mar  4 13:52:18 bot-6218 kernel: [74434.090833] cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 3000 mBm), (0 s)
Mar  4 13:52:18 bot-6218 kernel: [74434.099106] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: Regulatory information - country=KR (DFS-JP)
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 2402-2482 @ 40 MHz 20 mBm
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5170-5250 @ 80 MHz 20 mBm
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5250-5330 @ 80 MHz 20 mBm (DFS)
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5490-5710 @ 160 MHz 30 mBm (DFS)
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5735-5835 @ 80 MHz 30 mBm
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: Added 802.11b mode based on 802.11g information
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: wlan0: Updating hw mode
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: Regulatory information - country=KR (DFS-JP)
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 2402-2482 @ 40 MHz 20 mBm
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5170-5250 @ 80 MHz 20 mBm
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5250-5330 @ 80 MHz 20 mBm (DFS)
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5490-5710 @ 160 MHz 30 mBm (DFS)
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: 5735-5835 @ 80 MHz 30 mBm
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: Added 802.11b mode based on 802.11g information
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: wlan0: Control interface command 'SIGNAL_POLL'
Mar  4 13:52:18 bot-6218 kernel: [74434.108737] CFG80211-ERROR) wl_cfg80211_get_station : Wrong Mac address: 00:00:00:00:00:00 != 8c:94:1f:08:22:ed
Mar  4 13:52:18 bot-6218 kernel: [74434.121103] cfg80211: World regulatory domain updated:
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: Event message available
Mar  4 13:52:18 bot-6218 wpa_supplicant[6392]: nl80211: Ignored event (cmd=46) for foreign interface (ifind

The crash log is similar to one reported on topic but solution here marked suggest changes in Network-Manager. However we are using wpa_supplicant for connecting to wifi, and Network-Manger is disabled.

what could be the other reason for this crash?

System details :
System Information :
Nvidia Tx1

Linux nvidia 4.4.38-tegra #1 SMP PREEMPT Thu Mar 1 20:44:58 PST 2018 aarch64 aarch64 aarch64 GNU/Linux
#R28 (release), REVISION: 2.0, GCID: 10567845, BOARD: t210ref, EABI: aarch64, DATE: Fri Mar 2 04:58:16 UTC 2018

Could you also try with latest rel28.4 or rel32.5.1 to see if any issue?

@WayneWWW, Sorry but we don’t have the flexibility to upgrade the Jetpack OTA on many of our client site. Instead if a patch can solve the problem that would be much appreciated. If it’s a known issue then we can try with a patch on wifi module/Kernel Image.