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:  closed
    Priority:  normal           |    Milestone:        
   Component:  System Software  |      Version:        
    Severity:  major            |   Resolution:  fixed 
    Keywords:                   |     Haspatch:  0     
   Blockedby:                   |    Estimated:        
 Patchreview:                   |     Blocking:        
Reproducible:                   |  
--------------------------------+-------------------------------------------

Comment(by Matthias):

 Replying to [comment:56 werner]:
 > Yes, time to move on :-)
 > I'm closing it as "fixed" (in 2.6.28).

 Werner, don't get me wrong, but I have always a bad feeling if a bug gets
 closed because "I believe this bug has vanished" or when a bug can not be
 reproduced any more; a bug is only really fixed when someone says, for
 example, "yes there was a small int used where it should be integer, I've
 changed and commited it"; believe me that I know about what I'm talking,
 I'm working as the tech head in a software company;

 concerning the bug itself I said, that it also occurs without 'long
 suspend time'; may be we are talking about two different bugs or usages of
 the FR; has someone with a 2.6.28 kernel tested it 7x24 without suspending
 the FR, at least?

 anyway; I will update asap to 2.6.28 (once I get an idea about an upgrade
 path in Om2008.12++) and will come back to this (or hopefully not :-))

 just my concerns, Matthias

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