> Can you please help out and try to produce a repeatable test case to > trigger this bug?
I managed to reproduce the issue in a KVM virtual machine running on a Raspberry Pi 4. The detail I was missing was having to restart the server twice after creating a rocksdb table. I believe it should be possible to reproduce the issue on an emulated VM, but I couldn't find a way to configure CPU features in QEMU as required. -- Check that crc32 is supported, but pmull isn't. root@armtest:~# grep Features /proc/cpuinfo Features : fp asimd evtstrm crc32 cpuid root@armtest:~# apt-get install mariadb-plugin-rocksdb root@armtest:~# mysql <<< "CREATE DATABASE a; USE a; CREATE TABLE a (id INT PRIMARY KEY) ENGINE=ROCKSDB; INSERT INTO a VALUES (1);" root@armtest:~# mysql <<< "SELECT * FROM a.a;" -- This returns correct results root@armtest:~# systemctl restart mysql root@armtest:~# mysql <<< "SELECT * FROM a.a;" -- Restart mysql once, everything still works root@armtest:~# systemctl restart mysql Job for mariadb.service failed because a fatal signal was delivered to the control process. See "systemctl status mariadb.service" and "journalctl -xe" for details. -- But the second restart fails!
