CRITICAL: WiFi CMD_RESP 0xf2 'block in pre_asleep' Errors on imx8mm-jaguar-sentai

[ajlennon]

CRITICAL: WiFi CMD_RESP 0xf2 "block in pre_asleep" Errors

Priority: CRITICAL 🚨

Summary

The imx8mm-jaguar-sentai board is experiencing persistent WiFi errors with CMD_RESP: 0xf2 block in pre_asleep! messages that cause network connectivity issues and system instability.

Environment

• Board: imx8mm-jaguar-sentai
• Branch: main-jaguar-sentai-dev-v95
• Build: 5.0.9-1111-95 (IMAGE_VERSION=1111)
• WiFi Module: NXP IW612 (SDIW612)
• Error Pattern: Continuous CMD_RESP: 0xf2 block in pre_asleep! messages

Problem Description

Error Messages

[   31.609216] CMD_RESP: 0xf2 block in pre_asleep!
[   31.614108] CMD_RESP: 0xf2 block in pre_asleep!
[   31.618927] CMD_RESP: 0xf2 block in pre_asleep!
[   31.623730] CMD_RESP: 0xf2 block in pre_asleep!
[   31.628537] CMD_RESP: 0xf2 block in pre_asleep!

Impact

• Network connectivity becomes unreachable
• System instability
• Board may become unresponsive
• Different from previous CMD_RESP: 0x107 errors

Current Configuration

WiFi Module Parameters (SDIW612 section)

SDIW612 = {
    cfg80211_wext=0xf
    max_vir_bss=1
    cal_data_cfg=none
    ps_mode=0              # Power save disabled
    auto_ds=0              # Auto deep sleep disabled
    host_mlme=1
    drv_mode=1             # STA-only mode
    pm_keep_power=0        # Additional PM disable
    shutdown_hs=0          # Additional PM disable
    fw_name=nxp/sduart_nw61x_v1.bin
}

Investigation History

Previous Issues Resolved

1. CMD_RESP: 0x107 errors - Fixed by disabling ps_mode and auto_ds
2. USB Composite Gadget conflicts - Fixed by disabling USB gadget auto-startup

Current Status

• Power management shows as "off" in iwconfig
• No USB gadget processes running
• WiFi connects but errors persist
• Error code 0xf2 is different from previous 0x107

Potential Root Causes

1. Firmware Issues

• IW612 combo firmware state machine problems
• Firmware version compatibility issues
• Power state transition bugs

2. Driver Configuration

• Additional power management parameters needed
• Driver mode conflicts
• Interrupt handling issues

3. Hardware/Timing Issues

• GPIO power control conflicts
• Clock domain issues
• Race conditions during initialization

4. System Integration

• Interaction with other services
• Kernel module loading order
• Device tree configuration issues

Attempted Fixes

✅ Completed

• Disabled ps_mode=0 and auto_ds=0
• Added pm_keep_power=0 and shutdown_hs=0
• Disabled USB composite gadget auto-startup
• Set drv_mode=1 (STA-only mode)

❌ Still Needed

• Investigate firmware version/compatibility
• Check for additional power management parameters
• Analyze driver initialization sequence
• Review device tree WiFi configuration
• Test with different firmware variants

Debug Information Needed

System Information

# WiFi module info
lsmod | grep -E 'mlan|moal'
cat /sys/module/moal/parameters/*

# Firmware version
dmesg | grep -i firmware

# Device tree WiFi config
find /proc/device-tree -name '*wifi*' -o -name '*sdio*'

# Detailed error context
dmesg | grep -B5 -A5 "CMD_RESP.*0xf2"

Timing Analysis

• Monitor error frequency and patterns
• Check correlation with system events
• Analyze power state transitions

Next Steps

Immediate Actions

1. Firmware Investigation

   • Check if different firmware variant resolves issue
   • Verify firmware loading sequence
   • Test with secure vs non-secure firmware

2. Driver Parameter Analysis

   • Research NXP documentation for additional parameters
   • Test with different driver configurations
   • Check for errata or known issues

3. System Integration Review

   • Analyze service startup order
   • Check for resource conflicts
   • Review power management across system

Long-term Solutions

• Engage with NXP support if needed
• Consider firmware update/patch
• Implement workaround if root cause cannot be resolved

Files Modified

• meta-dynamicdevices-bsp/recipes-bsp/firmware-imx/firmware-nxp-wifi/wifi_mod_para.conf
• meta-dynamicdevices-bsp/conf/machine/imx8mm-jaguar-sentai.conf

Related Issues

• Previous CMD_RESP: 0x107 errors (resolved)
• USB composite gadget conflicts (resolved)
• SPI DMA timeout issues (resolved)

---

This issue is blocking production deployment and requires immediate attention.