#9836 HIGH 1.5-sof: Invalid opcode in Libertas if_sdio_interrupt() routine

[Zarro Boogs per Child]

#9836: Invalid opcode in Libertas if_sdio_interrupt() routine
--------------------------------+-------------------------------------------
           Reporter:  dsaxena   |       Owner:  dsaxena            
               Type:  defect    |      Status:  new                
           Priority:  high      |   Milestone:  1.5-software-update
          Component:  kernel    |     Version:  1.5-B3             
         Resolution:            |    Keywords:                     
        Next_action:  diagnose  |    Verified:  0                  
Deployment_affected:            |   Blockedby:                     
           Blocking:            |  
--------------------------------+-------------------------------------------
Changes (by cjb):

 * cc: rchokshi (added)


Comment:

 Going to suspend while pingflooding was enough to reproduce this on the
 second suspend -- attaching the full log.  The (B3, ECOs) system
 temporarily came back from resume, and then crashed hard with the
 backlight still dimmed a few seconds later.

 Questions:

  * we first see a timeout waiting for hardware interrupt -- did we fail to
 quiesce some state on the way down?
  * mmc1:0001: error -110 reading SDIO_CCCR_INTx suggests an SD-level
 failure/hang at that point
  * Which line of code is if_sdio_interrupt()+0x3f7?  The kernel's the
 build os63 2.6.31_xo1.5-20091215.1440.1.olpc.9815d58

 We should ask for Marvell's help with this one, too.

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