Bug is prevalent on 4.8 kernels too.

---
[251529.693133] CPU: 3 PID: 1547 Comm: icinga2 Not tainted 4.8.0-34-generic 
#36~16.04.1-Ubuntu
[251529.693134] Hardware name: MSI MS-7823/B85M-G43 (MS-7823), BIOS V3.14B3 
06/23/2014
[251529.693135]  0000000000000286 00000000e9fa7ede ffff95c3f774bb38 
ffffffffab62d7b3
[251529.693137]  ffff95c3f774bcc8 ffff95c3f23bd700 ffff95c3f774bba0 
ffffffffab42e9bb
[251529.693138]  ffff95c3f774bb40 0000000000000000 0000000000000000 
0000000000000000
[251529.693140] Call Trace:
[251529.693145]  [<ffffffffab62d7b3>] dump_stack+0x63/0x90
[251529.693148]  [<ffffffffab42e9bb>] dump_header+0x5c/0x1dc
[251529.693151]  [<ffffffffab3a5836>] oom_kill_process+0x226/0x3f0
[251529.693153]  [<ffffffffab3a5daa>] out_of_memory+0x35a/0x3f0
[251529.693155]  [<ffffffffab3ab06b>] __alloc_pages_slowpath+0x9fb/0xa20
[251529.693157]  [<ffffffffab3ab34a>] __alloc_pages_nodemask+0x2ba/0x300
[251529.693160]  [<ffffffffab280726>] copy_process.part.30+0x146/0x1b50
[251529.693162]  [<ffffffffab95c66d>] ? sock_recvmsg+0x3d/0x50
[251529.693163]  [<ffffffffab95c8aa>] ? SYSC_recvfrom+0xda/0x150
[251529.693164]  [<ffffffffab282327>] _do_fork+0xe7/0x3f0
[251529.693166]  [<ffffffffab95e171>] ? __sys_recvmsg+0x51/0x90
[251529.693168]  [<ffffffffab2826d9>] SyS_clone+0x19/0x20
[251529.693170]  [<ffffffffab203bae>] do_syscall_64+0x5e/0xc0
[251529.693174]  [<ffffffffaba96625>] entry_SYSCALL64_slow_path+0x25/0x25
[251529.693174] Mem-Info:
[251529.693177] active_anon:339565 inactive_anon:133615 isolated_anon:0
                 active_file:3938458 inactive_file:328087 isolated_file:0
                 unevictable:8 dirty:200 writeback:37 unstable:0
                 slab_reclaimable:3365424 slab_unreclaimable:16102
                 mapped:9114 shmem:1459 pagetables:2462 bounce:0
                 free:49449 free_pcp:32 free_cma:0
---

Had 5 servers knocked out over the weekend.

-- 
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/1655842

Title:
  "Out of memory" errors after upgrade to 4.4.0-59

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  I recently replaced some Xenial servers, and started experiencing "Out
  of memory" problems with the default kernel.

  We bake Amazon AMIs based on an official Ubuntu-provided image (ami-
  e6b58e85, in ap-southeast-2, from https://cloud-
  images.ubuntu.com/locator/ec2/).  Previous versions of our AMI
  included "4.4.0-57-generic", but the latest version picked up
  "4.4.0-59-generic" as part of a "dist-upgrade".

  Instances booted using the new AMI have been using more memory, and
  experiencing OOM issues - sometimes during boot, and sometimes a while
  afterwards.  An example from the system log is:

  [  130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' 
at Wed, 11 Jan 2017 22:07:53 +0000. Up 29.28 seconds.
  [  130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 
2017 22:09:35 +0000. Datasource DataSourceEc2.  Up 130.09 seconds
  [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice 
child
  [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, 
anon-rss:51184kB, file-rss:2164kB
  [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or 
sacrifice child
  [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, 
anon-rss:6676kB, file-rss:0kB
  [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or 
sacrifice child
  [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, 
anon-rss:23956kB, file-rss:1356kB

  I have a hunch that this may be related to the fix for
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400,
  introduced in linux (4.4.0-58.79).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---- 1 root audio 116,  1 Jan 12 06:29 seq
   crw-rw---- 1 root audio 116, 33 Jan 12 06:29 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 12 06:38:45 2017
  Ec2AMI: ami-0f93966c
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-southeast-2a
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-59-generic N/A
   linux-backports-modules-4.4.0-59-generic  N/A
   linux-firmware                            1.157.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2016
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to