Memory Stress-ng Test Failing on a System with 881.46GB of RAM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Stress-ng |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have a system with a large amount of memory that is failing with the stress-ng memory test. It did pass when the amount of memory for the test was reduced. Typically we like stress the system with the maximum amount available. Once the memory was added back in, the same failures occurred. We tried increasing the base timeout and that passed all of the stressors except malloc. I am unsure if this is an actual bug where the system resources cannot keep up or are we being too aggressive with the testcase.
CPU: AMD EPYC 9754 128-Core Processor (Bergamo)
Mem: 881 GB
22.04.4 5.15 kernel
Steps to Reproduce
sudo add-apt-repository ppa:checkbox-
sudo apt install canonical-
sudo /usr/lib/
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Initially mlock, mremap, shm-sysv, vm-splice, numa, malloc failed
03 Sep 07:34: Running stress-ng mlock stressor for 300 seconds...
** stress-ng timed out and was forcefully terminated
03 Sep 11:50: Running stress-ng mremap stressor for 300 seconds...
** stress-ng timed out and was forcefully terminated
03 Sep 12:00: Running stress-ng shm-sysv stressor for 300 seconds...
** stress-ng timed out and was forcefully terminated
03 Sep 12:10: Running stress-ng vm-splice stressor for 300 seconds...
** stress-ng timed out and was forcefully terminated
03 Sep 12:20: Running stress-ng numa stressor for 300 seconds...
** stress-ng timed out and was forcefully terminated
-03 Sep 12:30: Running stress-ng malloc stressor for 9115 seconds...
** stress-ng timed out and was forcefully terminated
However, after doubling, tripling and quadrupling the 300 second timeout malloc is the only stressors with an issue.