I still see OOM killer invocation on 4.4.0-64.85: Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857840] java invoked oom-killer: gfp_mask=0x26000c0, order=2, oom_score_adj=0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857846] java cpuset=/ mems_allowed=0-1 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857855] CPU: 27 PID: 47820 Comm: java Tainted: G W 4.4.0-64-generic #85-Ubuntu Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857857] Hardware name: Xen HVM domU, BIOS 4.2.amazon 12/12/2016 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857860] 0000000000000286 00000000ee496386 ffff882358f13b10 ffffffff813f8083 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857867] ffff882358f13cc8 ffff883c70a8f000 ffff882358f13b80 ffffffff8120b0fe Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857871] ffffffff81cd63bf 0000000000000000 ffffffff81e677e0 0000000000000206 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857875] Call Trace: Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857885] [<ffffffff813f8083>] dump_stack+0x63/0x90 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857893] [<ffffffff8120b0fe>] dump_header+0x5a/0x1c5 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857899] [<ffffffff81192812>] oom_kill_process+0x202/0x3c0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857902] [<ffffffff81192c39>] out_of_memory+0x219/0x460 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857907] [<ffffffff81198c28>] __alloc_pages_slowpath.constprop.88+0x938/0xad0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857911] [<ffffffff81199046>] __alloc_pages_nodemask+0x286/0x2a0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857915] [<ffffffff811990fb>] alloc_kmem_pages_node+0x4b/0xc0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857921] [<ffffffff8107ea5e>] copy_process+0x1be/0x1b70 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857930] [<ffffffff811c19bd>] ? handle_mm_fault+0xcbd/0x1820 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857935] [<ffffffff81406574>] ? call_rwsem_down_read_failed+0x14/0x30 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857938] [<ffffffff810805a0>] _do_fork+0x80/0x360 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857942] [<ffffffff81080929>] SyS_clone+0x19/0x20 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857948] [<ffffffff8183c5f2>] entry_SYSCALL_64_fastpath+0x16/0x71 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857969] Mem-Info: Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857981] active_anon:32518350 inactive_anon:2099 isolated_anon:0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857981] active_file:45384948 inactive_file:45384381 isolated_file:64 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857981] unevictable:914 dirty:104 writeback:0 unstable:0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857981] slab_reclaimable:1282591 slab_unreclaimable:39566 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857981] mapped:10291496 shmem:2227 pagetables:732932 bounce:0 Feb 27 15:43:09 ip-10-0-9-47 kernel: [61385.857981] free:272957 free_pcp:1153 free_cma:0
-- 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
