wlan: mlan0 START SCAN

[KentarouFujita]

In rare cases, a custom board equipped with i.MX8MQ keeps failing to scan Wi-Fi.
If the scan is successful, the connection will be completed in about 10 seconds, but if an ABORT SCAN occurs, it will not return.
The wi-fi module we are using is 88W9098.

I have changed the moal log level to 2 and am analyzing it, but it doesn't seem to output any significant logs.
If anyone has solved a similar problem, please let me know how to solve it.

[ 11.428717] mlan: loading out-of-tree module taints kernel.
[ 11.454906] wlan: Loading MWLAN driver
[ 11.455385] wlan_pcie 0000:01:00.0: enabling device (0000 -> 0002)
[ 11.455449] Attach moal handle ops, card interface type: 0x206
[ 11.456183] PCIE9098: init module param from usr cfg
[ 11.456231] card_type: PCIE9098, config block: 0
[ 11.456237] cfg80211_wext=0xf
[ 11.456241] wfd_name=p2p
[ 11.456245] max_vir_bss=1
[ 11.456249] cal_data_cfg=none
[ 11.456253] drv_mode = 7
[ 11.456256] ps_mode = 2
[ 11.456259] auto_ds = 2
[ 11.456263] fw_name=nxp/pcieuart9098_combo_v1.bin
[ 11.456270] host_mlme=enable
[ 11.456316] rx_work=1 cpu_num=4
[ 11.456331] Attach mlan adapter operations.card_type is 0x206.
[ 11.458146] Request firmware: nxp/pcieuart9098_combo_v1.bin
[ 12.026570] FW download over, size 618724 bytes
[ 12.552662] ddrc freq set to low bus mode
[ 12.890879] WLAN FW is active
[ 12.890904] on_time is 12888812952
[ 12.905158] fw_cap_info=0x81c3fa3, dev_cap_mask=0xffffffff
[ 12.905361] max_p2p_conn = 8, max_sta_conn = 64
[ 12.961013] ddrc freq set to high bus mode
[ 12.961124] wlan: version = PCIE9098--17.92.5.p3-MM5X17247.p5-GPL-(FP92)
[ 12.961726] wlan_pcie 0000:01:00.1: enabling device (0000 -> 0002)
[ 12.961795] Attach moal handle ops, card interface type: 0x206
[ 12.961889] PCIE9098: init module param from usr cfg
[ 12.961940] card_type: PCIE9098, config block: 1
[ 12.961947] cfg80211_wext=0xf
[ 12.961951] wfd_name=p2p
[ 12.961954] max_vir_bss=1
[ 12.961959] cal_data_cfg=none
[ 12.961962] drv_mode = 7
[ 12.961965] ps_mode = 2
[ 12.961968] auto_ds = 2
[ 12.961972] fw_name=nxp/pcieuart9098_combo_v1.bin
[ 12.961979] host_mlme=enable
[ 12.961994] rx_work=1 cpu_num=4
[ 12.962012] Attach mlan adapter operations.card_type is 0x206.
[ 12.966172] Request firmware: nxp/pcieuart9098_combo_v1.bin
[ 12.967101] WLAN FW already running! Skip FW download
[ 12.967112] WLAN FW is active
[ 12.967119] on_time is 12965036475
[ 12.969398] fw_cap_info=0x81c3fa3, dev_cap_mask=0xffffffff
[ 12.969427] max_p2p_conn = 8, max_sta_conn = 64
[ 12.988979] wlan: version = PCIE9098--17.92.5.p3-MM5X17247.p5-GPL-(FP92)
[ 12.989366] wlan: Driver loaded successfully
[ 14.187052] wlan: mlan0 START SCAN
[ 15.268701] ddrc freq set to low bus mode
[ 24.188103] wlan: ABORT SCAN start
[ 24.188330] IOCTL failed: 000000006991828c id=0x10000, sub_id=0x10003 action=1, status_code=0x80000007
[ 29.205726] wlan: mlan0 START SCAN
[ 33.511905] ddrc freq set to high bus mode
[ 34.596334] ddrc freq set to low bus mode
[ 39.207750] wlan: ABORT SCAN start
[ 39.207972] IOCTL failed: 00000000de34e17e id=0x10000, sub_id=0x10003 action=1, status_code=0x80000007
[ 43.751761] ddrc freq set to high bus mode
[ 44.222069] wlan: mlan0 START SCAN
[ 44.836336] ddrc freq set to low bus mode
[ 48.872768] ddrc freq set to high bus mode
[ 49.961326] ddrc freq set to low bus mode
[ 54.223771] wlan: ABORT SCAN start
[ 54.224010] IOCTL failed: 00000000dd8cf28c id=0x10000, sub_id=0x10003 action=1, status_code=0x80000007
[ 64.231817] ddrc freq set to high bus mode
[ 65.316338] ddrc freq set to low bus mode
[ 67.393538] ddrc freq set to high bus mode

[KentarouFujita · Accepted solution]

This case was due to memory corruption caused by an inadequate DRAM configuration.

The problem has now been resolved.
This ticket has served its purpose and is closed.

[masateesh]

Which dram used? what configuration Is required. Could you share solution?

[masateesh]

I am also getting same problem could you please share correction which is required dram side.

[estephania_mart]

Hello,

Is the issue happening in the same custom board ? Could you please share the configuration settings you have ? According to the log you shared, you are using the latest version of this release, could you please help me confirm if you are and also are you using the default driver or are you using another driver ?  Is there some pattern identified when the scan fails ?

Regards,
Estephania

[KentarouFujita]

Hi Estephania!

>Is the problem happening on the same custom board?
Yes, the problem is happening on the same custom board.

>Please let me know your configuration settings.
I am attaching my defconfig and dts.
The defconfig is almost unchanged from BSP (imx8mqevk).

>According to your log, you are using the latest version of this release, please confirm and tell me if you are using the default driver or some other driver.
I am not using the default driver.
The moal and pcieuart9098_combo_v1.bin are using Linux 5.10.72_2.2.0, as I initially suspected a driver problem.
However, the same phenomenon occurred with Linux 5.10.35_2.0.0.

>Is there any pattern when the scan fails?
There is no particular pattern when the scan fails.
When I start up moal and wpa_supplicant after the kernel starts, ABORT SCAN occurs evenly.

[KentarouFujita]

Hi.

>moal and pcieuart9098_combo_v1.bin, I first suspected a driver problem and used Linux 5.10.72_2.2.0.
Sorry, this is a mistake. When I got the first log, the mall and firmware version defaulted to 5.10.35_2.0.0.
It is still at 5.10.35_2.0.0.

I referred to UM11490 to get the moal and firmware logs.
I set the debug flag (drvbdg) for moal to 0x60000207.

The dmesg does not seem to have changed from the first log I posted.
In the firmware dump, there was a log in file_drv_info that I found interesting.
The value of num_cmd_assoc_failure is set to 1.
UM11490 does not have a detailed description of the dump file, so I don't know what this represents.
Does "num_cmd_assoc_failure = 1" have anything to do with ABORT SCAN?

I'm looking for clues to solve the problem, whatever it may be.
Any information is welcome.

Regards

[estephania_mart]

Hello,

I have been checking this and I have not been able to reproduce it with my setup, we might need more details on this setup that you have. I already sent you a message directly, could you please help me check it ?

Regards,

[masateesh]

I am also facing above issue.

here is my log I have observed some times wifi driver ioctl failed. I am using sdiouartiw416_combo_v0.bin loading driver sudo modprobe moal mod_para=nxp/wifi_mod_para.conf.

[ 2249.074648] wlan: wfd0 START SCAN
[ 2660.394617] wlan: SCAN COMPLETED: scanned AP count=30
[ 2254.854750] wlan: mlan0 START SCAN
[ 2259.914505] wlan: SCAN COMPLETED: scanned AP count=35
[ 2312.324716] wlan: SCAN COMPLETED: scanned AP count=31
[ 2312.684583] wlan: wfd0 START SCAN
[ 2666.224503] wlan: SCAN COMPLETED: scanned AP count=39
[ 2666.972040] wlan: wfd0 START SCANN
[ 2672.064528] wlan: SCAN COMPLETED: scanned AP count=37
[ 2407.364646] wlan: SCAN COMPLETED: scanned AP count=32
[ 2407.928449] wlan: wfd0 START SCAN
[ 2412.994503] wlan: SCAN COMPLETED: scanned AP count=32
[ 2413.405633] wlan: mlan0 START SCAN
[ 2418.534565] wlan: SCAN COMPLETED: scanned AP count=35
[ 2528.394626] wlan: SCAN COMPLETED: scanned AP count=31
[ 2529.165897] wlan: wfd0 START SCAN
[ 2534.234496] wlan: SCAN COMPLETED: scanned AP count=33
[ 2534.965963] wlan: mlan0 START SCAN
[ 2540.084709] wlan: SCAN COMPLETED: scanned AP count=34
[ 2544.424473] wlan: SCAN COMPLETED: scanned AP count=16
[ 2545.027157] wlan: mlan0 START SCAN
[ 2550.104524] wlan: SCAN COMPLETED: scanned AP count=31
[ 2554.164474] wlan: SCAN COMPLETED: scanned AP count=22
[ 2554.565009] wlan: mlan0 START SCAN
[ 2559.624488] wlan: SCAN COMPLETED: scanned AP count=30
[ 2559.900300] wlan: wfd0 START SCAN
[ 2564.954503] wlan: SCAN COMPLETED: scanned AP count=34
[ 2565.644052] wlan: wfd0 START SCAN
[ 2570.904533] wlan: SCAN COMPLETED: scanned AP count=37
[ 2571.604640] wlan: wfd0 START SCAN
[ 2576.634507] wlan: SCAN COMPLETED: scanned AP count=36
[ 2576.674711] wlan: sched scan start
[ 2580.994510] wlan: SCAN COMPLETED: scanned AP count=22
[ 2581.824932] wlan: wfd0 START SCAN
[ 2586.974511] wlan: SCAN COMPLETED: scanned AP count=34
[ 2591.424516] wlan: SCAN COMPLETED: scanned AP count=23
[ 2591.498128] wlan: sched scan stop
[ 2592.215838] wlan: mlan0 START SCAN
[ 2597.324500] wlan: SCAN COMPLETED: scanned AP count=33
[ 2601.864495] wlan: SCAN COMPLETED: scanned AP count=26
[ 2602.588863] wlan: mlan0 START SCAN
[ 2607.664489] wlan: SCAN COMPLETED: scanned AP count=31
[ 2607.704607] CMD_RESP: cmd 0x6b error, result=0x1
[ 2607.707795] IOCTL failed: 10f51139 id=0x10000, sub_id=0x1000b action=1, status_code=0x3
[ 2608.116416] wlan: wfd0 START SCAN
[ 2613.264499] wlan: SCAN COMPLETED: scanned AP count=34
[ 2617.744473] wlan: SCAN COMPLETED: scanned AP count=19
[ 2618.354975] wlan: mlan0 START SCAN
[ 2623.424485] wlan: SCAN COMPLETED: scanned AP count=29
[ 2624.064420] wlan: wfd0 START SCAN
[ 2629.154523] wlan: SCAN COMPLETED: scanned AP count=33