← Back to team overview

kernel-packages team mailing list archive

[Bug 1389304] Re: OOM killer triggered during encrypted home dir vivid desktop installations

 

I am trying to find the information, a manual installation with 512 MB
did not cause this issue. So certainly utah appears to be adding to the
issue. openssh-server python-yaml bzr git gdebi-core are the additional
packages being installed during the installation.

Also, tried with 470 MB of memory to see if the following line has any relevance but it dint.
 kernel: [    0.000000] Memory: 477892K/523888K available (7731K kernel code, 1200K rwdata, 3608K rodata, 1360K init, 1308K bss, 45996K reserved)

Will make detailed investigation.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1389304

Title:
  OOM killer triggered during encrypted home dir vivid desktop
  installations

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The following trace appears during a vivid desktop installation with
  encrypted home dir setup.

  2014-11-04T13:08:50.904446+00:00 utah-29294-vivid-amd64 kernel: [  245.136823] gtk-update-icon cpuset=session-c1.scope mems_allowed=0
  2014-11-04T13:08:50.904451+00:00 utah-29294-vivid-amd64 kernel: [  245.136831] CPU: 0 PID: 9528 Comm: gtk-update-icon Not tainted 3.16.0-24-generic #32-Ubuntu
  2014-11-04T13:08:50.904453+00:00 utah-29294-vivid-amd64 kernel: [  245.136832] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
  2014-11-04T13:08:50.904454+00:00 utah-29294-vivid-amd64 kernel: [  245.136835]  0000000000000000 ffff8800089bb908 ffffffff8177fcbc ffff880019f265e0
  2014-11-04T13:08:50.904455+00:00 utah-29294-vivid-amd64 kernel: [  245.136837]  ffff8800089bb970 ffffffff8177c3e8 0000000000000003 0000000000000000
  2014-11-04T13:08:50.904456+00:00 utah-29294-vivid-amd64 kernel: [  245.136839]  ffff88001fffae28 ffff8800089bb940 0000000000000206 ffffffff81c670c0
  2014-11-04T13:08:50.904457+00:00 utah-29294-vivid-amd64 kernel: [  245.136843] Call Trace:
  2014-11-04T13:08:50.904458+00:00 utah-29294-vivid-amd64 kernel: [  245.136859]  [<ffffffff8177fcbc>] dump_stack+0x45/0x56
  2014-11-04T13:08:50.904459+00:00 utah-29294-vivid-amd64 kernel: [  245.136862]  [<ffffffff8177c3e8>] dump_header+0x9e/0x205
  2014-11-04T13:08:50.904461+00:00 utah-29294-vivid-amd64 kernel: [  245.136870]  [<ffffffff8116cea5>] oom_kill_process+0x205/0x360
  2014-11-04T13:08:50.904462+00:00 utah-29294-vivid-amd64 kernel: [  245.136872]  [<ffffffff8116d68d>] out_of_memory+0x4cd/0x510
  2014-11-04T13:08:50.904463+00:00 utah-29294-vivid-amd64 kernel: [  245.136879]  [<ffffffff8117454e>] __alloc_pages_nodemask+0xb6e/0xbb0
  2014-11-04T13:08:50.904463+00:00 utah-29294-vivid-amd64 kernel: [  245.136885]  [<ffffffff811b6a41>] alloc_pages_current+0xb1/0x160
  2014-11-04T13:08:50.904464+00:00 utah-29294-vivid-amd64 kernel: [  245.136888]  [<ffffffff81169497>] __page_cache_alloc+0xa7/0xc0
  2014-11-04T13:08:50.904465+00:00 utah-29294-vivid-amd64 kernel: [  245.136890]  [<ffffffff8116bb67>] filemap_fault+0x1b7/0x410
  2014-11-04T13:08:50.904466+00:00 utah-29294-vivid-amd64 kernel: [  245.136896]  [<ffffffff81194c6d>] __do_fault+0x3d/0xc0
  2014-11-04T13:08:50.904468+00:00 utah-29294-vivid-amd64 kernel: [  245.136899]  [<ffffffff81197210>] do_read_fault.isra.57+0x50/0x300
  2014-11-04T13:08:50.904469+00:00 utah-29294-vivid-amd64 kernel: [  245.136902]  [<ffffffff81199286>] handle_mm_fault+0x896/0xf90
  2014-11-04T13:08:50.904470+00:00 utah-29294-vivid-amd64 kernel: [  245.136910]  [<ffffffff8105ce42>] __do_page_fault+0x1c2/0x580
  2014-11-04T13:08:50.904471+00:00 utah-29294-vivid-amd64 kernel: [  245.136919]  [<ffffffff810a9de8>] ? __enqueue_entity+0x78/0x80
  2014-11-04T13:08:50.904472+00:00 utah-29294-vivid-amd64 kernel: [  245.136922]  [<ffffffff810abb55>] ? set_next_entity+0x95/0xb0
  2014-11-04T13:08:50.904472+00:00 utah-29294-vivid-amd64 kernel: [  245.136940]  [<ffffffff810116a6>] ? __switch_to+0x1d6/0x5e0
  2014-11-04T13:08:50.904474+00:00 utah-29294-vivid-amd64 kernel: [  245.136943]  [<ffffffff8105d2b1>] trace_do_page_fault+0x41/0x100
  2014-11-04T13:08:50.904475+00:00 utah-29294-vivid-amd64 kernel: [  245.136950]  [<ffffffff81055659>] do_async_page_fault+0x29/0xe0
  2014-11-04T13:08:50.904476+00:00 utah-29294-vivid-amd64 kernel: [  245.136957]  [<ffffffff81789db8>] async_page_fault+0x28/0x30

  Steps to reproduce:
  1. Install utah:
            sudo apt-add-repository -y ppa:utah/stable
            sudo apt-get update
            sudo apt-get install utah

  2.  Make the iso readable by the user utah

  3.  Run 
     "sudo -u utah -i run_utah_tests.py -i /path/to/the/vivid-desktop-amd64.iso -p lp:ubuntu-test-cases/desktop/preseeds/encrypted_home.cfg lp:ubuntu-test-cases/desktop/runlists/encrypted_home.run -f /var/log/installer -x /etc/utah/bridged-network-vm.xml"

  Now the trace above could be seen. 
  The installation log containing the kernel log is attached.

  Note: This is reproducible with vm's provisioned with 512 MB memory,
  which is the default value in /etc/utah/bridged-network-vm.xml in the
  host machine. With 1G RAM this kernel trace is not reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389304/+subscriptions


References