topic Re: WIFI driver issue IOCTL issue in Wi-Fi® + Bluetooth® + 802.15.4

WIFI driver issue IOCTL issue

masateesh — Tue, 07 May 2024 09:35:43 GMT

Hi Team,

I am facing an issue wifi driver using marvell driver. driver -> marvell,sd8978

sdiouartiw416_combo_v0.bin wifi_mod_para.conf

root@ST-CUSTOMBOARD :/lib/firmware/nxp# cat wifi_mod_para.conf
SDIW416 = {
cfg80211_wext=0xf
max_vir_bss=1
cal_data_cfg=none
ps_mode=1
auto_ds=1
host_mlme=1
fw_name=nxp/sdiouartiw416_combo_v0.bin
}

kernel version - 5.15.67

Below I have attached full dmeg log.

[ 103.844811] CMD_RESP: cmd 0x6b error, result=0x1
[ 103.848002] IOCTL failed: c38f07ff id=0x10000, sub_id=0x1000b action=1, status_code=0x3

[ 1699.006444] IOCTL failed: c2334065 id=0x10000, sub_id=0x10003 action=1, status_code=0x80000007

sub_id -> changing 0x10003 & 0x1000b

status code -> 0x3 , 0x80000007

I am loading this wifi module using systemd service during bootup time.

ExecStart=sudo modprobe moal mod_para=nxp/wifi_mod_para.conf

Regards,

Sateesh

Re: WIFI driver issue IOCTL issue

Christine_Li — Wed, 08 May 2024 07:19:11 GMT

Hi, @masateesh

Thanks for creating case to us.

From your given attached logs, I saw that our IW416 driver has been loaded successfully.

======

[ 34.464949] Register NXP 802.11 Adapter mlan0
[ 34.519196] Register NXP 802.11 Adapter uap0
[ 34.630158] Register NXP 802.11 Adapter wfd0
[ 34.633100] wlan: version = SDIW416---16.92.21.p55.3-MM5X16366.p5-GPL-(FP92)
[ 34.764807] Set REG 0x80002328: 0x13d57 slew_rate=3
[ 34.799409] wlan: Register to Bus Driver Done
[ 34.802382] wlan: Driver loaded successfully

=======

But logs are cut off, please send to me a full dmesg logs for further tracking.

By the way, can you let me know what did you do before this issue occurred? If possible, please share to me your detailed steps.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Fri, 10 May 2024 11:10:11 GMT

Hello Christine,

I have created systemd servcie. As I mentioned below. once I login I have observed this issue. Previosly I have attached dmesg log

[Unit]
Description="Start WIFI"

[Service]
ExecStart=sudo modprobe moal mod_para=nxp/wifi_mod_para.conf

[Install]
WantedBy=multi-user.target

In my yocto environment I have created linux-firmware directory.

SDIW416 = {
cfg80211_wext=0xf
max_vir_bss=1
cal_data_cfg=none
ps_mode=1
auto_ds=1
host_mlme=1
fw_name=nxp/sdiouartiw416_combo_v0.bin
}

Additionally I not modified.

Regards,

masateesh

Re: WIFI driver issue IOCTL issue

Christine_Li — Wed, 08 May 2024 09:51:13 GMT

Hi， @masateesh

Thanks for your reply.

But your previous dmesg log is cut off.

It only has 418 lines, and after below line, there is no anything.

=======

[ 77.670774] wlan: mlan0 START SCAN
[ 82.814630] wlan: SCAN COMPLETED: scanned AP count=24

=========

Please help to check again and share me your full dmesg logs.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Wed, 08 May 2024 11:32:22 GMT

Hi Christine,

I have attached complete log could you please check it.

Regards,

masateesh

Re: WIFI driver issue IOCTL issue

Christine_Li — Thu, 09 May 2024 08:14:21 GMT

Hi, @masateesh

Thanks for your reply.

From your given logs, I think you have loaded Wi-Fi driver and FW successfully and also Wi-Fi has been working properly.

I think the ioctl failed logs doesn't influence Wi-Fi function. It can scan and can connect with AP successfully.

But you can have a try with below commands to see whether can avoid these ioctl failed prints:

=========

root@imx8mnevk:~# systemctl status connman.service //To check whether connman.service is enabled
* connman.service - Connection service
Loaded: loaded (/lib/systemd/system/connman.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Tue 2024-04-02 07:37:24 UTC; 35min ago
Process: 383 ExecStart=/usr/sbin/connmand -n (code=exited, status=0/SUCCESS)
Main PID: 383 (code=exited, status=0/SUCCESS)

Apr 02 07:37:24 imx8mnevk connmand[383]: Remove interface uap0 [ wifi ]
Apr 02 07:37:24 imx8mnevk connmand[383]: Remove interface mlan0 [ wifi ]
Apr 02 07:37:24 imx8mnevk connmand[383]: Remove interface wfd0 [ wifi ]
Apr 02 07:37:24 imx8mnevk connmand[383]: eth0 {remove} index 2
Apr 02 07:37:24 imx8mnevk connmand[383]: uap0 {remove} index 4
Apr 02 07:37:24 imx8mnevk connmand[383]: mlan0 {remove} index 3
Apr 02 07:37:24 imx8mnevk connmand[383]: wfd0 {remove} index 5
Apr 02 07:37:24 imx8mnevk connmand[383]: Exit
Apr 02 07:37:24 imx8mnevk systemd[1]: connman.service: Deactivated successfully.
Apr 02 07:37:24 imx8mnevk systemd[1]: Stopped Connection service.
root@imx8mnevk:~# systemctl stop connman.service //To stop this service

After stop connman.service, please do not use connmanctl to connect AP.

Please do not hesitate to reply me if have any other concerns.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Thu, 09 May 2024 12:05:25 GMT

Hi Christine,

I see wifi is working.

But below issue's I have observed. I am guessing moal driver some patch may required. I see same issue in this forum IOCTL failed somebody mentioned he have corrected DRAM configuration then issue fixed mentioned. I just want to know the clear on this.

Is their any patch is required please provide I will add those changes locally and built mlan, moal kernel modules.

[ 754.344729] InterpretIE: Error in processing IE, bytes left < IE length
[ 754.349925] EXT_SCAN: wlan_interpret_bss_desc_with_ie returned error
[ 755.224629] wlan: SCAN COMPLETED: scanned AP count=16
[ 755.594619] InterpretIE: Error in processing IE, bytes left < IE length
[ 755.599816] EXT_SCAN: wlan_interpret_bss_desc_with_ie returned error
[ 755.606259] wlan: SCAN COMPLETED: scanned AP count=0
[ 755.614841] bssid not find in scan list
[ 756.119045] wlan: mlan0 START SCAN
[ 758.884780] InterpretIE: Error in processing IE, bytes left < IE length
[ 758.889976] EXT_SCAN: wlan_interpret_bss_desc_with_ie returned error
[ 761.364655] wlan: SCAN COMPLETED: scanned AP count=11
[ 761.914752] InterpretIE: Error in processing IE, bytes left < IE length
[ 761.919950] EXT_SCAN: wlan_interpret_bss_desc_with_ie returned error
[ 761.926393] wlan: SCAN COMPLETED: scanned AP count=0
[ 761.934841] bssid not find in scan list
[ 762.939624] wlan: mlan0 START SCAN
[ 765.030731] IOCTL failed: 1ebea63f id=0x10000, sub_id=0x10003 action=1, status_code=0x80000007
[ 765.124690] wlan: SCAN COMPLETED: scanned AP count=0
[ 765.474778] InterpretIE: Error in processing IE, bytes left < IE length
[ 765.479978] EXT_SCAN: wlan_interpret_bss_desc_with_ie returned error
[ 765.486435] wlan: SCAN COMPLETED: scanned AP count=0
[ 765.494878] bssid not find in scan list
[ 765.805067] wlan: mlan0 START SCAN
[ 770.104956] InterpretIE: Error in processing IE, bytes left < IE length
[ 770.110156] EXT_SCAN: wlan_interpret_bss_desc_with_ie returned error
[ 770.984682] wlan: SCAN COMPLETED: scanned AP count=24
[ 772.324877] wlan: mlan0 START SCAN
[ 777.544645] wlan: SCAN COMPLETED: scanned AP count=25
[ 778.184800] wlan: HostMlme mlan0 send auth to bssid 5e:XX:XX:XX:96:4e
[ 778.214730] mlan0:
[ 778.214763] wlan: HostMlme Auth received from 5e:XX:XX:XX:96:4e
[ 778.275226] wlan: HostMlme mlan0 Connected to bssid 5e:XX:XX:XX:96:4e successfully
[ 778.317151] mlan0:
[ 778.317181] wlan: Send EAPOL pkt to 5e:XX:XX:XX:96:4e
[ 778.337371] mlan0:
[ 778.337401] wlan: Send EAPOL pkt to 5e:XX:XX:XX:96:4e
[ 778.375260] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready
[ 778.488443] woal_cfg80211_set_rekey_data return: gtk_rekey_offload is DISABLE
[ 785.064712] wlan: SCAN COMPLETED: scanned AP count=17
[ 786.644535] wlan: wfd0 START SCAN

Re: WIFI driver issue IOCTL issue

Christine_Li — Fri, 10 May 2024 01:40:00 GMT

Hi, @masateesh

Thanks for your reply.

From the given logs, I think IW416 is working as a STA and has been connected successfully with your AP.

[ 778.184800] wlan: HostMlme mlan0 send auth to bssid 5e:XX:XX:XX:96:4e
[ 778.214730] mlan0:
[ 778.214763] wlan: HostMlme Auth received from 5e:XX:XX:XX:96:4e
[ 778.275226] wlan: HostMlme mlan0 Connected to bssid 5e:XX:XX:XX:96:4e successfully
[ 778.317151] mlan0:
[ 778.317181] wlan: Send EAPOL pkt to 5e:XX:XX:XX:96:4e
[ 778.337371] mlan0:
[ 778.337401] wlan: Send EAPOL pkt to 5e:XX:XX:XX:96:4e
[ 778.375260] IPv6: ADDRCONF(NETDEV_CHANGE): mlan0: link becomes ready

I don't think there is issue during connection.

And can you please let me know whether my previous comment mentioned that disable connman service is helpful or not?

Besides, you can also update to our latest driver + FW combinations to see whether is helpful. I believe there must some fixes in our latest release.

Your current

wlan: version = SDIW416---16.92.21.p55.3-MM5X16366.p5-GPL-(FP92)

driver version:MM5X16366.p5

FW version:16.92.21.p55.3

Our latest

driver version: MM6X16437.P3

FW version: 16.92.21.p119.2

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Fri, 10 May 2024 05:35:27 GMT

Hi Christine,

Actually I am using wpa_supplicant & iw , I am not using connman.

Can you share me latest binary available link.

Regards,

Sateesh

Re: WIFI driver issue IOCTL issue

Christine_Li — Fri, 10 May 2024 07:44:42 GMT

Hi, @masateesh

Thanks for your reply.

Connman service might be started automatically in Linux OS.

Our latest open source

driver link:

https://github.com/nxp-imx/mwifiex/tree/lf-6.6.3_1.0.0

FW link:

https://github.com/nxp-imx/imx-firmware/tree/lf-6.6.3_1.0.0/nxp/FwImage_IW416_SD

Please let me know if you have another queries.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Fri, 10 May 2024 07:47:15 GMT

Our kernel verison 5.15.67. is this lf-lf-6.6.3_1.0.0 will work ?

Re: WIFI driver issue IOCTL issue

Christine_Li — Fri, 10 May 2024 08:07:30 GMT

Hi, @masateesh

Sure, this driver supports Linux kernel from 2.6.32 to 6.6.2.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Fri, 10 May 2024 09:37:22 GMT

Hi Christine,

I have successfully compiled and generated moal.ko & mlan.ko

these modules I have placed /lib/modules/5.15.67/extra/

& /lib/firmware/nxp/sdiouartiw416_combo_v0.bin placed wifi_mod_para.conf

after I used modprobe moal mod_para=nxp/wifi_mod_para.conf to load module But I have observed an issue.

modprobe: ERROR: could not insert 'moal': Invalid argument

Even I tried insmod moal.ko mod_para=nxp/wifi_mod_para.conf

insmod: ERROR: could not load module moal.ko: No such file or directory.

Regards,

Sateesh

Re: WIFI driver issue IOCTL issue

Christine_Li — Fri, 10 May 2024 09:48:35 GMT

Hi, @masateesh

Please make sure you are using the correct Linux kernel 5.15.67 tool chain and related source environment path when you compile Wi-Fi driver.

Also the KERNELDIR should be correct.(With Linux kernel 5.15.67 after compiled kernel Image).

For example:

KERNELDIR ?= ~/linux-source-code/L5.15.67_1.0.0/linux-imx

source /opt/fsl-imx-xwayland/5.4-zeus/environment-setup-aarch64-poky-linux

make

One of above info is incorrect, it will cause this error.

You can also use:

file mlan.ko

this command to check what is the mlan.ko file type to see whether is correct.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Fri, 10 May 2024 10:29:41 GMT

Thank you Christine for quick response.

Actually previous my binary not fully copied. due to this reason I have faced problem.

[ 4554.298625] InterpretIE: Error in processing IE, bytes left < IE length
[ 4554.303883] EXT_SCAN: wlan_interpret_bss_desc_with_ie returned error
[ 4555.178670] wlan: SCAN COMPLETED: scanned AP count=28
[ 4555.945174] wlan: wfd0 START SCAN
[ 4561.879643] wlan: SCAN COMPLETED: scanned AP count=32
[ 4570.058042] wlan: uap0 START SCAN
[ 4575.151886] wlan: SCAN COMPLETED: scanned AP count=27
[ 4576.022132] wlan: wfd0 START SCAN
[ 4582.053159] wlan: SCAN COMPLETED: scanned AP count=29
[ 4599.062539] wlan: uap0 START SCAN
[ 4604.227542] wlan: SCAN COMPLETED: scanned AP count=27
[ 4605.007728] wlan: wfd0 START SCAN
[ 4610.928930] wlan: SCAN COMPLETED: scanned AP count=30
[ 4642.072688] wlan: uap0 START SCAN
[ 4647.336836] wlan: SCAN COMPLETED: scanned AP count=26
[ 4647.967868] wlan: wfd0 START SCAN
[ 4653.938295] wlan: SCAN COMPLETED: scanned AP count=28
[ 4706.156640] wlan: uap0 START SCAN
[ 4711.351195] wlan: SCAN COMPLETED: scanned AP count=24
[ 4712.152203] wlan: wfd0 START SCAN
[ 4718.132740] wlan: SCAN COMPLETED: scanned AP count=27
MP.appl@BCEA1-864950060008118:/home/root# [ 4801.110701] wlan: uap0 START SCAN
[ 4806.262691] wlan: SCAN COMPLETED: scanned AP count=21
[ 4806.452959] wlan: wfd0 START SCAN
[ 4812.454083] wlan: SCAN COMPLETED: scanned AP count=22
[ 4922.306714] wlan: uap0 START SCAN
[ 4925.123819] IOCTL failed: 07605cf1 id=0x10000, sub_id=0x10003 action=1, status_code=0x80000007
I have updated latest binaries but still I see this above issue.

Re: WIFI driver issue IOCTL issue

Christine_Li — Sat, 11 May 2024 02:18:11 GMT

Hi, @masateesh

Did you only update the FW to latest one? or also update the driver to latest one?

Can you please help to provide me your full dmesg logs like before?

And, as I mentioned before, I don't think these IOCTL prints have influence to Wi-Fi function.

Also, in your previous comments, I checked your logs, it show that connection has been successfully created.

These IOCTL prints means there are some commands which sent from upper application layer, our FW side doesn't support to response. But actually it doesn't effect Wi-Fi function.

Before we also received similar cases from other customers, and customers also accepted our ideas.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

masateesh — Tue, 14 May 2024 05:09:25 GMT

I have updated both kernel module & firmware binary. Still I have observed same problem.

Re: WIFI driver issue IOCTL issue

Christine_Li — Tue, 14 May 2024 06:24:04 GMT

Hi, @masateesh

Please provide me your full dmesg log, Thanks.

Best regards,

Christine.

Re: WIFI driver issue IOCTL issue

ADblue — Mon, 03 Jun 2024 11:12:52 GMT

Is there any solution for this issue since we have as the same problem.

Re: WIFI driver issue IOCTL issue

Christine_Li — Tue, 04 Jun 2024 02:14:47 GMT

Hi, @ADblue

This IOCTL error doesn't have influence with Wi-Fi function. You can check whether your Wi-Fi can work well.

And also only from the scenario, we can not say it is same issue.

Still, This thread is long time ago.

If you have similar issue, please create a new case to us and attach your full logs and wpa_supplicant.conf, we will follow on your new case.

Have a nice day~

Best regards,

Christine.