The FW crashed issue is still exist in Generic_PCIE-WLAN-UART-BT-8997-LNX_6_6_3-IMX8-16.92.21.p119.2-16.92.21.p119.2-MM6X16437.P3-GPL.
follow previous case:
and reopen by this case.
Hi, @yao_feng
Can you please help to provide the dmesg+ fw_dump +drv_dump logs based on the new release?
Please pay attention to the parameter: drvdbg = 0xa0037 when load drivers and make sure FW dump is available. After issue is occurred, directly export the logs without rebooting your device. Once device is reboot, FW dump will be lost.
Also do not use below command before export the failed logs because below command will automatically trigger another FW dump and it will override the real failed one.
echo debug_dump > /proc/mwlan/adapter0/config
Best regards,
Christine.
Hi, @ArthurC
Thanks for your reply.
I am checking with our internal team, will share with you once have any updates.
Best regards,
Christine.
Hi @ArthurC
Could you please help to share with NXP:
dmesg
fw_dump
drv_dump
based on new release.
parameter settings: drvdbg = 0xa0037
After issue is occurred, directly export the logs without rebooting your device. Once device is reboot, FW dump will be lost.
!!! Don't do below before export logs. it will overwrite the old one.
echo debug_dump > /proc/mwlan/adapter0/config
Thank you very much.
Hello @yao_feng ,
During the test thease days as 88W8997 Wi-Fi driver probing with parameter "drvdbg = 0xa0037"
We found the FW Generic_PCIE-WLAN-UART-BT-8997-LNX_6_6_3-IMX8-16.92.21.p119.2-16.92.21.p119.2-MM6X16437.P3-GPL which will cause host system hanging & crashed.
So we can't dump the internal logs by following command.
echo debug_dump > /proc/mwlan/adapter0/config
What's the power consumption about the module 88W8997 caused by FW Generic_PCIE-WLAN-UART-BT-8997-LNX_6_6_3-IMX8-16.92.21.p119.2-16.92.21.p119.2-MM6X16437.P3-GPL ?
The dmesg about driver probed with parameter "drvdbg = 0xa0037" from start to host system hanging & crashed is as attached.
Please to analysis and fix issue.
Hello @yao_feng ,
The bring-up command:
modprobe moal mod_para=nxp/wifi_mod_para.conf drvdbg=0xa0037
There is no WiFi FW hang message because the whole system have been hang by the module 88W8997 with FW Generic_PCIE-WLAN-UART-BT-8997-LNX_6_6_3-IMX8-16.92.21.p119.2-16.92.21.p119.2-MM6X16437.P3-GPL.
Worse than previous version!
That's the current final dmesg log record to the log file stored to EMMC.
It's caused every time in 2.4G WiFi connection.
Hello @yao_feng,
Without debug level setting, it's on working but the 88W8997 will be caused FW crashing.
Our used wifi_mod_para.conf is as attached.
Hi @Christine_Li
drvdbg=0xa0037 seems cause system hang and can't test normally, any suggestion or other settings is ok for FW dump correctly?
The driver parameters settings are below
Please help to review if its ok?
PCIE8997 = {
cfg80211_wext=0xf
max_vir_bss=1
cal_data_cfg=none
ps_mode=1
auto_ds=1
host_mlme=1
fw_name=nxp/pcie8997_wlan_v4.bin
sta_name=wlan
drv_mode=3
}
Thanks.
Hi, @ArthurC
Can you please have a try with drvdbg=0x20037?
At the same time, I will double confirm with our internal team whether Q1-24 release surely include the fix of this issue as promised before.
Best regards,
Christine.
Hello @Christine_Li,
Yes, I have tried for 10 times.
The FW with drvdbg=0x20037 in 2.4G connection caused whole system hang everytimes.
Hi, @ArthurC
So for both drvdbg=0x20037 and drvdbg=0xa0037, in 2.4G connection , will cause whole system hang every time. But without drvdbg parameter, system will not hang but still have FW crash.
Am I right?
Best regards,
Christine.
Hello @Christine_Li ,
The FW crashed dmesg log about probe without both drvdbg=0x20037 and drvdbg=0xa0037 is as attached.
Hi @ArthurC
Could you please help to try
1. Replace FW to combo one: pcieuart8997_combo_v4.bin with drvdbg=0xa0037
2. Set
ps_mode=2
auto_ds=2
with drvdbg=0xa0037
= = =
in my experience, drvdbg level will not cause system hang, did you upgrade i.MX8 image or not?
Hello @yao_feng ,
With pcieuart8997_combo_v4.bin, the default uart speed is 115200.
It is out of our requirement about audio play via A2DP.
As we known, if we need Bluetooth uart working in baud 3M.
There are flows including killing hciattach.
It's not OK for production.
So we will not use pcieuart8997_combo_v4.bin.
Hi, @ArthurC
Thanks for your logs and information.
I checked internally about this release, our internal team mentioned they have raised a JIRA ticket and fixes have been merged. So it might be a new issue because of some other submits.
According to the given logs, we will continue to track.
Also about the issue that drvdbg=0x20037 and drvdbg=0xa0037 will cause system hang, I will report internally and may try to reproduce locally.
Once have any feedback, I will sync with you at the first time.
Best regards,
Christine.
Hi, @ArthurC
May I ask about the issue that drvdbg=0x20037 and drvdbg=0xa0037 will cause system hang, need to start iperf in STA mode connect with 2.4G AP and Bluetooth Audio at the same time then can reproduce?
About how long this issue will happen on your side?
I am setting up the environment to reproduce this issue.
Best regards,
Christine.
Hello @Christine_Li,
May I ask about the issue that drvdbg=0x20037 and drvdbg=0xa0037 will cause system hang, need to start iperf in STA mode connect with 2.4G AP and Bluetooth Audio at the same time then can reproduce?
-> Yes, BTW, please use Bluetooth uart working in baud 3M, first.
About how long this issue will happen on your side?
-> After 5 minutes.
Thank you for your help.