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 reasonable to create, IMO, 100GB swap files just to be sure we
don't accidentally trip the OOMKiller when running memory tests.

Also, the ratio seems to be variable. On my amd64 system, the swap
consumed was 5x the amount of installed RAM.  On the ppc64le system, the
amount was just shy of 2x the amount of physical RAM (this is also a
NUMA capable system, so maybe that's a contributing factor, beyond the
differences in how each arch handles memory, which I freely admit to not
understanding well.

-- 
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:
  Invalid
Status in linux source package in Artful:
  Invalid

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     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to