#12569 NORM Not Tri: 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
Zarro Boogs per Child
bugtracker at laptop.org
Wed Feb 20 12:48:39 EST 2013
#12569: 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
--------------------+-------------------------------------------------------
Reporter: shep | Owner: shep
Type: defect | Status: new
Priority: normal | Milestone: Not Triaged
Component: kernel | Version: Development source as of this date
Keywords: | Next_action: never set
Verified: 0 | Deployment_affected:
Blockedby: | Blocking:
--------------------+-------------------------------------------------------
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
}}}
--
Ticket URL: <http://dev.laptop.org/ticket/12569>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list