Opened 4 years ago

Closed 4 years ago

#12569 closed defect (duplicate)

mwifiex/8787 non-functional on resume after powered suspend, with "mwifiex_sdio mmc0:0001:1: GET_CMD_NODE: cmd node not available" kernel error message

Reported by: shep Owned by: shep
Priority: high Milestone: 13.1.0
Component: kernel Version: Development source as of this date
Keywords: XO-4 8787 WLAN suspend Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: diagnose
Verified: no


While testing mwifiex/8787 suspend resume with wake-on-lan wakeups over the last couple of days (using kernel a92e022840e7e044fc9a45003f0772314a308191 ), I have twice had the mwifiex/8787 wireless interface fail to work after the resume (and continue to fail to work after subsequent resumes), with the following error messages appearing on the console on resume:

[ 1716.275081] mwifiex_sdio mmc0:0001:1: GET_CMD_NODE: cmd node not available
[ 1716.275087] mwifiex_sdio mmc0:0001:1: PREP_CMD: no free cmd node

I did manage to recover use of the wireless interface after one such failure by stopping my suspend loop and forcing an unpowered suspend with:

bash-4.2# echo 1 | tee /sys/module/mwifiex_sdio/parameters/mwifiex_always_poweroff_on_sleep 
bash-4.2# rtcwake -m mem -s 5
bash-4.2# echo 0 | tee /sys/module/mwifiex_sdio/parameters/mwifiex_always_poweroff_on_sleep

Change History (3)

comment:1 Changed 4 years ago by dsd

  • Milestone changed from Not Triaged to 13.1.0
  • Priority changed from normal to high

comment:2 Changed 4 years ago by wad

  • Action Needed changed from never set to diagnose
  • Keywords XO-4 8787 WLAN suspend added

I verified that this is fixed by doing an unpowered suspend of the WLAN card. This bug is blocking further WOL testing, I've seen it twice in a day when testing five laptops.

Logged with Marvell as ticket #479050.

comment:3 Changed 4 years ago by dsd

  • Resolution set to duplicate
  • Status changed from new to closed

This has not been seen since we fixed #12573. Assuming it is the same bug just with a different error message as a result.

Note: See TracTickets for help on using tickets.