Comment 0 for bug 1819447

We have 3 ARM64 instances for AWS, 2 of them failed with this test (a1.2xlarge, a1.large):

sysfs STARTING
sysfs RETURNED 2
sysfs FAILED
stress-ng: debug: [14785] 2 processors online, 2 processors configured
stress-ng: info: [14785] dispatching hogs: 4 sysfs
stress-ng: debug: [14785] cache allocate: reducing cache level from L3 (too high) to L2
stress-ng: debug: [14785] cache allocate: default cache size: 2048K
stress-ng: debug: [14785] starting stressors
stress-ng: debug: [14786] stress-ng-sysfs: started [14786] (instance 0)
stress-ng: debug: [14785] 4 stressors spawned
stress-ng: debug: [14788] stress-ng-sysfs: started [14788] (instance 2)
stress-ng: debug: [14789] stress-ng-sysfs: started [14789] (instance 3)
stress-ng: debug: [14787] stress-ng-sysfs: started [14787] (instance 1)
stress-ng: error: [14787] stress-ng-sysfs: A SIGSEGV occurred while exercising /sys/bus/pci/slots/15/attention, aborting
stress-ng: debug: [14787] stress-ng-sysfs: exited [14787] (instance 1)
stress-ng: debug: [14786] stress-ng-sysfs: exited [14786] (instance 0)
stress-ng: debug: [14789] stress-ng-sysfs: exited [14789] (instance 3)
stress-ng: debug: [14785] process [14786] terminated
stress-ng: debug: [14788] stress-ng-sysfs: exited [14788] (instance 2)
stress-ng: error: [14785] process 14787 (stress-ng-sysfs) terminated with an error, exit status=1 (stress-ng core failure)