#10075 NORM Not Tri: long uptime with constant wakeups fills /var/log and crashes machine

[Zarro Boogs per Child]

#10075: long uptime with constant wakeups fills /var/log and crashes machine
--------------------------------+-------------------------------------------
           Reporter:  rsmith    |       Owner:  cjb          
               Type:  defect    |      Status:  new          
           Priority:  normal    |   Milestone:  Not Triaged  
          Component:  distro    |     Version:  not specified
         Resolution:            |    Keywords:               
        Next_action:  diagnose  |    Verified:  0            
Deployment_affected:            |   Blockedby:               
           Blocking:            |  
--------------------------------+-------------------------------------------
Changes (by pgf):

  * next_action:  never set => diagnose


Comment:

 just to be clear -- the log was full of the unavoidable kernel messages,
 happening for every suspend and resume, correct?  it wasn't your logging
 script?  (powerd may do some minimal logging at s/r time, but i it should
 be only one line or two.)

 one s/r cycle per minute for 48 hours is about 3000 cycles.  18M of logs
 means over 6Mb per s/r cycle.  does this seem right?  i don't have a log
 handy to do an actual count on.

 btw, even if logrotate configuration is tuned correctly for our reduced
 /var/log space (doubtful), i think it only runs once a day by default.
 even if your test was somewhat artificial, it seems like actual usage
 could give the same result after, say, a week or two of uptime.  i think
 the logging config should be examined.

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