88w9098 association and IOCTL failed, build p126

[CupOfTea]

Using using the 88w9098 driver 17.68.1.p126.15 we are observing association and IOCTL errors as shown in the log below. The error states don't seem to be persistent.

The association failed error 0xfffc seems to indicate "Timeout waiting for AP response".

The failing IOCTL seems to be:
wlan_src/mlan/mlan_fw.h:#define HostCmd_CMD_TX_AMPDU_PROT_MODE 0x0263

Are these known issues?

We don't see this with p136.54. If the issue is known and in the public code and not in the firmware binary, then we would like to backport the change to p126.

Errors in log:

Aug 16 00:30:10 dh100 kernel: wlan: SCAN COMPLETED: scanned AP count=49
Aug 16 00:30:10 dh100 systemd-journald[239]: Forwarding to syslog missed 3 messages.
Aug 16 00:30:12 dh100 kernel: ASSOC_RESP: Association Failed, status code = 1, error = 0xfffc, a_id = 0xffff (POSSIBLY HERE?)
Aug 16 00:30:12 dh100 kernel: IOCTL failed: 00000000c1851a4b id=0x20000, sub_id=0x20001 action=1, status_code=0xfffc0001
Aug 16 00:30:18 dh100 kernel: wlan: SCAN COMPLETED: scanned AP count=42
Aug 16 00:30:24 dh100 kernel: CMD_RESP: cmd 0x107 error, result=0x4
Aug 16 00:30:24 dh100 kernel: IOCTL failed: 000000002b455603 id=0x10000, sub_id=0x10003 action=1, status_code=0x8000000a
Aug 16 00:30:29 dh100 kernel: CMD_RESP: cmd 0x107 error, result=0x4
Aug 16 00:30:29 dh100 kernel: IOCTL failed: 0000000087478cbb id=0x10000, sub_id=0x10003 action=1, status_code=0x8000000a
Aug 16 00:30:36 dh100 kernel: wlan: SCAN COMPLETED: scanned AP count=43
Aug 16 00:30:44 dh100 kernel: wlan: SCAN COMPLETED: scanned AP count=41
Aug 16 00:30:44 dh100 systemd-networkd[346]: sta0: Gained carrier
Aug 16 00:30:44 dh100 systemd-journald[239]: Forwarding to syslog missed 1 messages.
Aug 16 00:30:44 dh100 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): sta0: link becomes ready
Aug 16 00:30:44 dh100 systemd-networkd[346]: sta0: Lost carrier
Aug 16 00:30:44 dh100 systemd-networkd[346]: sta0: Kernel removed an address we don't remember: fe80::4ae7:daff:fe25:6266/64 (valid forever), ignoring.
Aug 16 00:30:47 dh100 kernel: ap0: 
Aug 16 00:30:47 dh100 kernel: wlan: EVENT: MICRO_AP_STA_ASSOC 68:XX:XX:XX:90:12
Aug 16 00:30:50 dh100 kernel: CMD_RESP: cmd 0x107 error, result=0x4
Aug 16 00:30:50 dh100 kernel: IOCTL failed: 000000005534c0b7 id=0x10000, sub_id=0x10003 action=1, status_code=0x8000000a
Aug 16 00:30:51 dh100 udhcpd[810]: udhcpd: sending OFFER to 192.168.4.59
Aug 16 00:30:51 dh100 udhcpd[810]: udhcpd: sending ACK to 192.168.4.5 

[CupOfTea]

The problem is that p136.54 has a connection problem. I've created a new post for that issue: https://community.nxp.com/t5/i-MX-Processors/88w9098-device-connection-problem-with-p136-54/m-p/1706...

Overall, p136.54 doesn't cause the same errors as p126.15 does, yet not having the connection issue is what makes 126.15 the better driver (from our perspective).

[Christine_Li · Accepted solution]

Hi, @CupOfTea 

Because the 17.68.1.p126.15 driver is too old, and there are many issues on this driver.(You can see the newer driver's release note.)

We strongly suggest you to use the latest driver version: p136.54.

Between 17.68.1.p126.15 and p136.54, we have a lot of fixes. Even you resolve this issue by modifying driver(I am not sure whether is it driver side or FW side issue right now.) You may met other known issue on  17.68.1.p126.15 driver.

So if it is acceptable to use p136.54 for you, it will be better choice.

Best regards,

Christine.