#7985 HIGH 8.2.0 (: Starting Chat crashes laptop

[Zarro Boogs per Child]

#7985: Starting Chat crashes laptop
-----------------------------+----------------------------------------------
   Reporter:  joe            |       Owner:  cjb                 
       Type:  defect         |      Status:  new                 
   Priority:  high           |   Milestone:  8.2.0 (was Update.2)
  Component:  chat-activity  |     Version:  not specified       
 Resolution:                 |    Keywords:  blocks?:8.2.0       
Next_action:  reproduce      |    Verified:  0                   
  Blockedby:                 |    Blocking:                      
-----------------------------+----------------------------------------------

Comment(by dilinger):

 Looking at dmesg.out, it's pretty clear that this is an OOM (potentially
 triggered by libertas failures?)

 {{{
 [52721.719978] NETDEV WATCHDOG: eth0: transmit timed out
 [52721.720011] libertas: tx watch dog timeout
 }}}

 {{{
 [63868.750174] NETDEV WATCHDOG: eth0: transmit timed out
 [63868.750207] libertas: tx watch dog timeout
 [63873.598599] libertas: Command 1f timed out
 [63873.605388] libertas: requeueing command 1f due to timeout (#1)
 [63873.607514] libertas: Received result 0 to command 1f after 1 retries
 }}}

 {{{
 [85840.663155] hald invoked oom-killer: gfp_mask=0x1201d2, order=0,
 oomkilladj=0
 [85840.663223] Pid: 946, comm: hald Not tainted
 2.6.25-20080813.4.olpc.cc866cfe0c31220 #1
 }}}

 In the messages file, you'll see lots of errors from NetworkManager.  So,
 taking a wild guess, I'd suspect either:
 a) Chat is unable to access the network, and procceeds to spin/allocate
 lots of memory until the OOM killer kills it, or
 b) libertas errors are causing NM to get confused, at which point NM is
 spinning/allocating lots of memory until the OOM killer kills it (or it
 crashes).

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