Comment 6 for bug 1819447

Saw this with a1.large on D-AWS:
        sysfs FAILED
        stress-ng: debug: [16588] 2 processors online, 2 processors configured
        stress-ng: info: [16588] dispatching hogs: 4 sysfs
        stress-ng: debug: [16588] cache allocate: reducing cache level from L3 (too high) to L2
        stress-ng: debug: [16588] cache allocate: default cache size: 2048K
        stress-ng: debug: [16588] starting stressors
        stress-ng: debug: [16589] stress-ng-sysfs: started [16589] (instance 0)
        stress-ng: debug: [16588] 4 stressors spawned
        stress-ng: debug: [16590] stress-ng-sysfs: started [16590] (instance 1)
        stress-ng: debug: [16592] stress-ng-sysfs: started [16592] (instance 3)
        stress-ng: debug: [16591] stress-ng-sysfs: started [16591] (instance 2)
        stress-ng: error: [16590] stress-ng-sysfs: A SIGSEGV occurred while exercising /sys/fs/cgroup/devices/init.scope/notify_on_release, aborting
        stress-ng: debug: [16590] stress-ng-sysfs: exited [16590] (instance 1)
        stress-ng: error: [16589] stress-ng-sysfs: A SIGSEGV occurred while exercising /sys/devices/platform/ACPI0007:08/uevent, aborting
        stress-ng: debug: [16589] stress-ng-sysfs: exited [16589] (instance 0)
        stress-ng: error: [16588] process 16589 (stress-ng-sysfs) terminated with an error, exit status=1 (stress-ng core failure)
        stress-ng: debug: [16588] process [16589] terminated
        stress-ng: error: [16588] process 16590 (stress-ng-sysfs) terminated with an error, exit status=1 (stress-ng core failure)
        stress-ng: debug: [16588] process [16590] terminated
        stress-ng: debug: [16592] stress-ng-sysfs: exited [16592] (instance 3)
        stress-ng: debug: [16591] stress-ng-sysfs: exited [16591] (instance 2)
        stress-ng: debug: [16588] process [16591] terminated
        stress-ng: debug: [16588] process [16592] terminated
        stress-ng: info: [16588] unsuccessful run completed in 5.00s