© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
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 stack stressor for 300 seconds....
stress-ng: info: [4431] dispatching hogs: 256 stack
stress-ng: info: [4431] successful run completed in 742.49s (12 mins, 22.49 secs)
return_code is 124
*******
** Error 124 reported on stressor stack!)
*******
Running stress-ng brk stressor for 930 seconds....
stress-ng: info: [5007] dispatching hogs: 256 brk
stress-ng: info: [5007] successful run completed in 1412.12s (23 mins, 32.12 secs)
return_code is 124
*******
** Error 124 reported on stressor brk!)
*******
*******
** stress-ng memory test failed; most recent error was 124
*******
ubuntu@lalande:~$ free -m
total used free shared buff/cache available
Mem: 64281 1133 62825 11 322 62530
Swap: 796134 0 796134
I'm attaching a tarball with dmesg, the output of vmstat 1 that shows the memory consumption during testing, and a copy of the test script being used.