stress-ng freezes system

[Kenneth]

While running "stress-ng --aggressive --verify --timeout 2860 --log-file stress-ng-brk.log -v --brk 0", the system would freeze within an hour of running the test.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: stress-ng 0.05.23-1ubuntu2
ProcVersionSignature: User Name 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic ppc64le
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: ppc64el
Date: Fri Aug 19 01:04:30 2016
ProcEnviron:
 SHELL=/bin/bash
 TERM=linux
 PATH=(custom, user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=<set>
ProcLoadAvg: 0.00 0.00 0.00 1/1200 10125
ProcLocks:
 1: POSIX ADVISORY WRITE 7809 00:14:652 0 EOF
 2: FLOCK ADVISORY WRITE 7797 00:14:646 0 EOF
 3: POSIX ADVISORY WRITE 7799 00:14:656 0 EOF
 4: POSIX ADVISORY WRITE 8810 00:14:670 0 EOF
 5: POSIX ADVISORY WRITE 4914 00:14:419 0 EOF
ProcSwaps:
 Filename Type Size Used Priority
 /swap.img file 8388544 0 -1
ProcVersion: Linux version 4.4.0-34-generic (buildd@bos01-ppc64el-022) (gcc version 5.3.1 20160413 (User Name/IBM 5.3.1-14ubuntu2.1) ) #53-User Name SMP Wed Jul 27 16:04:07 UTC 2016
SourcePackage: stress-ng
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 20
cpu_coreson: Number of cores online = 20
cpu_smt: SMT=8

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1614791

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Kenneth (kennethc-m)]

apport-collect 1614791 cannot run because it is unable to identify the application

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc3

[Kenneth (kennethc-m)]

Hi Joseph,

I was able to run with 4.8 kernel.

[Joseph Salisbury (jsalisbury)]

Can you also give the latest 4.4 upstream stable kernel a test? It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/

[Colin Ian King (colin-king)]

I've been soak testing the 4.4.0-64-generic with stress-ng across multiple cores on ppc64 with 4GB of swap and have not been able to hang the kernel. Can you test with the latest kernel and see if this resolves the issue for you?

[Colin Ian King (colin-king)]

Hi Kenneth, I've not had any updates on this bug from you, so I am going to close it. If this is still and issue, please feel free to reopen this bug.