You can potentially use numactl to launch the process and set a policy
of interleaving allocations between NUMA nodes to avoid these 1 sided
allocations. Tends to happen with servers that make big allocations
from a single thread during startup, as commonly seen on mysqld servers
and the innodb_bu
In our production environment of ~1800 nodes we've seen oom-kill events
that looked similar to this bug's pattern - oom-kills killing large
server processes while resident memory was far lower than available
physical memory.
We were affected by the original bug and saw that issue readily
addresse
** Description changed:
- I recently replaced some Xenial servers, and started experiencing "Out
- of memory" problems with the default kernel.
+ After a fix for LP#1647400, a bug that caused freezes under some
+ workloads, some users noticed regular OOMs. Those regular OOMs were
+ reported under
Side Question... Is there something I can specifically look for on a
Ubuntu install that would indicate if that kernel has the fix or not. I
assume the "Fix or Not" indicates are manually triggered and the fix
could be out for AWS but not indicated.
--
You received this bug notification because y
We believe that we are experiencing this issue on kernel 4.4.0-1030-aws
as well. We recently move from 14 LTS to 16LTS and are now experience
oom kills.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
Not sure if it's the same issue, but we had an unexpected OOM with
Ubuntu 16.04.3 LTS, 4.4.0-91.
Oct 31 23:52:25 db3 kernel: [6569272.882023] psql invoked oom-killer:
gfp_mask=0x26000c0, order=2, oom_score_adj=0
...
Oct 31 23:52:25 db3 kernel: [6569272.882154] Mem-Info:
Oct 31 23:52:25 db3 kerne
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Ti
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
** Changed in: linux-raspi2 (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: linux-raspi2 (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Attached kern.log
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4944721/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165
We have found this issue on 4.4.0-92 too.
But only when the systems were put under stress.
Reverting back to 4.4.0-57 resolved it.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4944720/+files/dmesg.txt
--
You received this bug notif
With the sysctl settings provided by Pete (vm.min_free_kbytes = 100
and vm.zone_reclaim_mode = 1), we've been running the linux-aws
4.4.0-1028.37 kernel successfully without an OOM killer invocation for
about four days now. Previously we would have seen three or more
occurrences of this per day
Attaching dmesg output
** Attachment added: "dmesg-kernel4.4.0-89.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4934014/+files/dmesg-kernel4.4.0-89.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
We have another case of OOM at one of the host that we upgraded kernel
to 4.4.0-89 a week ago.
kern.log attached.
** Attachment added: "Kern log attached."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4934013/+files/kern-log-kernel4.4.0-89.txt
--
You received th
> kthreadd invoked oom-killer: gfp_mask=0x26000c0, order=2,
oom_score_adj=0
Yea - that 2nd order allocation failure is the exact same issue I was
able to see (same GFP mask also)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Apologies - the file was inadvertently split by logrotate. I have
concatenated the entire contents of kern.log and kern.log.1 into the
attached file; these are the only kern.log files in /var/log on the
system.
I do have to redact the hostname in question, but it is a simple
substitution of 'local
I have seemingly solved this issue with linux-aws version 4.4.0-1016-aws
at the very least. The specific issue I was seeing was 2nd order
allocations failing when OOMKiller triggered. At the time I was
thinking the issue was due to XFS and memory fragmentation with lots and
lots of memory mapped
Please, do not cut the logs. Without the "invoked oom-killer" line, for
example, it's hard to see the gfp flags and allocation order that
failed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
We are also experiencing this issue running linux-aws 4.4.0-1028.37,
which tracks Ubuntu kernel 4.4.0-89.112. Our use case is very similar to
comment #86
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/comments/86).
In our case ElasticSearch 2.4.5 is running under Java 1.8.0_131 with
Hi
I am experiencing at one of our compute node hypervisor. kernel version
we are using is 4.4.0-83, but seems to be having the issue reported in
this report.
[Mon Aug 7 00:19:42 2017] nova-compute invoked oom-killer: gfp_mask=0x2c200ca,
order=0, oom_score_adj=0
[Mon Aug 7 00:19:42 2017] nova
Mine's also still stable (no OOMs), after running the patched kernel for
9 days, on a Raspberry pi 2 Model B v1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors
4.4.0-1062-raspi2 is looking good - I've had it running for a week
without oom-killer being invoked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade
Update: No sign of Out-of-memory errors or kills, after 3 days of
testing the 4.4.0-1062-raspi2 kernel. I'll report back again next week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
Sure.
I undid the workaround, installed and booted the kernel and will test it for a
few days. I'll keep you posted on results.
Thanks Paolo!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
T
Chris, can you test if this kernel solves your problem?
http://people.canonical.com/~ppisati/lp1655842/linux-
image-4.4.0-1062-raspi2_4.4.0-1062.70~lp1655842_armhf.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Paolo Pisati (p-pisati)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0
The bug is still confirmed and not fixed for linux-raspi2 (Ubuntu), 5
months after getting fixed for the main Ubuntu.
Shouldn't this have some priority? Even apt upgrade breaks if I don't
use the clear cache workaround. I can live with it (cron job to clear
cache) but this is not great for LTS.
C
@nicholas-hatch - what file system are your disks formatted as? I was
able to stop the OOM's on my ES hosts by moving from XFS to EXT4. My
belief is that there was a memory fragmentation issue with ES and many
small files on XFS formatted volumes.
--
You received this bug notification because y
We're still having issues with higher-order allocations failing and
triggering an OOM kill for unexplainable reasons. (on 4.4.0-78-generic).
I've attached the relevant OOM killer logs. It may be relevant to note
that the server these logs are from is an Elasticsearch instance with a
large (~32GB)
Also observed with 4.4.0-1054-raspi2. I'm now back on 4.4.0-1038-raspi2.
I think that one was ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Confirmed
** Changed in: linux-raspi2 (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
I'm seeing oom-killer being invoked despite having 2GB free swap when
using the kernel from linux-image-4.4.0-1055-raspi2 version
4.4.0-1055.62.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
T
linux-raspi2 version 4.4.0.1055.56 that is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notifications about this bug go t
This is still an issue in the current linux-raspi2 version. Where those
changes ported to that kernel?
** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'd like to emphasise that the OOM problem only happens with KDE. I have
several DE installed including Unity, GNOME3, Cinnamon. But none of them
caused a OOM, at least I never noticed. But in KDE, most of the time
when chrome is opened, it triggers OOM. dmesg tells that, sometimes
kwin_x11 invoked
I also haven't personally encountered any further OOM issues on my home
desktop (used daily) with 4.4.0.63.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after
Yes, 4.4.0.63 solved our OOM issues (and we had plenty after 4.4.0.59).
Ours were all headless server (bare metal and VMs) related though - no
desktop usage.
But I never experienced this issue with my home laptop either, but that
had lots of RAM and was only lightly used during that period - not
r
Anybody having successfully tested 4.4.0.63 for OOM-kill issue...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notificatio
I have 4.4.0-59 till 4.4.0-71 and 4.8.0-41 till 4.8.0-46 installed on my
system and all are affected by this bug. Firefox, Chrome and Netbeans
regularly get killed without a warning and for no reason (since I have
something like 10GB+ RAM and all 16GB Swap free at the time the process
gets killed).
I was using 4.4.0-21 as reported by `uname -r` which is default in
Kubuntu 16.04. The same bug appears on mainline kernel 4.10 too!
Now, I'm in confusion. Which kernel should I upgrade to? Also I
experience this only in KDE session with yandex or chrome browser opened
--
You received this bug no
This is plaguing Horizon project Pi2 and Pi3 devices running Xenial
16.04.2 w/ kernel 4.4.0-1050-raspi2. From a pi2:
root@horizon-a17d2187:~# uname -a
Linux horizon-a17d2187 4.4.0-1050-raspi2 #57-Ubuntu SMP Wed Mar 22
12:52:22 UTC 2017 armv7l armv7l armv7l GNU/Linux
root@horizon-0
I am seeing this issue as well, on Arch kernel v 4.10.4-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notifications about
We have been seeing this issue recently as well. We are running
4.4.0-66-generic #87-Ubuntu - I can attempt to downgrade to 4.4.0-57 but
its a large cluster with a lot of data so it may take some time.
Attached a kern.log from this most recent oom.
** Attachment added: "kern.log"
https://bugs
Hi Cascardo,
there is no related dmesg output after the incident (just some lines
from apt-daily.timer).
I filed a bug for the possible swap corruption issue here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1669707
Thanks so far.
Julian
--
You received this bug notification because
Julian, your logs indicate some possible swap corruption, would you mind
opening a new bug and sending it using apport-bug?
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Ti
Hi, Julian.
Do you have the output of dmesg after the incident before a reboot?
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0
Attached kern.log. Let me know in case you need more logs.
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+attachment/4829766/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Hi, Anton and Julian.
Can you attach complete logs for investigation?
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-5
Same here on Linux 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux.
Out of memory: Kill process 11067 (java) score 28 or sacrifice child
Killed process 11067 (java) total-vm:3569724kB, anon-rss:211720kB,
file-rss:20208kB
systemd-journald[247]: /dev/kmsg
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: [613
I can confirm 4.4.0-64.85 fixes our OOM issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notifications about this bug
Could somebody please confirm that the issue has been fixed with the
kernel 4.4.0-64.85? We had massive problems with OOM killed qemu
instances on our virtualization hosts and would not like to have this
introduced again.
--
You received this bug notification because you are a member of Ubuntu
Bu
I'm pretty sure this bug was introduced in 4.4.0-58, even though I
reported it against 4.4.0-59. Still, +1 for a raising a separate bug
against 4.8.
Thanks to Cascardo for fixing this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
The OOM fixes were introduced in 4.4.0-58 according to the changelog,
but sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To mana
Hi, Mr. Iain Buclaw.
Memory usage reports could be related to something else. This bug was
introduced at 4.4.0-59, you mention 4.4.0-58. We could certainly
investigate the issue you see, just not on this bug. Much more data is
necessary, but, please, don't attach new data to this bug. Your report
This is the reported /proc/meminfo Buffers usage for 4 different kernel
versions. We got the same OOM call traces on both 4.4.0-58 and
4.8.0-34, I highly doubt that to be a coincidence.
** Attachment added: "meminfo-buffers.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+at
This bug is not about memory use. It's about the Linux kernel triggering
the OOM killer when higher-order (order 2) allocations are requested and
progress cannot be made. This affected Linux 4.7 on mainline and was
fixed on Linux 4.7 stable and Linux 4.8. When some fixes were backported
to 4.4.0-59
Yes they are, I'm seeing the same exorbitant memory usage that we had on
4.4.0-58 as am currently getting on 4.8.0-36.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" er
4.8 kernels are not affected by this bug. If you have OOMs on 4.8
kernels, please file a new bug with all the revelant details and logs.
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
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] 0286 e9fa7ede 95c3f774bb38
This bug was fixed in the package linux - 4.4.0-63.84
---
linux (4.4.0-63.84) xenial; urgency=low
[ Thadeu Lima de Souza Cascardo ]
* Release Tracking Bug
- LP: #1660704
* Backport Dirty COW patch to prevent wineserver freeze (LP: #1658270)
- SAUCE: mm: Respect FOLL_FO
** Description changed:
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/e
I was curious if I could answer Sridhar's question as I had the same
question.
The introduction of the problem appears to be in Ubuntu's packaging of
select upstream commits from 4.7 to address bug #1647400.
>From the comments in that case, it appears
6b4e3181d7bd5ca5ab6f45929e4a5ffa7ab4ab7f shou
Did anybody also notice any pattern in "invoked oom-killer". I see a
pattern like daily almost same time cron or scripts invoking oom-
killer...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
T
Thanks to those who reported/fixed this bug.
Out of curiosity, was this a bug in the 4.4.0-59 kernel itself or in
Ubuntu's packaging of the kernel, i.e. were other (non-Ubuntu) Linux
users impacted ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
To throw some more light into the matter. Two machines were upgraded to
4.4.0-59 on 16th Jan, same load, but only one out of them is reporting
oom-kill. Anybody experiencing same scenario...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Like Luk (#29), I upgraded to 4.8.0-34, but the problem disappeared for
me. I ran system for two days without any OOM-kills. Before that, simply
copying a big file (9Gb+) fired the system. My system has 16Gb RAM and
runs 16.04.1.
--
You received this bug notification because you are a member of U
you should re-release 4.4.0-62 as linux-image-chaosmonkey-virtual
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notificatio
Tested Ubuntu 4.4.0-63.84-generic 4.4.44 on a desktop system with a
workload which previously led to Chrome processes being OOM-killed.
Situation with 4.4.0-62-generic: between 8 and 54 processes OOM-killed per
24-hour period
Situation with 4.4.0-63-generic: no OOM-kills during 46 hours of testin
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To
-63 works for me as well, thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notifications about this bug go to:
http
I've been using -63 for a while now (even before it was in proposed, via
an sbuild setup) on a machine that had OOM problems with -59, and I
haven't noticed any issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
-
Sender: Nate Eldredge <1655...@bugs.launchpad.net>
Time: Fri 2/10 19:21
To: wurlyfan
Subject: Re: [Bug 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
>On Fri, 10 Feb 2017, Travisgevans wrote:
>
>> However, it might help if anyone has an idea how t
I see this bug on Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-1042-raspi2
armv7l) as described here: https://superuser.com/questions/1176773
/ubuntu-on-rpi-starts-killing-processes-when-ram-is-filled-up-by-cache
The workaround by Krzysztof Dryja (cih997) works for me as well but is
very ugly and temporary
On Fri, 10 Feb 2017, Travisgevans wrote:
> However, it might help if anyone has an idea how the OOM kill bug might
> be reliably reproduced. “5 working days” isn't very long to reliably be
> sure the problem is solved otherwise; it took more than half that time
> upon upgrading to -59 for me to hi
Don't forget that the earlier kernels are affected by Bug #1647400,
which does something even worse (hang the system). I've verified that it
affected my particular system before 4.4.0-59, and it may explain a
couple of lockups I had previously experienced during normal operation
when using previous
To be fair, there have been multiple USN-reported kernel security
patches fixed in post-57 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade
@nick-maynard: Why is such a bug unforgivable? You can just boot a
previous kernel instead. If you're concerned about availability then
don't reboot in the first place unless there's an important security
patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Cascardo: Just to be clear, are you looking for verification from anyone
in the world, or from specific kernel testers?
(I'd like to help, but I'm only able to reproduce the issue in
production, and the process of debugging this issue when we ran into it
was already more restarts than is good for
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
kulwinder singh: Either one, but nothing in between.
-57 will reintroduce a few (unrelated) security bugs as well as the bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400 whose fix
caused this one, but is easier to enable and has been tested for longer.
-63 should fix this bug, the
Who is the saver 4.4.0-57-generic or 4.4.0-63-generic now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notifications abou
Testing...
Enabled proposed (https://wiki.ubuntu.com/Testing/EnableProposed).
Installed kernel packages:
# apt-get install -s -t xenial-proposed 'linux-headers-4.4.0.63$'
'linux-headers-4.4.0.63-generic$' 'linux-image-4.4.0.63-generic$'
'linux-image-extra-4.4.0.63-generic$'
Rebooted.
# cat /pr
The fix is now available for testing in kernel version 4.4.0-63.84, if
you enable proposed[1]
$ apt-cache policy linux-image-4.4.0-63-generic
linux-image-4.4.0-63-generic:
Installed: (none)
==> Candidate: 4.4.0-63.84
Version table:
4.4.0-63.84 500
500 http://archive.ubuntu.com/u
If this kernel is not going to hit -updates shortly (i.e. days), can
something be done to pull or downgrade the broken kernel? At least
revert linux-image-generic to depend back on linux-
image-4.4.0-57-generic which doesn't have the issues and will stop more
people from upgrading to a broken kerne
LTS Ubuntu with -updates shouldn't have this sort of issue - this is,
frankly, unforgivable.
We need a new kernel urgently in -updates, and I'd expect serious
discussions within the kernel team to understand what has caused this
issue and avoid it reoccurring.
--
You received this bug notificati
Just by the way - 4.4.0-62-generic has the exact same problem. Even when
uninstalling 4.4.0-59-generic, my system at some point auto-updated to
4.4.0-62-generic . Only 4.4.0-57-generic is safe for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Hi, Luk.
linux-image-4.8.0-34-generic should not be affected by this. If you see
unexpected OOM problems, please open a new bug report and attach the
kernel logs, please.
Thanks.
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
This bug also appears to affect linux-image-4.8.0-34-generic in 16.04.1
Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To mana
When this new kernel will be released? This bug is killing our MySQL
Servers. Booting old kernels is only a bad workaround. I think a lot of
people with busy servers will have a problem.
This is 2.nd time we were hit by a big bug within short time. In oct 2016 our
nameservers got problems because
I've been struggling with this bug for nearly a week and only now found
this issue. Thanks for fixing it!
For the sake of others finding it, here's the stack trace part of the
oom-killer log, which contains some terms I searched for a while ago
that aren't mentioned here yet.
docker invoked oom-
As a note: I believe this also affects the armhf kernel
4.4.0-1040-raspi2 for the Raspberry Pi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4
@nate Thank you! You just saved me a lot of hassle as I was about to
unpin the 4.4.0-57 kernel and update a bunch of machines on the
assumption the fix was in that version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This is fixed in 4.4.0-63.84, which will be available in proposed soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0-59
To manage notif
I could not reboot my machine and the ugly workaround for this issue was
to login as root and clear system caches:
echo 3 > /proc/sys/vm/drop_caches
This made my machine stable again, at least for the time I needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just as a note for newcomers reading this, I can confirm the bug is NOT
fixed in the officially released 4.4.0-62.83.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" err
This is a severe bug. It should be treated a high-priority bugfix that
cannot wait 3 weeks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655842
Title:
"Out of memory" errors after upgrade to 4.4.0
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
@Gaudenz Steinlin (gaudenz-debian),
It will takes 3 weeks to land in -updates pocket, but you can expect to
have a call for testing a proposed package by EOW.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
@slashd It sounds really strange to me that I should wait til 20-Feb for
a fix for this bug while this is clearly a regression introduced with
the latest kernel upgrade. Is there no way to speed things up to fix
this regression.
Currently we had to downgrade all our xenial systems to linux-
image-
1 - 100 of 119 matches
Mail list logo
