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 other hoggy processes to be OOM'd as well.
This is not a bug, it is expected behaviour. See the stress-ng manual,
it clearly states when a stressors can trigger the OOM killer and how
each stress-ng stressor copes with this, for example:
--brk N
start N workers that grow the data segment by one page at a time
using
multiple brk(2) calls. Each successfully allocated new page is
touched
to ensure it is resident in memory. If an out of memory
condition
occurs then the test will reset the data segment to the point
before
it started and repeat the data segment resizing over again.
The
process adjusts the out of memory setting so that it may be
killed by
the out of memory (OOM) killer before other processes. If
it is
killed by the OOM killer then it will be automatically re-started
by a
monitoring parent process.
I shall close this as it is not a bug. Stress-ng is expected to stress a
kernel to trigger OOMs.
--
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:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Artful:
Won't Fix
Bug description:
During regression testing on a z/VM instance, I noticed call traces
being dumped to dmesg that seem to be related to stress-ng.
The stress-ng invocation we're using is:
stress-ng --aggressive --verify --timeout $runtime \
--metrics-brief --tz --times \
--af-alg 0 --bsearch 0 --context 0 --cpu 0 \
--crypt 0 --hsearch 0 --longjmp 0 --lsearch
0 \
--matrix 0 --qsort 0 --str 0 --stream 0 \
--tsearch 0 --vecmath 0 --wcs 0
as executed by the cpu_stress script from the cpu/cpu_stress_ng test
in the certification suite.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic s390x
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Fri Nov 3 11:12:04 2017
HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M
BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.13.0-16-generic N/A
linux-backports-modules-4.13.0-16-generic N/A
linux-firmware 1.169
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
---
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4
IwConfig: Error: [Errno 2] No such file or directory
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M
BOOT_IMAGE=0
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
RelatedPackageVersions:
linux-restricted-modules-4.13.0-16-generic N/A
linux-backports-modules-4.13.0-16-generic N/A
linux-firmware 1.169
RfKill: Error: [Errno 2] No such file or directory
Tags: artful
Uname: Linux 4.13.0-16-generic s390x
UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago)
UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1729878/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
