Comment 3 for bug 1757967

It seems that the stress-ng log messages from the enosys testcase are:

Mar 22 06:27:10 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test stress-ng: info: [14237] dispatching hogs: 4 enosys
Mar 22 06:27:10 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test stress-ng: info: [14237] cache allocate: using built-in defaults as unable to determine cache details
Mar 22 06:27:10 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test kernel: [ 513.698028] signal_fault: 5 callbacks suppressed
Mar 22 06:27:10 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test kernel: [ 513.698030] stress-ng-enosy[14972] bad frame in x32 rt_sigreturn frame:00007ffc115313c0 ip:40128f5c28f5c28f sp:500cd8a6c9bbb800 orax:ffffffffffffffff
Mar 22 06:27:10 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test kernel: [ 513.699810] stress-ng-enosy[14993] bad frame in x32 rt_sigreturn frame:00007ffc115313c0 ip:40128f5c28f5c28f sp:500cd8a6c9bbb800 orax:ffffffffffffffff
Mar 22 06:27:10 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test kernel: [ 513.700422] stress-ng-enosy[15001] bad frame in x32 rt_sigreturn frame:00007ffc115313c0 ip:40128f5c28f5c28f sp:500cd8a6c9bbb800 orax:ffffffffffffffff
Mar 22 06:27:10 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test kernel: [ 513.702243] stress-ng-enosy[15022] bad frame in x32 rt_sigreturn frame:00007ffc115313c0 ip:40128f5c28f5c28f sp:500cd8a6c9bbb800 orax:ffffffffffffffff
Mar 22 06:27:13 x-la-azure-4-13-0-Standard-H16mr-stress-smoke-test stress-ng: info: [14237] successful run completed in 2.96s