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 zecke):

 Debugging hint:
   - Compile a6k as module make it autoload
   - If CPU is eaten unload the module

 Hypothesis:
   - events/0 is executing the work queue of the hcd s3c implementation of
 "Openmoko" (glue)
   - interrupts will continue but the cpu will not be busy anymore

 What would be interesting:
   - loading the module again (assuming the hcd s3c implementation is doing
 a reset)
   - What happens with the interrupts and the load
   - Maybe even restart connman


 Possible outcomes:
   - With reload/reset interrupts come in and events/0 is busy => firmware
   - With reload/reset interrupts are normal => our hcd glue


 who is willing to do what is necessary?

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