Fallback CRC-32C computation wrongly uses SSE4.1 instructions

2021-01-30 20:34:40 0 [Note] InnoDB: Using Linux native AIO

2021-01-30 20:34:40 0 [Note] InnoDB: Uses event mutexes

2021-01-30 20:34:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2021-01-30 20:34:40 0 [Note] InnoDB: Number of pools: 1

2021-01-30 20:34:40 0 [Note] InnoDB: Using generic crc32 instructions

2021-01-30 20:34:40 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)

2021-01-30 20:34:40 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728

2021-01-30 20:34:40 0 [Note] InnoDB: Completed initialization of buffer pool

2021-01-30 20:34:40 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

210130 20:34:40 [ERROR] mysqld got signal 4 ;

This could be because you hit a bug. It is also possible that this binary

or one of the libraries it was linked against is corrupt, improperly built,

or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help

diagnose the problem, but since we have already crashed,

something is definitely wrong and this may fail.

Server version: 10.5.8-MariaDB-log

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=0

max_threads=153

thread_count=0

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466473 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

terribly wrong...

stack_bottom = 0x0 thread_stack 0x49000

??:0(my_print_stacktrace)[0x12d69ae]

??:0(handle_fatal_signal)[0xc3b992]

addr2line: 'linux-gate.so.1': No such file

linux-gate.so.1(__kernel_sigreturn+0x0)[0xb7f87554]

??:0(my_dlerror)[0x12f1250]

??:0(std::unique_lock<std::mutex>::unlock())[0x1185e9c]

??:0(std::unique_lock<std::mutex>::unlock())[0x117b47f]

??:0(std::unique_lock<std::mutex>::unlock())[0x11fd753]

??:0(std::unique_lock<std::mutex>::unlock())[0x1201618]

??:0(std::unique_lock<std::mutex>::unlock())[0x1201c17]

??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x85df98]

??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0xfeabdc]

??:0(ha_initialize_handlerton(st_plugin_int*))[0xc3eb2d]

??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*, st_plugin_int*, st_mysql_sys_var*))[0x9e20cc]

??:0(plugin_init(int*, char**, int))[0x9e37da]

??:0(unireg_abort)[0x8df56c]

??:0(mysqld_main(int, char**))[0x8e5b35]

??:0(main)[0x8a2467]

??:0(__libc_start_main)[0xb760405a]

??:0(_start)[0x8d8811]

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains

information that should help you find out what is causing the crash.

Writing a core file...

Working directory at /var/lib/mysql

Resource Limits:

Limit                     Soft Limit           Hard Limit           Units

Max cpu time              unlimited            unlimited            seconds

Max file size             unlimited            unlimited            bytes

Max data size             unlimited            unlimited            bytes

Max stack size            8388608              unlimited            bytes

Max core file size        0                    unlimited            bytes

Max resident set          unlimited            unlimited            bytes

Max processes             15973                15973                processes

Max open files            32186                32186                files

Max locked memory         65536                65536                bytes

Max address space         unlimited            unlimited            bytes

Max file locks            unlimited            unlimited            locks

Max pending signals       15973                15973                signals

Max msgqueue size         819200               819200               bytes

Max nice priority         0                    0

Max realtime priority     0                    0

Max realtime timeout      unlimited            unlimited            us

Core pattern: core