#12545 HIGH 13.1.0: mwifiex communication issues when suspending while scanning

[Zarro Boogs per Child]

#12545: mwifiex communication issues when suspending while scanning
--------------------+-------------------------------------------------------
 Reporter:  dsd     |                 Owner:  shep         
     Type:  defect  |                Status:  new          
 Priority:  high    |             Milestone:  13.1.0       
Component:  kernel  |               Version:  not specified
 Keywords:          |           Next_action:  never set    
 Verified:  0       |   Deployment_affected:               
Blockedby:          |              Blocking:               
--------------------+-------------------------------------------------------
 Running 13.1.0 build 29 on XO-4 C1, with
 mwifiex_always_poweroff_on_sleep=n for testing/bug-hunting reasons.

 This command reliably produces bad behaviour for me:

 {{{
 (iwlist eth0 scan &) ; sleep 1; ethtool -s eth0 wol u; echo mem >
 /sys/power/state
 }}}

 Firstly there is a long delay during suspend, which you can see in the
 timestamps.

 {{{
 [  451.353150] PM: Syncing filesystems ... done.
 [  451.488175] Freezing user space processes ... (elapsed 0.02 seconds)
 done.
 [  451.512627] Freezing remaining freezable tasks ... (elapsed 0.01
 seconds) done.
 [  451.558502] dcon_source_switch to DCON
 [  451.601190] olpc-dcon: The DCON has control
 [  451.662705] mmp3_usb_phy_deinit_internal: Deinit usb phy!!!
 [  451.712625] mmc2: dropping power over suspend
 [  451.721034] mmc1: dropping power over suspend
 [  459.581368] mmc0: keeping power over suspend
 [  459.589634] [galcore] enter gpu_suspend
 [  459.597398] [galcore] exit gpu_suspend, return 0
 [  459.605909] PM: suspend of devices complete after 8063.302 msecs
 [  459.615970] PM: late suspend of devices complete after 0.001 msecs
 [  459.626285] PM: noirq suspend of devices complete after 0.001 msecs
 [  459.636497] mmp3_pm_enter_d2
 [  459.636518] before suspend
 }}}

 Secondly, the system resumes immediately (without any obvious explanation
 for why it should have woken up at this time), but suffers another long
 delay during the resume sequence, and presents some error messages.

 {{{
 [  459.668209] after resume
 [  459.675202] PM: noirq resume of devices complete after 0.001 msecs
 [  459.685335] PM: early resume of devices complete after 0.001 msecs
 [  459.695305] [galcore] enter gpu_resume
 [  459.707119] [galcore] exit gpu_resume, return 0
 [  469.730606] mmc0: Timeout waiting for hardware interrupt.
 [  469.739920] mwifiex_sdio mmc0:0001:1: mwifiex_sdio_card_to_host: read
 iomem failed: -1
 [  469.751796] mwifiex_sdio mmc0:0001:1: card_to_host_mpa failed: int
 status=0x3
 [  469.910624] mmp3_usb_phy_init_internal: Init usb phy!!!
 [  469.941458] dcon_source_switch to CPU
 [  470.008932] olpc-dcon: The CPU has control
 [  470.140624] usb 1-1: reset high-speed USB device number 2 using pxau2o-
 ehci
 [  470.411996] PM: resume of devices complete after 10716.817 msecs
 [  470.422078] Restarting tasks ... done.
 }}}

-- 
Ticket URL: <http://dev.laptop.org/ticket/12545>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system