Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. Re: Openmoko Bug #1597: after a long suspend time,        kernel
      thread events/0 sits eating 30% cpu (Openmoko Public Trac)
   2. Re: Openmoko Bug #1597: after a long suspend time,        kernel
      thread events/0 sits eating 30% cpu (Openmoko Public Trac)
   3. Re: Openmoko Bug #1597: after a long suspend time,        kernel
      thread events/0 sits eating 30% cpu (Openmoko Public Trac)
--- Begin Message ---
#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            |       Keywords:            
 Haspatch:  0                |      Blockedby:            
Estimated:                   |    Patchreview:            
 Blocking:                   |   Reproducible:            
-----------------------------+----------------------------------------------

Comment(by Matthias):

 I did a lot of tests with monitor-scripts to catch the situation and can
 confirm:

 - the runaway (consuming CPU) of events/0 occurs also without using
 suspend;
 - it occurs without using GPRS, GPS and Wifi, just acting the FR as a GSM
 phone
 - it occurs exactly after 18h+16...17min uptime (which is in seconds a bit
 more
   than the unsigned short value of 65536)

 Matthias ([email protected])

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

--- End Message ---
--- Begin Message ---
#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            |       Keywords:            
 Haspatch:  0                |      Blockedby:            
Estimated:                   |    Patchreview:            
 Blocking:                   |   Reproducible:            
-----------------------------+----------------------------------------------

Comment(by Matthias):

 Replying to [comment:53 Matthias]:
 > I did a lot of tests with monitor-scripts to catch the situation and can
 confirm:
 >
 > - the runaway (consuming CPU) of events/0 occurs also without using
 suspend;
 > - it occurs without using GPRS, GPS and Wifi, just acting the FR as a
 GSM phone
 > - it occurs exactly after 18h+16...17min uptime (which is in seconds a
 bit more
 >   than the unsigned short value of 65536)
 >
 > Matthias ([email protected])

 sorry, forgot to say this is with Om2008.9

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

--- End Message ---
--- Begin Message ---
#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            |       Keywords:            
 Haspatch:  0                |      Blockedby:            
Estimated:                   |    Patchreview:            
 Blocking:                   |   Reproducible:            
-----------------------------+----------------------------------------------

Comment(by andy):

 As it says above the issue can't be reproduced (allegedly) on 2.6.28
 kernels, we won't be backporting the change that we think solved it to
 2.6.24.

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

--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to