stress-ng-membarrier: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64

[pradeepvdevan]

I am getting this error while running it.

CentOS Linux release 7.6.1810 (Core) Linux srlinux 4.19.39-2.x86_64 #1 SMP PREEMPT Mon Mar 23 16:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[root@mypc tmp]# sudo stress-ng --all 2 --timeout 2s stress-ng: info: [20389] dispatching hogs: 2 af-alg, 2 affinity, 2 aio, 2 aiol, 2 apparmor, 2 atomic, 2 bigheap, 2 brk, 2 bsearch, 2 cache, 2 cap, 2 chdir, 2 chmod, 2 chown, 2 chroot, 2 clock, 2 clone, 2 context, 2 copy-file, 2 cpu, 2 cpu-online, 2 crypt, 2 daemon, 2 dccp, 2 dentry, 2 dir, 2 dirdeep, 2 dnotify, 2 dup, 2 epoll, 2 eventfd, 2 exec, 2 fallocate, 2 fanotify, 2 fault, 2 fcntl, 2 fiemap, 2 fifo, 2 filename, 2 flock, 2 fork, 2 fp-error, 2 fstat, 2 full, 2 futex, 2 get, 2 getdent, 2 getrandom, 2 handle, 2 hdd, 2 heapsort, 2 hsearch, 2 icache, 2 icmp-flood, 2 inotify, 2 io, 2 iomix, 2 ioprio, 2 itimer, 2 kcmp, 2 key, 2 kill, 2 klog, 2 lease, 2 link, 2 locka, 2 lockbus, 2 lockf, 2 lockofd, 2 longjmp, 2 lsearch, 2 madvise, 2 malloc, 2 matrix, 2 membarrier, 2 memcpy, 2 memfd, 2 mergesort, 2 mincore, 2 mknod, 2 mlock, 2 mmap, 2 mmapfork, 2 mmapmany, 2 mq, 2 mremap, 2 msg, 2 msync, 2 netlink-proc, 2 nice, 2 nop, 2 null, 2 numa, 2 oom-pipe, 2 opcode, 2 open, 2 personality, 2 pipe, 2 poll, 2 procfs, 2 pthread, 2 ptrace, 2 pty, 2 qsort, 2 quota, 2 rdrand, 2 readahead, 2 remap, 2 rename, 2 resources, 2 rlimit, 2 rmap, 2 rtc, 2 schedpolicy, 2 sctp, 2 seal, 2 seccomp, 2 seek, 2 sem, 2 sem-sysv, 2 sendfile, 2 shm, 2 shm-sysv, 2 sigfd, 2 sigfpe, 2 sigpending, 2 sigq, 2 sigsegv, 2 sigsuspend, 2 sleep, 2 sock, 2 sockfd, 2 sockpair, 2 spawn, 2 splice, 2 stack, 2 stackmmap, 2 str, 2 stream, 2 switch, 2 symlink, 2 sync-file, 2 sysfs, 2 sysinfo, 2 tee, 2 timer, 2 timerfd, 2 tlb-shootdown, 2 tmpfs, 2 tsc, 2 tsearch, 2 udp, 2 udp-flood, 2 unshare, 2 urandom, 2 userfaultfd, 2 utime, 2 vecmath, 2 vfork, 2 vforkmany, 2 vm, 2 vm-rw, 2 vm-splice, 2 wait, 2 wcs, 2 xattr, 2 yield, 2 zero, 2 zlib, 2 zombie stress-ng: info: [20394] stress-ng-apparmor: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 stress-ng: info: [20412] stress-ng-copy-file: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 stress-ng: info: [20453] stress-ng-getrandom: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 stress-ng: info: [20480] stress-ng-lockofd: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 stress-ng: error: [20433] stress-ng-fanotify: cannot initialize fanotify, errno=38 (Function not implemented) stress-ng: info: [20483] stress-ng-madvise: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 stress-ng: info: [20486] stress-ng-membarrier: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 stress-ng: info: [20431] stress-ng-exec: running as root, won't run test. stress-ng: fail: [20470] stress-ng-kcmp: kcmp: KCMP_FILE failed, errno=38 (Function not implemented) stress-ng: fail: [20470] stress-ng-kcmp: kcmp: KCMP_FILE failed, errno=38 (Function not implemented) stress-ng: fail: [20470] stress-ng-kcmp: kcmp: KCMP_FILE failed, errno=38 (Function not implemented) stress-ng: fail: [20470] stress-ng-kcmp: kcmp: KCMP_FILE failed, errno=38 (Function not implemented) stress-ng: fail: [20470] stress-ng-kcmp: kcmp: KCMP_FILES failed, errno=38 (Function not implemented) info: 5 failures reached, aborting stress process

[ColinIanKing]

Hi, I've pushed a fix for these, please pull and rebuild and let me know if this fixes this issue.

[pradeepvdevan]

Thanks for the quick response. I pulled your changes, now I am getting these.

stress-ng: info: [7267] stress-ng-af-alg: 17 cryptographic algorithms found in /proc/crypto stress-ng: info: [7267] stress-ng-af-alg: 104 cryptographic algorithms max (with defconfigs) stress-ng: info: [7270] stress-ng-aiol: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: info: [7275] stress-ng-binderfs: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: info: [7283] stress-ng-cap: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: info: [7300] stress-ng-cyclic: for best results, run just 1 instance of this stressor stress-ng: info: [7296] stress-ng-copy-file: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: error: [7318] stress-ng-fanotify: cannot initialize fanotify, errno=38 (Function not implemented) stress-ng: info: [7342] stress-ng-heapsort: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: info: [7393] stress-ng-mergesort: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: info: [7358] stress-ng-key: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: info: [7356] stress-ng-judy: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: error: [7412] stress-ng-netlink-task: failed to get family id stress-ng: error: [7411] stress-ng-netlink-proc: writev failed: errno=111 (Connection refused) stress-ng: info: [7388] stress-ng-memhotplug: /sys/devices/system/memory not accessible, skipping stressor stress-ng: info: [7302] stress-ng-dccp: DCCP protocol not supported, skipping stressor stress-ng: info: [7508] stress-ng-numa: system has 1 of a maximum 4 memory NUMA nodes stress-ng: info: [7392] stress-ng-memthrash: starting 8 threads on each of the 2 stressors on a 16 CPU system stress-ng: info: [7524] stress-ng-radixsort: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: fail: [7508] stress-ng-numa: get_mempolicy failed, errno=38 (Function not implemented) stress-ng: info: [7802] stress-ng-sctp: this stressor is not implemented on this system: x86_64 Linux 4.19.39-2.x86_64 gcc 4.8 stress-ng: info: [7300] stress-ng-cyclic: SCHED_FIFO: no latency information available stress-ng: info: [7390] stress-ng-memrate: write64: interrupted early stress-ng: info: [7390] stress-ng-memrate: read64: interrupted early stress-ng: info: [7390] stress-ng-memrate: write32: interrupted early stress-ng: info: [7390] stress-ng-memrate: read32: interrupted early stress-ng: info: [7390] stress-ng-memrate: write16: interrupted early stress-ng: info: [7390] stress-ng-memrate: read16: interrupted early stress-ng: info: [7390] stress-ng-memrate: write8: interrupted early stress-ng: info: [7390] stress-ng-memrate: read8: interrupted early stress-ng: info: [7528] stress-ng-readahead: test expired during test setup (writing of data file) stress-ng: info: [7308] stress-ng-dirdeep: note: specifying a larger --dirdeep setting or running the stressor for longer will use more inodes stress-ng: info: [7514] stress-ng-pipeherd: 0.66 context switches per bogo operation (71274.43 per second) stress-ng: error: [7260] process 7318 (stress-ng-fanotify) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: info: [7533] stress-ng-revio: average number of extents 28590.00 stress-ng: error: [7260] process 7411 (stress-ng-netlink-proc) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: error: [7260] process 7412 (stress-ng-netlink-task) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: error: [7260] process 7508 (stress-ng-numa) terminated with an error, exit status=1 (stress-ng core failure) stress-ng: info: [7260] unsuccessful run completed in 4.24s [root@srlinux tmp]#

[ColinIanKing]

Hi again, I've pushed a few more changes to the repository that should address these issues. Please pull, rebuild and let me know if this helps. Thanks!

[ColinIanKing]

Any chance to test the fixes yet?

[pradeepvdevan]

Hi, I did test it again after pulling your latest changes and it works like charm. Thank you!