** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack str
** Tags added: cscc
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack stressors on all
arches.
Status in Stress-ng:
** Changed in: stress-ng
Status: New => Invalid
** Changed in: stress-ng
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/17
These stressors are expected to trigger the OOM killer. The oom
adjustment for the stressor child processes is always adjusted to make
them the first processes to be OOM'd. However, the kernel make's it
choice on what gets OOM'd depending on many factors, so the stressors
may end up triggering ot
Is this still an open bug or can it be closed now?
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack stressors on all
a
** Tags removed: kernel-da-key
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack stressors on all
arches.
Status in St
** Tags added: hwcert-server
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack stressors on all
arches.
Status in Stre
I'm not able to recreate this on a smaller generic amd64 machine:
ubuntu@xwing:~$ free
totalusedfree shared buff/cache available
Mem:3930172 133912 33192006124 477060 3500044
Swap: 100040060 0 100040060
ubuntu
I'm still able to trigger problems with the "stack" stressor on the Xeon
Phi...
ubuntu@lalande:~$ sudo ./memory_stress_ng
Total memory is 63 GiB
Constant run time is 300 seconds per stressor
Variable run time is 930 seconds per stressor
Estimated total run time is 20 minutes
Running stress-ng st
Because of the above, I've re-opened the kernel tasks :(
--
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/1729878
Title:
stress-ng triggering oomkiller running brk and stack stressors on a
Given that, I'm marking the kernel tasks as invalid as this appears to
be stress-ng being over aggressive.
MAAS deployments (and I presume server installs in general) only provide
about 4 - 8GB swap max in a swap file created in the root filesystem (no
swap partition anymore).
It is not reasonabl
Also retried on amd64 and the effect was the same:
ubuntu@xwing:~$ free -lm
totalusedfree shared buff/cache available
Mem: 3838 1203601 0 1153510
Low: 3838 2363601
High:
So I did this on 4.4 on ppc64le with 32GB RAM and 96GB Swap:
ubuntu@entei:~$ free -lm
totalusedfree shared buff/cache available
Mem: 32565 656 30603 21304 30503
Low: 325651961 30603
High:
Ok, I've narrowed it down to the brk and stack stressors in stress-ng.
I've recreated this on amd64, ppc64el and s390x across 4.4, 4.10 and
4.13 kernels.
Stress-NG reports the tests as successful so I guess now the only thing
remaining is to confirm that hitting OOM killer is expected behaviour
wh
** Summary changed:
- stress-ng triggering call-traces on s390x z/VM instances
+ stress-ng triggering oomkiller running brk and stack stressors on all arches.
** Also affects: stress-ng
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
15 matches
Mail list logo