Openmoko Bug #1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu

[Openmoko Public Trac]

#1597: after a long suspend time, kernel thread events/0 sits eating 30% cpu
--------------------------------+-------------------------------------------
    Reporter:  raster           |        Owner:  zecke     
        Type:  defect           |       Status:  in_testing
    Priority:  normal           |    Milestone:            
   Component:  System Software  |      Version:            
    Severity:  major            |   Resolution:            
    Keywords:                   |    Blockedby:            
Reproducible:                   |     Blocking:            
--------------------------------+-------------------------------------------

Comment(by andy):

 ar6k doesn't work as it is when compiled as a module.  The stack doesn't
 pick up that it exists on module insertion.

 Having WLAN stuff as a module gives some nice opportunity to recover from
 this and firmware / stack problems without reboot, it also enables power
 saving stuff too.

 If Werner can put ar6k on normal stack, maybe it can detect "insertion"
 properly and we can use the whole thing as a module, that will be another
 advantage of the change.


 Attempts to use Linux SPI stack with interrupt lockout are doomed, these
 are the source of the dmesg traffic.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/1597#comment:40>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac