stress-ng: numa stressor may be unreliable on some systems
Bug #1542741 reported by
Colin Ian King
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
stress-ng (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King |
Bug Description
User is seeing errors:
stress-ng: fail: [19811] stress-ng-numa: mbind: errno=5 (Input/output
error)
stress-ng: info: [19811] 5 failures reached, aborting stress process
stress-ng: fail: [19658] stress-ng-numa: mbind: errno=5 (Input/output
error)
stress-ng: fail: [19792] stress-ng-numa: mbind: errno=5 (Input/output
error)
stress-ng: info: [19792] 5 failures reached, aborting stress process
stress-ng: fail: [19658] stress-ng-numa: mbind: errno=5 (Input/output
error)
stress-ng: fail: [19658] stress-ng-numa: mbind: errno=5 (Input/output
error)
stress-ng: info: [19658] 5 failures reached, aborting stress process
Need to investigate why this is occurring
Changed in stress-ng (Ubuntu): | |
importance: | Undecided → Medium |
assignee: | nobody → Colin Ian King (colin-king) |
status: | New → Incomplete |
Changed in stress-ng (Ubuntu): | |
status: | Incomplete → In Progress |
To post a comment you must log in.
I'm attaching a tarball with additional information. This includes runs that generate these errors on three systems in the certification lab in 1SS: rollinia, wildorange, and hogplum. I'm providing both sample runs and CPU information ("lscpu" and "cat /proc/cpuinfo" output) for each system. I've been running via a simple script, which I'm also attaching. (We've omitted the --numa option from the final certification script, but I've added it back to this version so as to trigger the complaint from stress-ng.)