stress ng seal regression on K-riscv 5.19-1003

[Dimitri John Ledkov]

stress ng seal regression

1800 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] invoked with './stress-ng -v -t 5 --seal 4 --seal-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
    1801 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] stress-ng 0.14.03 g346518caffe5
    1802 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] system: Linux riscv64-kinetic 5.19.0-1003-generic #3-Ubuntu SMP Mon Oct 10 15:09:23 UTC 2022 riscv64
    1803 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] RAM total: 7.8G, RAM free: 7.4G, swap free: 1021.4M
    1804 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] 8 processors online, 8 processors configured
    1805 21:47:23 DEBUG| [stdout] stress-ng: info: [43108] setting to a 5 second run per stressor
    1806 21:47:23 DEBUG| [stdout] stress-ng: info: [43108] dispatching hogs: 4 seal
    1807 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] cache allocate: using defaults, cannot determine cache level details
    1808 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] cache allocate: shared cache buffer size: 2048K
    1809 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] starting stressors
    1810 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] 4 stressors started
    1811 21:47:23 DEBUG| [stdout] stress-ng: debug: [43109] stress-ng-seal: started [43109] (instance 0)
    1812 21:47:23 DEBUG| [stdout] stress-ng: debug: [43110] stress-ng-seal: started [43110] (instance 1)
    1813 21:47:23 DEBUG| [stdout] stress-ng: debug: [43111] stress-ng-seal: started [43111] (instance 2)
    1814 21:47:23 DEBUG| [stdout] stress-ng: debug: [43112] stress-ng-seal: started [43112] (instance 3)
    1815 21:47:23 DEBUG| [stdout] stress-ng: fail: [43110] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
    1816 21:47:23 DEBUG| [stdout] stress-ng: fail: [43109] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
    1817 21:47:23 DEBUG| [stdout] stress-ng: fail: [43111] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
    1818 21:47:23 DEBUG| [stdout] stress-ng: fail: [43112] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
    1819 21:47:23 DEBUG| [stdout] stress-ng: debug: [43109] stress-ng-seal: exited [43109] (instance 0)
    1820 21:47:23 DEBUG| [stdout] stress-ng: debug: [43110] stress-ng-seal: exited [43110] (instance 1)
    1821 21:47:23 DEBUG| [stdout] stress-ng: debug: [43112] stress-ng-seal: exited [43112] (instance 3)
    1822 21:47:23 DEBUG| [stdout] stress-ng: debug: [43111] stress-ng-seal: exited [43111] (instance 2)
    1823 21:47:23 DEBUG| [stdout] stress-ng: error: [43108] process 43109 (stress-ng-seal) terminated with an error, exit status=2 (stressor failed)
    1824 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] process [43109] terminated
    1825 21:47:23 DEBUG| [stdout] stress-ng: error: [43108] process 43110 (stress-ng-seal) terminated with an error, exit status=2 (stressor failed)
    1826 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] process [43110] terminated
    1827 21:47:23 DEBUG| [stdout] stress-ng: error: [43108] process 43111 (stress-ng-seal) terminated with an error, exit status=2 (stressor failed)
    1828 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] process [43111] terminated
    1829 21:47:23 DEBUG| [stdout] stress-ng: error: [43108] process 43112 (stress-ng-seal) terminated with an error, exit status=2 (stressor failed)
    1830 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] process [43112] terminated
    1831 21:47:23 DEBUG| [stdout] stress-ng: debug: [43108] metrics-check: all stressor metrics validated and sane
    1832 21:47:23 DEBUG| [stdout] stress-ng: info: [43108] unsuccessful run completed in 0.05s
    1833 21:47:23 DEBUG| [stdout]

potentially related to the https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992484

[Colin Ian King (colin-king)]

Which file system is that running the test on?

[Po-Hsu Lin (cypressyew)]

Hi Colin,
It's ext4:
ubuntu@riscv64-kinetic:~$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
tmpfs tmpfs 794M 468K 794M 1% /run
/dev/vda1 ext4 20G 8.0G 11G 43% /
tmpfs tmpfs 3.9G 4.0K 3.9G 1% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 3.9G 0 3.9G 0% /run/qemu
tmpfs tmpfs 794M 0 794M 0% /run/user/1000

I can see this issue has gone with K-riscv 5.19.0-1004.4
and bug 1992484 has been marked as Fix committed for Jammy.