#9744 HIGH 1.5-sof: XO-1.5 WLAN errors after multiple suspend/resumes

[Zarro Boogs per Child]

#9744: XO-1.5 WLAN errors after multiple suspend/resumes
--------------------------------+-------------------------------------------
           Reporter:  wad       |       Owner:  mbletsas                         
               Type:  defect    |      Status:  new                              
           Priority:  high      |   Milestone:  1.5-software-beta                
          Component:  wireless  |     Version:  Development build as of this date
         Resolution:            |    Keywords:  XO-1.5 WLAN                      
        Next_action:  diagnose  |    Verified:  0                                
Deployment_affected:            |   Blockedby:                                   
           Blocking:            |  
--------------------------------+-------------------------------------------
Changes (by dsaxena):

 * cc: cjb, edmcnierney (added)


Comment:

 I've been running lots of S/R loops and grabbing the console logs to see
 if I can find a pattern and I've got some info but really need to look at
 what is happening on the firmware side and co-relate it to the kernel to
 move forward.

 One thing I have determined is that every time that the WLAN card stops
 responding, we see the following message very close to when the WLAN
 starts miss-behaving. Either we'll get a timeout on CMD 0x0006 (SCAN) and
 then requeue it and later start seeing the list_add() and list_del()
 messages, or we'll see the following and then immediately see the list
 corruption warning.

 {{{
 [  383.770098] mmc2: Timeout waiting for hardware interrupt.
 [  383.775777] sdhci: ============== REGISTER DUMP ==============
 [  383.780085] sdhci: Sys addr: 0x00000000 | Version:  0x00000000
 [  383.780085] sdhci: Blk size: 0x00000000 | Blk cnt:  0x00000000
 [  383.780085] sdhci: Argument: 0x10004000 | Trn mode: 0x00000000
 [  383.780085] sdhci: Present:  0x01f70000 | Host ctl: 0x00000001
 [  383.780085] sdhci: Power:    0x0000000f | Blk gap:  0x00000000
 [  383.780085] sdhci: Wake-up:  0x00000000 | Clock:    0x00000107
 [  383.780085] sdhci: Timeout:  0x00000000 | Int stat: 0x00000000
 [  383.780085] sdhci: Int enab: 0x00ff0103 | Sig enab: 0x00ff0103
 [  383.780085] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
 [  383.780085] sdhci: Caps:     0x056030b0 | Max curr: 0x00f001f0
 [  383.780085] sdhci: ===========================================
 [  383.851333] mmc2:0001:1: resume: we're back
 }}}

 Overall, what we're seeing with WLAN is very similar to #7458 on XO-1
 except that it happens much quicker (which does make it easier to
 reproduce and debug on the plus side).

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