Comment 1 for bug 1542741

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.)