** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1654971
Title:
linux 4.4.0-59.80 ADT test failure with linux 4.4.0-59.80
To
So the root issue behind this was stress-ng was calling
prctl(PR_SET_DUMPABLE) which causes the oom-adjustments to not be set.
This in turn meant that running the sockpair stressor as root let do
non-oomable processes when memory got tight and we end up in locked in
kernel space looking for free pa
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654971
Title:
linux 4.4.0-59.80 ADT test failure with linux 4.4.0-59.80
To manag
OK, there's one more bug that's causing ADT to hang, I've now managed to
reproduce another hang, it seems specific to running the sockpair
stress-ng stressor with a large number of CPUs and > 2GB of memory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
the following stable commit fixes this hang:
http://git.kernel.org/cgit/linux/kernel/git/stable/stable-
queue.git/diff/releases/4.4.41/ftrace-x86_32-set-ftrace_stub-to-weak-to-
prevent-gcc-from-using-short-jumps-to-
it.patch?id=4a1e0d3c5df26e1689c6147c078af10a367969d9
since these will be landing
This one failed with a hang in the kernel regression test suite in
whatever is after the sockfd test:
01:55:06 DEBUG| [stdout] sock PASSED
01:55:16 DEBUG| [stdout] sockfd PASSED
[hang]
Looking back at previous runs we also see it drop "Killed" in the same
place:
06:30:16 DEBUG| [stdout]
