#12872 HIGH -: Desktop instability in Ceibal Builds

[Zarro Boogs per Child]

#12872: Desktop instability in Ceibal Builds
-------------------------------------+-------------------------------------
            Reporter:  ebordon       |          Owner:  Quozl
                Type:  defect        |         Status:  assigned
            Priority:  high          |      Milestone:
           Component:  not assigned  |        Version:  Development build
          Resolution:                |  as of this date
          Blocked By:                |       Keywords:
Deployments affected:                |       Blocking:
            Verified:  0             |  Action Needed:  design
-------------------------------------+-------------------------------------
Changes (by Quozl):

 * status:  new => assigned
 * owner:  quozl => Quozl
 * next_action:  never set => design


Comment:

 Thanks.

 Your problem was replicated.  Using 14.1.0-10, Browse on ceibal.edu.uy
 does cause a desktop restart, but not a reboot.  ''uptime'' shows reboot
 has not happened.  ''journalctl'' shows Browse invoked oom-killer, because
 all memory had been consumed.  Kernel decided X process should be killed.
 systemd notes olpc-dm has failed, and restarts it.  See my
 [http://dev.laptop.org/~quozl/z/1YY8Xt.txt journalctl log].  Critical
 lines below:

 {{{
 Browse <4776c9f invoked oom-killer: gfp_mask=0x4d0, order=2, oom_adj=0,
 oom_score_adj=0
 [ pid ]   uid  tgid total_vm      rss cpu oom_adj oom_score_adj name
 [  792]     0   792   463461   409174   1       0             0 X
 [ 1019]  1000  1019   103948    39622   0       0             0 Browse
 <4776c9f
 Out of memory: Kill process 792 (X) score 763 or sacrifice child
 Killed process 792 (X) total-vm:1853844kB, anon-rss:1570496kB, file-
 rss:66200kB
 }}}

 So the cause is a memory leak; memory is allocated but not freed.

 Reviewing your logs.  Some of the logs showed X server failure.  For
 example, 1426520874.238467015 olpc-dm-client.error.log has "Fatal IO error
 11 (Recurso no disponible temporalmente) on X server".  But Xorg.0.log
 contained no error, which is consistent with the memory leak scenario,
 when kernel destroys X server process.

 The logs did not contain ''journalctl''.  There's an opportunity for you
 to add that to logs.

 The same does not occur on Browse on 13.2.3 (Fedora 18), so a root cause
 is likely to be in Fedora 20 or the Vivante X server which is required for
 OpenGL ES support.  It will require some time to diagnose fully.
 Meanwhile, if you can do without OpenGL ES, you might remove the packages
 and see if the problem continues.

--
Ticket URL: <http://dev.laptop.org/ticket/12872#comment:4>
One Laptop per Child <http://one.laptop.org/>
One Laptop per Child bug tracking system